IoT and OT: include physical safety in security decisions

Digital actions can have physical consequences

IoT includes varied connected sensors and service devices. OT involves systems that monitor or control physical processes. They overlap, but devices are not interchangeable. Restarting an office test machine can have very different consequences from interrupting a process controller.

Security measures must account for performance, reliability, physical safety and availability. Updates, scans or isolation may require vendor support, offline testing, operator coordination and maintenance windows. Ordinary IT scanning habits cannot simply be transferred.

Further reading: NIST SP 800-82 Rev. 3: OT Security

Identify communication that is actually necessary

Inventory device purpose, owner, version, support lifetime and required data flows. Segmentation and controlled channels can limit unnecessary connections, but rules must match operational needs and retain emergency and recovery procedures.

Begin validation with synthetic diagrams or an isolated test environment. Real-device changes must follow site approval procedures. This unit’s table establishes design reasoning, not verified safety of a production process.

Example: a temperature sensor and a controller

In a fictional greenhouse, a sensor sends temperature to a controller, which adjusts a fan. A reporting service only needs to read summaries.

The reporting service does not need to alter fan settings. Limit that unnecessary control path while retaining required sensing and control flows. Isolation should not blindly sever every connection.

Conclusion: Base the design on necessary flows; operational and safety verification remain necessary before activation.