Zero-Trust Network Segmentation for Industrial Control Systems

Zero trust in an industrial environment means no device, user or network zone receives permanent confidence merely because it is inside the plant. Controls must still respect availability, safety and legacy-protocol constraints.

Photo by Brecht Corbeel on Unsplash.
Why this topic matters
Good engineering decisions connect calculations with site conditions, equipment data and operating scenarios. The workflow below is intended for preliminary design, technical review and commissioning preparation. It does not replace the current local code, utility rules or a competent professional’s approval.
Core engineering checks
- Inventory assets, owners, firmware, protocols and required communication flows.
- Create zones for enterprise, operations, safety, vendors and field equipment.
- Allow only documented conduits and inspect traffic at controlled boundaries.
- Use strong identity, managed jump hosts, logging and time-limited remote access.
Calculation starting point
Measure progress with observable controls: percentage of known assets, blocked unauthorized flows, privileged sessions recorded, patch exposure and time to revoke vendor access.
Recommended workflow
- Collect evidence: obtain drawings, interval data, nameplates, manufacturer curves and site measurements.
- Define scenarios: include normal operation, peak demand, maintenance states, credible faults and future expansion.
- Calculate: state assumptions, units, correction factors and the source of every input.
- Coordinate: check interfaces with protection, controls, communications, civil works and operations.
- Verify: turn each design assumption into an inspection, measurement or functional test.
Europe and Gulf considerations
Critical-infrastructure operators in Europe and the Gulf face different regulatory frameworks, but both benefit from evidence-based segmentation and tested recovery rather than a firewall-only strategy.
Common mistakes
- Using nominal ratings without environmental or installation derating.
- Checking only one operating condition.
- Relying on software output without validating inputs and boundary conditions.
- Leaving commissioning criteria undefined until the equipment arrives.
- Failing to record the final settings, firmware, drawings and test results.
Handover checklist
Keep the approved design basis, calculations, single-line or network diagram, equipment schedules, protection and control settings, inspection records, test certificates, operating instructions, maintenance intervals and an as-built change log. A useful handover package allows a future engineer to understand not only what was installed, but why.
Frequently asked questions
Can this method be used for final design?
It is a strong review framework, but final values must come from project-specific data and the current requirements of the responsible authority.
What should be verified first?
Verify the input data that most strongly changes safety or capacity: source strength, load profile, environment, installation method and protective-device characteristics.
How should uncertainty be handled?
Use conservative but explicit assumptions, test sensitivity to uncertain inputs, and replace assumptions with measurements during commissioning.
Explore more practical guides in our engineering library and English Engineering section.




