OT segmentation readiness: are your controls keeping up?

TL;DR: Segmentation fails when it is treated as a one-time project rather than a continuously maintained control, because plant teams cannot contain what they cannot inventory, observe, or prove is isolated, according to Asimily’s analysis of the Mackay Sugar shutdown. Blast-radius control and restart confidence depend on live device context, not static network diagrams.

Editorial analysis by NHI Mgmt Group, based on content published by Asimily: “What the Mackay Sugar Shutdown Reveals About OT Segmentation Readiness”.

Key questions

Q: What breaks when OT segmentation is designed once and left alone?

A: Static segmentation loses fidelity as devices, routes, and production dependencies change.

Q: Why do OT teams need exploitability analysis instead of raw vulnerability counts?

A: Because severity scores do not tell you whether a flaw is reachable in the plant’s actual topology.

Q: How do security teams know if segmentation is still working in an industrial environment?

A: They validate it against observed traffic, not just design diagrams.

Practitioner guidance

• Build a current OT and IoT inventory Capture every connected device, communication path, and firmware state across production and corporate networks, then refresh it continuously as assets move or change.
• Prioritise by reachable exploitability Use observed topology and traffic to decide which vulnerabilities are actually reachable on specific assets, then focus remediation on the small set of devices driving most of the risk.
• Simulate segmentation before enforcement Test proposed network policies against live traffic to show exactly which devices and connections would be affected before any rule is applied.

Bottom line: The shutdown shows how OT resilience depends on the systems that coordinate production, not just the machines that perform it.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →