Critical infrastructure guide
Identity and Access Management
Control who and what can access infrastructure systems.
Safety and security boundary: this page stays at a public, defensive, conceptual level. It does not provide operating procedures for hazardous infrastructure, security-bypass methods, exploit instructions, sabotage guidance or sensitive facility details.
Why this matters
Control who and what can access infrastructure systems.
Core system ideas
Access should match job function and be removed when no longer needed.
Privileged and vendor access deserve stronger oversight because they can affect many systems.
Resilient identity design also considers what happens when the primary authentication service is unavailable.
What to review
Useful reviews usually combine service criticality, dependencies, condition, capacity, maintenance, alternate arrangements, restoration time and clear ownership rather than relying on one isolated metric.