Topic starter
14/08/2026 6:33 pm
TL;DR: Manufacturers are using identity-based microsegmentation to reduce outage risk, protect legacy systems, and produce audit-ready segmentation evidence, according to Zero Networks’ customer roundup and cited IBM breach data. The governance lesson is that resilience controls must be operationally non-disruptive or they stall before they can materially reduce blast radius.
Editorial analysis by NHI Mgmt Group, based on content published by Zero Networks: “How 3 Manufacturers Secured Production-Critical Systems with Microsegmentation”.
By the numbers:
- The mean time to identify and contain a breach increased over the last year, according to IBM’s 2026 Cost of a Data Breach Report cited by Zero Networks.
Key questions
Q: What breaks when manufacturing segmentation requires agents or re-architecture?
A: It usually fails at the adoption layer.
Q: Why does microsegmentation matter even when teams already use detection tools for containers?
A: Detection is useful, but it is not enough on its own because modern attacks can move faster than teams can investigate and respond.
Q: What are the main signs that segmentation is too complex for a manufacturing environment?
A: The warning signs are long rollout cycles, heavy dependence on manual policy changes, fear of breaking live systems, and poor fit with legacy assets or lean IT capacity.
Practitioner guidance
- Map segmentation to production-critical trust zones Identify the systems where downtime would materially affect production, and define segmentation boundaries around those zones before changing controls anywhere else.
- Prioritise agentless deployment paths Choose architectures that use native controls already present in the environment so you avoid introducing agents, extra latency, and rollout risk.
- Add just-in-time MFA for privileged operations Apply task-scoped MFA to administrative access paths that reach legacy and production systems, especially where standing privilege would widen blast radius.
Bottom line: Manufacturing segmentation fails when deployment complexity, agent overhead, or legacy compatibility problems make the control harder to operate than the risk it is meant to reduce.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/08/2026 6:41 pm
Resilience controls in manufacturing are only real when they are operationally non-disruptive. The article shows that the central barrier is not awareness of microsegmentation, but the failure of legacy deployment models to fit plant constraints. When a control risks downtime, teams delay it, and delay is itself a security decision. Practitioners should treat non-disruption as a core design requirement, not an implementation preference.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
- Breaches involving third parties rose to 48% of all breaches, a 60% increase on the previous year, according to Verizon's 2026 Data Breach Investigations Report.
A question worth separating out:
Q: When should manufacturers prioritise segmentation over other security projects?
A: They should prioritise it when a breach or outage would quickly spread across production systems, when cyber insurance requires proof of segmentation, or when legacy assets create broad lateral movement risk. In those cases, segmentation is not just another control. It becomes a containment layer that protects both operations and continuity.
👉 Read our full editorial: Microsegmentation in manufacturing: resilience without downtime risk