Book Image

IoT and OT Security Handbook

By : Smita Jain, Vasantha Lakshmi
Book Image

IoT and OT Security Handbook

By: Smita Jain, Vasantha Lakshmi

Overview of this book

The Fourth Industrial Revolution, or Industry 4.0, is all about digital transformation, manufacturing, and production. The connected world we live in today, including industries, comes with several cybersecurity challenges that need immediate attention. This book takes you through the basics of IoT and OT architecture and helps you understand and mitigate these security challenges. The book begins with an overview of the challenges faced in managing and securing IoT and OT devices in Industry 4.0. You’ll then get to grips with the Purdue model of reference architecture, which will help you explore common cyber attacks in IoT and OT environments. As you progress, you’ll be introduced to Microsoft Defender for IoT and understand its capabilities in securing IoT and OT environments. Finally, you will discover best practices for achieving continuous monitoring and vulnerability management, as well as threat monitoring and hunting, and find out how to align your business model toward zero trust. By the end of this security book, you’ll be equipped with the knowledge and skills to efficiently secure IoT and OT environments using Microsoft Defender for IoT.
Table of Contents (16 chapters)
Part 1: Understand the Challenges in IoT/OT Security and Common Attacks
Part 2: How Microsoft Defender for IoT Can Address the Open Challenges in the Connected World We Live in Today
Part 3: Best Practices to Achieve Continuous Monitoring, Vulnerability Management, Threat Monitoring and Hunting, and to Align the Business Model Toward Zero Trust
Chapter 9: Vulnerability Management and Threat Monitoring

The protocol violation detection engine

Generally, protocol violations can be identified by field values and packet structures that are being used in ways that go against the ICS protocol specifications.

In Figure 8.1, we can see Modbus Exception as an example of something picked up by the protocol violation engine. A secondary device did not send a response to the primary device when sending the exception code. This violation of the protocol was detected by MDIoT:

Figure 8.1 – Example of a protocol violation


In the MDIoT portal for the Modbus alert, the primary device is referred to as the master device, and the secondary as the slave. However, due to their unsavory connotations dating back to colonization, standardization organizations have spoken against the usage of these terms. We have used primary and secondary in this book, but there are various alternatives available, such as controller-responder and primary-replica. You can read more...