Make the controls
hold up in practice.
Connect risk decisions to controls that people can enforce, explain and maintain.
See the approachSwipe or use arrow keys to explore the diagram.
Read the diagram explanation
Name the owner, intended access and exceptions.
Carry the decision into identity, network and platform controls.
Prove required access works and other access is denied.
Record results, exceptions, ownership and review dates.
Trace the decision through the control to the tests. Keep the result and any exception with the person who owns the decision.
Follow the decision
through to evidence.
Agree the risk, choose an enforceable boundary and collect evidence that the control behaves as intended.
Define who owns the decision
Make responsibilities, exceptions and review points clear.
Put protection where it works
Integrate controls with identity, network and platform boundaries.
Check the behaviour over time
Test during maintenance, access changes and failures. Review exceptions as the environment evolves.
IEC 62443-3-3 Mapping Guide
A practical starting point for connecting system requirements to controls and evidence.
Part of the same system.
Connect the design decisions across these areas.
What needs to work better?
Start with the environment, the constraint and the change you need to make.


