The IEC 62443 risk analysis of an industrial site, step by step
Risk analysis turns a network map into decisions: what to protect first, against what and how far. IEC 62443 (part 3-2) describes the method for industrial systems. The steps below follow it.
1. Start from the site map
The analysis starts from the site map: equipment inventory, layered architecture, observed flows. Based on the observed traffic rather than a theoretical diagram, it covers the network as it runs.
2. Divide into zones and conduits
The standard organizes the site into zones, groups of equipment sharing the same security requirements (a production line, SCADA, the industrial DMZ), linked by conduits, the controlled communication channels between zones. Validated with your teams, this division structures the rest of the analysis, carried out zone by zone.
3. Identify scenarios: functional analysis, then impact analysis
For each zone, a workshop brings together the people who know the process (production, maintenance, automation). It starts with the functional analysis: the zone's role, its dependencies, what is expected of it. Then comes the impact analysis: the consequences of an unavailable SCADA, a modified recipe parameter or a hijacked remote-maintenance access. The method draws on the hazard studies industry already practices, HAZOP among them; its vocabulary is familiar to the teams.
4. Score the inherent risk, then the residual risk
Each scenario is scored, likelihood and severity, on your company's risk matrix rather than an imposed scale. The inherent risk is scored first (before measures), then the residual risk, once countermeasures are decided. The gap between the two measures what the action plan brings; the risk left above the tolerable threshold goes to management for a decision.
5. Set the target security levels
The standard gives each zone a target security level (SL-T) and derives measurable technical requirements from it. The analysis thus becomes verifiable: you check, requirement by requirement, where each zone stands.
6. The report and its update
The final report documents the scope, the map, the zones and conduits, the scenarios, the scores, the countermeasures and their rationale. It can be handed to management, an auditor, an insurer or a principal. The analysis is revised at every notable change of architecture, equipment or remote access. We also recommend a periodic review, as a good practice: no text makes it an obligation today. When the analysis is kept in a tool, that review means updating the existing project.
Tools and support
UMX Risk Manager follows this process, from the UMX Explorer map. Ultrametrix can also carry out or co-produce the analysis with your teams, who bring the process knowledge; the site then keeps its analysis in Risk Manager to keep it up to date.