Join our Newsletter — 33% off our NHI Course
Home› Guides› Cyber Risk Scenario Library Guide: Build Reusable Scenarios…
Guide Security Leadership & Governance

Cyber Risk Scenario Library Guide: Build Reusable Scenarios for Registers and CRQ

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 14 min read
On this page

Most cyber risk registers list topics such as "ransomware" or "insider threat" that nobody can estimate, compare or reduce, because they are not written as scenarios. A scenario library fixes that by giving the organisation a maintained set of standard, well scoped loss scenarios that every register entry, quantification and tabletop exercise draws from. This guide explains how to structure a library, which fields to hold, how to write the core scenarios (ransomware, business email compromise, cloud data exposure, insider misuse, supplier compromise, machine credential abuse), how to keep them current and how to map them to NIST and FAIR. It is written for risk managers, CISOs and GRC analysts who already run a register and want it to support decisions. For the register itself see the Risk Register Template; for the quantification method see the Cyber Risk Quantification Guide.

Key takeaways

  • The scenario is the unit of risk. A register line, a quantified estimate and a control business case should all point at the same scenario identifier, so numbers can be compared and challenged.
  • Scope tightly. The Open Group O-RA Standard asks for one sentence: a threat agent breaches or impairs an asset, causing an observable loss event. Split scenarios when threat communities, assets or effects differ.
  • Keep 15 to 30 core scenarios, not 300. A small library that leadership recognises beats an exhaustive catalogue that nobody reviews; use variants for business units rather than new scenarios.
  • Record evidence, not just ratings. Each scenario should hold its assumptions, data sources, controls in play and owner, which O-RA and NIST IR 8286A Rev. 1 both expect to be documented.
  • Review on triggers as well as on a calendar. New incident data, a major architecture change or a relevant breach in your sector should reopen the affected scenarios.

What a scenario library is and why registers need one

NIST IR 8286A Rev. 1 (final, December 2025) describes documenting scenarios that show how threats and vulnerabilities could affect enterprise assets, and recording the likelihood and impact of the resulting threat events in cybersecurity risk registers that roll up into an enterprise risk profile. NIST IR 8286 Rev. 1 (final, December 2025) publishes a risk register schema, a risk detail record schema and an example register as supplemental files. Neither tells you which scenarios to hold: that is the job of the library.

A library is a controlled list of scenario definitions, each with an identifier, a scoping statement and supporting data. It sits between threat intelligence (what is happening) and the register (what we are doing about it). Without it, each team writes its own version of "ransomware", the same exposure is counted three times and quantitative results cannot be aggregated.

ArtefactQuestion it answersOwned byChanges when
Scenario libraryWhat can go wrong, in standard terms?Cyber risk functionThreats, architecture or business model change
Risk registerHow big is each risk here, who owns it and what is the response?Risk owners, second lineAssessments, treatments, acceptances
Risk detail recordWhat evidence and assumptions sit behind one register entry?AnalystEach reassessment
Tabletop scenario packCan we respond to it?Incident response leadExercise cycle
Control catalogueWhat reduces it?Security architectureControl changes

The same scenario identifiers can drive exercises: the Tabletop Exercise Scenario Pack works best when each exercise names the library scenario it tests.

Anatomy of a well scoped scenario

O-RA 2.0.1 (the companion analysis standard to the Open Group Risk Taxonomy, O-RT 3.0.1) breaks scoping into a small number of elements. Using them as mandatory fields keeps scenarios comparable.

  • Asset: the information, system or component that is breached or impaired. Its value comes from the business processes it supports, so name the process too (for example "payments ledger supporting supplier payments").
  • Primary stakeholder: the accountable party that bears the loss, usually the asset or process owner.
  • Threat community: a subset of the threat agent population that shares key characteristics. O-RA asks for the most probable communities only, profiled by motive, access method, skill and resources, and recommends a consistent attribute list reused across analyses.
  • Threat event type and vector: malicious, error, failure or natural, plus the vector, because each vector has different frequencies and controls.
  • Effect: confidentiality, integrity or availability. O-RA says to analyse these separately and requires a loss event the stakeholder can observe; an unobserved compromise remains a threat event.
  • Loss forms: O-RT lists six: productivity, response, replacement, fines and judgements, competitive advantage and reputation. Primary loss falls on the stakeholder directly; secondary loss arises when customers, regulators or others react.
  • Timeframe: O-RA leaves this to the analyst; use one year across the library so frequencies are comparable.

O-RA treats a scope as too broad when it combines threat communities with nothing in common, several observable loss events or several asset types. A useful test is whether one person could estimate how often the scenario happens per year. "Ransomware" fails that test; "financially motivated extortion group encrypts the ERP platform through a compromised remote access account, halting order processing" passes it. The FAIR Model and Open FAIR Standard Guide covers the full factor tree.

Library record fields

Design the record so it maps onto the NIST IR 8286 register and detail record rather than inventing a parallel structure. The fields below are a practical minimum; the right-hand column shows where each value flows.

FieldContentFeeds
Scenario ID and versionStable identifier such as SCN-RAN-01 v3Register entry, CRQ model, exercise pack
Scenario statementOne sentence in O-RA formRegister risk description
Asset and business processNamed systems and the process they supportBusiness impact analysis
Threat community profileMotive, access method, skill, resourcesThreat event frequency estimate
Vector and ATT&CK techniquesInitial access route and key technique IDsDetection coverage review
Effect and loss formsC, I or A; which of the six loss forms applyLoss magnitude estimate
Frequency and magnitude rangesMinimum, most likely, maximum per year, with sourcesQuantitative model or likelihood rating
Key controlsControls assumed to operate, with ownerControl assurance testing
Assumptions and data sourcesLogs, incident history, industry data, expert judgementRisk detail record
Triggers for reviewEvents that reopen the scenarioMonitoring and KRIs
Owner and last review dateAccountable person and dateGovernance reporting

Keep business unit variants as child records (SCN-RAN-01-EU, SCN-RAN-01-Retail) that inherit the parent statement and override only the asset, frequency or magnitude. That lets you report both a group view and a unit view without double counting.

Core scenarios most organisations need

The set below is a starting point, written at the level of a library entry. Each should be tailored to named assets and then split further where the analysis shows different vectors behave differently.

IDScenario statement (template)EffectIndicative ATT&CKDominant loss forms
RAN-01Extortion group encrypts [core platform] through [remote access / exploited edge device], halting [process]AvailabilityT1486 Data Encrypted for Impact, T1490 Inhibit System RecoveryProductivity, response, replacement
RAN-02Extortion group exfiltrates [regulated dataset] and threatens publicationConfidentialityT1567 Exfiltration Over Web ServiceResponse, fines and judgements, reputation
BEC-01Fraudster using a compromised or spoofed mailbox diverts [supplier or payroll] paymentsIntegrityT1566 Phishing, T1534 Internal Spearphishing, T1657 Financial TheftProductivity (direct funds), response
CLD-01External actor reads [customer data store] through a misconfigured or over-permissive cloud storage resourceConfidentialityT1530 Data from Cloud StorageResponse, fines and judgements, reputation
CLD-02Attacker uses stolen cloud account or workload credentials to take control of [production tenant]Integrity and availabilityT1078.004 Cloud AccountsProductivity, response, replacement
INS-01Departing employee with legitimate access copies [intellectual property] to a personal serviceConfidentialityT1567 Exfiltration Over Web ServiceCompetitive advantage, response
INS-02Administrator error deletes or corrupts [critical data] without malicious intentAvailabilityNot applicable (error event)Productivity, replacement
SUP-01Compromise of [software supplier or managed service provider] gives attacker access to our environmentIntegrityT1195 Supply Chain CompromiseResponse, productivity, reputation
NHI-01Leaked API key, token or service account secret lets an attacker read [system] without user interactionConfidentialityT1078.004 Cloud AccountsResponse, fines and judgements

Separating RAN-01 from RAN-02 matters because the controls differ: backups and recovery reduce the first, while egress controls and data minimisation reduce the second. The same logic splits BEC-01 into a supplier invoice variant and a payroll variant if payment approval controls differ. US data shows why BEC deserves its own entries: the FBI Internet Crime Complaint Center's 2024 report records 21,442 BEC complaints with about USD 2.77 billion in reported losses, second only to investment fraud by loss. Treat such figures as context for calibration, not as your frequency. See the Business Email Compromise Response Playbook and the Ransomware Response and Recovery Guide for the response side.

Where identity fits

Valid credentials appear in most of these scenarios, either as the vector (CLD-02, NHI-01) or as the step that turns access into impact (RAN-01, INS-01). Write machine credentials as their own scenario family rather than burying them inside "cloud breach": service accounts, CI/CD tokens and API keys have different owners, rotation controls and detection signals from human accounts. The NHI Risk Scoring Guide shows how to rank those identities so the NHI scenarios point at real populations.

Building and populating the library

  1. Start from the current register. Rewrite the top 10 to 15 entries as O-RA statements. Many will split into two or three scenarios; some will merge.
  2. Agree the threat community list. Define five to eight communities (for example extortion groups, fraudsters, state-aligned actors, malicious insiders, careless insiders, opportunistic scanners) with a fixed attribute list, as O-RA recommends, and reuse them everywhere.
  3. Anchor on assets and processes. Use the business impact analysis to name the processes whose disruption or disclosure would matter most. NIST IR 8286D covers that impact analysis.
  4. Gather frequency evidence. Internal incident and near-miss records first, then sector information sharing, then published industry data. Record each source against the estimate, since O-RA asks for the source of every estimate to be documented.
  5. Estimate ranges, not points. Capture minimum, most likely and maximum values for frequency and each relevant loss form, even if the register still shows a qualitative rating.
  6. Peer review. Have a second analyst and the risk owner challenge each scenario before it is published to the library.
  7. Publish and lock. Version the library; register entries reference a scenario version, so a later change does not silently rewrite past reports.

Pilot with three scenarios that leadership already worries about. Familiar scenarios are easier to sense-check, and agreement on them earns support for the method.

Choosing depth: qualitative, semi-quantitative or quantitative

ApproachWhat the library holdsGood fitTrade-off
QualitativeStatement, owner, controls, likelihood and impact ratingsSmall organisations, first year of a registerRatings cannot be aggregated or compared with cost
Semi-quantitativeRatings tied to defined numeric bands (for example "likely = once in 1 to 3 years")Mid-size organisations moving towards CRQBand edges hide large differences
Quantitative (FAIR)Frequency and loss distributions, simulation output, loss exceedance curveRegulated or large organisations; investment decisionsNeeds calibrated estimators and analyst time

A small organisation can run a useful library of 10 to 12 qualitative scenarios maintained by one person, as long as the scoping discipline holds. Larger organisations usually quantify the top 10 to 20 scenarios and keep the rest qualitative. Whatever the depth, CSF 2.0 GV.RM-06 expects a standardised method for calculating, documenting, categorising and prioritising cybersecurity risks, which the library provides. Tie impact bands to the Risk Appetite and Tolerance for Cyber Guide.

Keeping the library current

  • Calendar review: owners confirm each scenario at least annually; the top scenarios quarterly.
  • Threat triggers: a new technique against your sector, a relevant public breach or a sharp change in threat intelligence reopens the affected entries. CSF 2.0 ID.RA-03 expects internal and external threats to be identified and recorded.
  • Change triggers: migrations, acquisitions, new suppliers and new AI or automation deployments reopen scenarios that touch them, consistent with ID.RA-07 on assessing changes for risk impact.
  • Incident triggers: after any incident, compare what happened with the scenario that should have described it. If no scenario fits, add one.
  • Control triggers: a failed control test changes the assumptions behind every scenario that relies on it.

Detection and measurement

Link each scenario to the signals that would show its frequency changing. For example, RAN-01 to exposed remote access and unpatched edge devices, BEC-01 to mailbox rule creation and payment detail changes, NHI-01 to secrets found in repositories. These become key risk indicators; see the Key Risk Indicators for Cyber Risk Guide.

MetricWhat it showsTarget direction
Register entries linked to a library scenario IDAdoption of standard scenariosAbove 90 percent
Scenarios reviewed within their review intervalLibrary currency100 percent for top scenarios
Incidents mapped to an existing scenarioLibrary completenessRising; unmapped incidents trigger new entries
Scenarios with documented data sources for every estimateDefensibilityRising
Key controls per top scenario with a test result under 12 months oldWhether assumptions are evidencedRising
Decisions (budget, acceptance, treatment) citing a scenario IDWhether the library drives decisionsRising

Framework mapping

Library activityNIST CSF 2.0NIST SP 800-53 Rev. 5Other
Threat community profiles, threat triggersID.RA-03PM-16 Threat Awareness ProgramO-RA threat community attributes
Frequency and impact estimatesID.RA-04, ID.RA-05RA-3 Risk AssessmentO-RT factors; NIST IR 8286A Rev. 1
Standard method and taxonomyGV.RM-06PM-28 Risk FramingNIST IR 8286 Rev. 1 register schema
Roll-up to enterprise riskGV.RM-03PM-9 Risk Management StrategyNIST IR 8286C
Treatment linked to scenariosID.RA-06RA-7 Risk ResponseNIST IR 8286B
Supplier scenariosGV.SC (supply chain category)RA-3(1) Supply Chain Risk AssessmentThird-party risk programme
Change triggersID.RA-07RA-3ISO/IEC 27001:2022 clause 6.1.2 risk assessment

ATT&CK technique IDs in the scenario table were checked against ATT&CK v20.

Common failure patterns

  • Topics instead of scenarios: entries like "cloud risk" cannot be estimated or reduced. Rewrite them in O-RA form or remove them.
  • Library explosion: hundreds of near-duplicate scenarios that nobody reviews. Use parent and variant records and merge anything whose controls and loss profile are the same.
  • Double counting: the same ransomware exposure entered by IT, operations and a business unit, then summed. Shared scenario IDs and variants prevent this.
  • Industry statistics as frequencies: copying a national loss total or a survey percentage into your model. Use external data to sense-check, and your own exposure to estimate.
  • Undocumented assumptions: ranges with no source cannot be defended to an auditor or a board. O-RA's requirement to document every estimate source is the minimum.
  • No owner for machine identity scenarios: NHI-driven scenarios sit between platform, security and application teams and are never reviewed. Assign one named owner per scenario.

Practitioner checklist

  • Every library scenario is one O-RA style sentence naming threat community, asset, effect and loss event.
  • A fixed threat community list with attributes is reused across all scenarios.
  • Confidentiality, integrity and availability outcomes are separate scenarios.
  • Records map to the NIST IR 8286 register and risk detail record fields.
  • Each estimate has a documented data source and assumption.
  • Business unit variants inherit from a parent scenario to avoid double counting.
  • Review triggers (threat, change, incident, control failure) are defined and monitored.
  • Machine credential scenarios exist with named owners.
  • Register entries, CRQ models and tabletop exercises cite scenario IDs and versions.
  • Library adoption and currency metrics are reported to the risk committee.

Standards and references

Related NHI Mgmt Group resources: Risk Register Template · Cyber Risk Quantification Guide · NIST IR 8286 Cybersecurity and ERM Guide · FAIR-CAM Controls Analytics Model Guide · Insider Threat Programme Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.