What it means
An OT scenario-based risk assessment describes a credible actor or failure path, affected assets and process, enabling conditions, controls, consequences, uncertainty, and response options.
Why it matters
Abstract risk scores do not show how multiple weaknesses, access paths, operational states, and human decisions combine into a plausible event.
Practical focus
- Build scenarios from architecture, threat intelligence, incidents, maintenance practices, process hazards, and known failure modes.
- Evaluate likelihood factors, control performance, detection, response time, safe-state behavior, consequence, and uncertainty.
- Use tabletop, simulation, testbed, or controlled validation to refine assumptions and mitigation priorities.
- Preserve this evidence: Retain scenario narratives, diagrams, assumptions, threat and exposure evidence, control analysis, consequence estimates, decisions, and exercise results.
- Exercise this failure scenario: A control appears sufficient in a generic register but fails when a vendor session, maintenance bypass, and degraded process state occur together.
Common mistakes
- Using the label OT Scenario-Based Risk Assessment without defining scope, ownership, decision authority, and the exact data, systems, people, or process affected.
- Treating a policy, contract, diagram, dashboard, or tool demonstration as proof that OT Scenario-Based Risk Assessment operates consistently in production.
- Closing work without retaining the evidence needed to reconstruct the decision and verify the intended control outcome.
- Testing only the normal path and never rehearsing the failure condition: A control appears sufficient in a generic register but fails when a vendor session, maintenance bypass, and degraded process state occur together.
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: