Book Image

Practical Internet of Things Security - Second Edition

By : Brian Russell, Drew Van Duren
Book Image

Practical Internet of Things Security - Second Edition

By: Brian Russell, Drew Van Duren

Overview of this book

With the advent of the Internet of Things (IoT), businesses have to defend against new types of threat. The business ecosystem now includes the cloud computing infrastructure, mobile and fixed endpoints that open up new attack surfaces. It therefore becomes critical to ensure that cybersecurity threats are contained to a minimum when implementing new IoT services and solutions. This book shows you how to implement cybersecurity solutions, IoT design best practices, and risk mitigation methodologies to address device and infrastructure threats to IoT solutions. In this second edition, you will go through some typical and unique vulnerabilities seen within various layers of the IoT technology stack and also learn new ways in which IT and physical threats interact. You will then explore the different engineering approaches a developer/manufacturer might take to securely design and deploy IoT devices. Furthermore, you will securely develop your own custom additions for an enterprise IoT implementation. You will also be provided with actionable guidance through setting up a cryptographic infrastructure for your IoT implementations. You will then be guided on the selection and configuration of Identity and Access Management solutions for an IoT implementation. In conclusion, you will explore cloud security architectures and security best practices for operating and managing cross-organizational, multi-domain IoT deployments.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Dedication
About Packt
Contributors
Preface
Index

Handling non-functional requirements 


Non-functional requirements handle the aspects of the system that are not directly related to the functionalities of the system. SEBOK—the systems engineering body of knowledge maintained jointly by INCOSE and the IEEE computer society (https://www.sebokwiki.org/wiki/Non-Functional_Requirements_(glossary))—defines them as follows: 

Quality at

tributes or characteristics that are desired in a system, that define how a system is supposed to be.

Non-functional requirements include security, performance, availability, resilience, safety, reliability, dependability, scalability, sustainability, portability, and interoperability.

IoT systems will require different variations of these requirements, depending on the context in which the system is designed to operate (C. Warren Axelrod, Engineering Safe and Secure Software Systems, Artech House).

 

For example, an IoT system that provides management features for a critical infrastructure system will have more safety...