Join our Newsletter — 33% off our NHI Course
Home› Guides› NIST SP 800-221 ICT Enterprise Risk Guide: Feeding…
Guide Regulations & Frameworks

NIST SP 800-221 ICT Enterprise Risk Guide: Feeding Cyber Risk into ERM

PDF for newsletter subscribers · free to read online

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

Security teams keep detailed risk registers, yet boards still see technology risk as a single red box with no link to the objectives it threatens. NIST Special Publication 800-221 and its companion SP 800-221A describe how to manage information and communications technology (ICT) risk as part of the enterprise risk portfolio, using risk registers that roll up from systems to organisations to the enterprise. This guide explains what each document contains, how they fit with the NIST IR 8286 series, what the Revision 1 draft of October 2026 changes, and how to build an ICT risk register that enterprise risk management (ERM) can actually use. It is written for CISOs, risk managers, ERM teams and auditors. Status was checked on the NIST Computer Security Resource Center on 27 October 2026.

Key takeaways

  • Two documents, two jobs. SP 800-221 (final, November 2023) explains how to govern and manage ICT risk programmes using risk registers; SP 800-221A (final, November 2023) gives the ICT Risk Outcomes Framework of outcomes to achieve.
  • ICT risk is wider than cyber. NIST defines it to include cybersecurity, privacy and supply chain risk, among others, so one register model serves several disciplines.
  • The register is the integration point. System-level risks are aggregated and normalised into discipline registers, combined into the enterprise risk register (ERR), and prioritised into the enterprise risk profile (ERP).
  • Revision 1 is in draft. SP 800-221 Rev. 1 initial public draft was published on 22 October 2026, with comments open until 7 December 2026. Build on the 2023 final and track the draft.
  • The IR 8286 series supplies the method. IR 8286 Rev. 1 and its parts A to D cover identifying, estimating, prioritising, staging and impact analysis of cybersecurity risk feeding the same registers.

What it is and who it applies to

SP 800-221, Enterprise Impact of Information and Communications Technology Risk: Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio, argues that enterprises should give ICT risk appropriate attention within ERM. It describes how to roll up risks addressed at lower system and organisational levels to the enterprise level, using ICT risk registers as input to the enterprise risk profile. SP 800-221A, Information and Communications Technology (ICT) Risk Outcomes: Integrating ICT Risk Management Programs with the Enterprise Risk Portfolio, provides a framework of outcomes that applies to all types of ICT risk.

  • US federal agencies: the documents are written in the context of OMB Circular A-123 and A-11 requirements for ERM and risk profiles. The Rev. 1 draft says it reflects OMB's 2026 revision of Circular A-123.
  • Private sector: nothing in the approach is federal-only. NIST names its primary audience as federal and non-federal professionals who understand ICT but may not know ERM well, and a secondary audience of executives and ERM staff who understand ERM but not ICT.
  • Status: both are NIST guidance, not regulation. They become binding only where a policy, contract or regulator adopts them.
PublicationTitle (short)Status as of 27 October 2026Role
SP 800-221Enterprise Impact of ICT RiskFinal, November 2023 (initial public draft July 2022)Governing and managing ICT risk programmes with risk registers
SP 800-221 Rev. 1Enterprise Impact of ICT RiskInitial public draft, 22 October 2026; comments to 7 December 2026Update for A-123 (2026), risk culture, risk capacity, quantification
SP 800-221AICT Risk OutcomesFinal, November 2023ICT Risk Outcomes Framework (Govern, Manage)
IR 8286 Rev. 1Integrating Cybersecurity and ERMFinal, December 2025Cybersecurity risk registers and roll-up
IR 8286A Rev. 1Identifying and Estimating Cybersecurity Risk for ERMFinal, December 2025Risk scenarios, likelihood and impact, appetite and tolerance examples
IR 8286B (update 1)Prioritizing Cybersecurity Risk for ERMFinal, February 2025Ranking risks and selecting responses
IR 8286C Rev. 1Staging Cybersecurity Risks for ERM and Governance OversightFinal, December 2025Combining registers into the ERR and ERP
IR 8286D (update 1)Using Business Impact Analysis to Inform Risk Prioritization and ResponseFinal, February 2025Business impact analysis feeding impact values

Structure and key requirements

The ICT risk management life cycle (SP 800-221)

SP 800-221 describes six steps, applied at each level and repeated continuously:

  1. Identify the context: mission, objectives, risk appetite and tolerance from leadership.
  2. Identify the risks: written in a cause and effect form, "if X occurs, then Y happens".
  3. Analyse the risks: likelihood, impact and the resulting exposure rating.
  4. Prioritise the risks: against enterprise objectives.
  5. Plan and execute risk responses: the appropriate response is determined for each risk, informed by risk guidance from leadership.
  6. Monitor, evaluate and adjust: the Monitor-Evaluate-Adjust cycle, using key risk indicators (KRIs) that show where tolerances have been exceeded or validate operation within appetite.

Appetite and tolerance

NIST draws a sharp distinction. Risk appetite, set by senior leadership, is "the broad-based amount of risk an organization is willing to accept in pursuit of its mission/vision". Risk tolerance is "the acceptable level of variance in performance relative to the achievement of objectives", and is always more specific. SP 800-221's own example maps a broad email availability appetite to a tolerance of no more than five minutes of interruption during core hours. See the Risk Appetite and Tolerance for Cyber Guide.

The ICT Risk Outcomes Framework (SP 800-221A)

The ICT ROF has two functions, not the six of CSF 2.0. Subcategories are numbered (for example GV.RR-1, MA.RM-4), each with an implementation example, and informative references are kept in NIST's Online Informative References (OLIR) catalogue.

FunctionCategoriesPurpose
Govern (GV)Context (GV.CT), Roles and Responsibilities (GV.RR), Policy (GV.PO), Benchmarking (GV.BE), Communication (GV.CO), Adjustments (GV.AD), Oversight (GV.OV)Sets the organisation's risk management logic and ensures risk management follows it
Manage (MA)Risk Identification (MA.RI), Risk Analysis (MA.RA), Risk Prioritization (MA.RP), Risk Response (MA.RR), Risk Monitoring, Evaluation, and Adjustment (MA.RM), Risk Communication (MA.RC), Risk Improvement (MA.IM)Continuously identifies and addresses risks under the organisation's policies, processes and priorities

Note that the ROF's GV prefix is not CSF 2.0's Govern function: GV.RR in SP 800-221A and GV.RR in CSF 2.0 are different identifiers in different documents. Always cite the publication with the ID.

Several ROF outcomes set a cadence. GV.CO-1 says ERR information forms the basis for a quarterly ERP update; GV.CO-3 and MA.RC-2 cover escalating risks under criteria set by the ERM committee; GV.OV-7 covers programmes giving feedback on appetite and priorities; MA.IM-1 covers reporting lessons learned to leadership quarterly.

Registers and the roll-up

ArtefactLevelContentOwner
ICT risk register (IRR)System and organisationID, priority, risk description, risk category, current likelihood, impact and exposure rating; optionally residual and target residual riskSystem owners, discipline risk managers
Discipline register (cyber, privacy, supply chain)Enterprise, per disciplineAggregated and normalised IRR entries in the enterprise formatDiscipline risk leads (for example CISO)
Enterprise risk register (ERR)EnterpriseDiscipline registers combined with non-ICT registers after normalisationERM function
Enterprise risk profile (ERP)EnterprisePrioritised view covering strategic, operations, reporting and compliance objectives, with positive (opportunities) and negative (threats) uncertaintyThose with fiduciary and oversight responsibility

The enterprise risk strategy defines the terminology, formats and criteria for inputs from lower levels. Without that, roll-up becomes a translation exercise every quarter. SP 800-221 also insists that positive risks go through the same process, warning that ignoring them can lead to over-investing in the corresponding negative risks.

What the Revision 1 draft changes

  • Reflects OMB's 2026 revision of Circular A-123.
  • Revised sections on risk culture, risk capacity and comprehensive risk assessment.
  • Stronger alignment with IR 8286 Rev. 1.
  • Guidance on using the risk register for risk-informed workforce decisions, referencing NIST SP 1308.
  • Recognition of multiple ways to quantify risk, within disciplines and in aggregate.

The draft may change before final publication. Treat its content as direction, not as settled requirements.

Identity and NHI requirements

SP 800-221 does not set identity controls; it sets how identity risk should be expressed so it reaches the enterprise. Identity risk is a good test of a register, because the causes are technical (an over-privileged service account, a long-lived API key) but the effects are business outcomes. Practical rules:

  • Write identity risks in cause and effect form: "If a long-lived cloud access key with production write access is exposed in a code repository, then an attacker can alter customer data, breaching the availability tolerance for the order platform." Vague entries such as "weak IAM" cannot be rolled up.
  • Link to the objective: the effect should name the business objective or tolerance it threatens, so the ERM team can place it in the ERP.
  • Use the identity inventory for likelihood: counts of unowned, dormant and over-privileged non-human identities give evidence for likelihood instead of opinion. See the Non-Human Identity (NHI) Guide.
  • Define KRIs with thresholds: for example "privileged non-human identities without an owner: tolerance zero for more than 30 days". KRIs are what show a tolerance has been exceeded. See the Key Risk Indicators for Cyber Risk Guide.
  • Treat supplier access as ICT risk: SP 800-221A's scope includes supply chain risk, so third-party integrations and OAuth grants belong in the register, not only in procurement files.

In the Change Healthcare Breach 2024, a single remote access login without MFA became an enterprise-wide outage. That is the kind of system-level cause whose enterprise effect a well-built register should have made visible before the event.

Implementation steps

  1. Get the enterprise rules first. Ask ERM for the enterprise risk strategy: categories, likelihood and impact scales, exposure rating method, appetite statements and the register template. If none exists, agree them jointly before collecting risks.
  2. Derive tolerances. Turn each relevant appetite statement into measurable tolerances for ICT (availability minutes, records exposed, days to remediate). Use business impact analysis to set impact values, as IR 8286D describes. See the Business Impact Analysis Template.
  3. Build the ICT register. Use the notional fields (ID, priority, description, category, likelihood, impact, exposure rating, optionally residual and target residual risk) and add response and owner columns. Start with a pilot business unit and 20 to 40 well-written risks rather than hundreds of findings. See the Risk Register Template.
  4. Estimate consistently. Apply one method across the register (qualitative scales or quantitative estimates); IR 8286A gives scenario-based examples. If you quantify, see the Cyber Risk Quantification Guide.
  5. Prioritise and choose responses. Rank against enterprise objectives (IR 8286B) and record the response, cost and owner for each risk.
  6. Aggregate and normalise. Combine system registers into the discipline register using the enterprise terminology, then hand it to ERM for the ERR (IR 8286C).
  7. Set the reporting rhythm. Quarterly ERP input, with escalation criteria agreed with the ERM committee so urgent risks do not wait for the quarter.
  8. Monitor, evaluate and adjust. Track KRIs against tolerances, review residual risk after responses, and feed lessons learned upward.

Testing the design: before full rollout, take three recent incidents or near misses and check whether the register would have shown them, at what level, and whether the escalation criteria would have fired. Adjust categories and criteria, not the incident facts.

Evidence and assessment

Auditors and internal audit will look for the chain from system risk to enterprise decision. Evidence that demonstrates it:

OutcomeEvidenceRed flag
Context and appetite set (GV.CT, GV.PO)Approved appetite statements and derived ICT tolerancesAppetite exists but no measurable tolerances
Roles assigned (GV.RR)Named risk owners for each register entry, with authority to acceptThe CISO owns every risk
Consistent analysis (MA.RA)One documented scale or model used across the registerEach team scores differently
Responses tracked (MA.RR)Response, cost, due date and status per riskResponses listed as "mitigate" with no plan
Communication (GV.CO, MA.RC)Quarterly ERP submissions and escalation recordsNo ICT risks appear in the ERP
Monitoring (MA.RM)KRI dashboards with thresholds and breach historyMetrics with no threshold

Mapping to other frameworks

SP 800-221 / 800-221A conceptNIST CSF 2.0NIST SP 800-53 Rev. 5Other
Risk objectives and contextGV.RM-01PM-28 Risk FramingISO 31000 context
Appetite and toleranceGV.RM-02PM-9 Risk Management StrategyOMB A-123
ICT risk in ERMGV.RM-03PM-9IR 8286 series
Standard calculation and prioritisation methodGV.RM-06RA-3 Risk AssessmentIR 8286A, 8286B
Risk analysis and responseID.RA-05, ID.RA-06RA-3, RA-7 Risk ResponseSP 800-30
Supplier risk in the registerGV.SC-07PM-30, SR-6SP 800-161
Oversight and adjustmentGV.OV-01CA-7 Continuous MonitoringMonitor-Evaluate-Adjust

SP 800-221A describes the CSF, Privacy Framework and SSDF as containing outcomes that are "more specific instances" of its more general outcomes. In practice: use the ROF to run the risk programme, and CSF 2.0 for the cybersecurity outcomes inside it. For related methods see the NIST SP 800-30 Risk Assessment Guide, the NIST Risk Management Framework (SP 800-37) Guide and the ISO 31000 Risk Management Guide.

Detection and measurement

  • Register coverage: percentage of critical systems and business units with a current ICT register entry set.
  • ERP inclusion: number of ICT risks reaching the ERP each quarter, and how many were escalated outside the cycle.
  • Tolerance breaches: KRIs breaching tolerance, and median time from breach to decision.
  • Response delivery: percentage of risk responses on schedule, and residual risk against target residual risk.
  • Owner quality: share of risks with a named owner who has authority to accept the risk.

Common pitfalls

  • Exporting vulnerability findings as risks. Thousands of scanner findings are not a register. Write scenarios with business effects and keep findings as evidence.
  • No common scale. When each team scores differently, aggregation produces nonsense. The enterprise strategy must fix terminology and formats first.
  • Appetite with no tolerance. "Low appetite for data loss" cannot be monitored. Derive measurable tolerances and KRIs.
  • Ignoring positive risk. SP 800-221 warns that neglecting opportunities drives over-investment in negative risks.
  • Confusing the GV identifiers. Mixing SP 800-221A and CSF 2.0 Govern IDs in one mapping misleads auditors.
  • Treating the Rev. 1 draft as final. Plan on the 2023 final and note draft-driven changes separately.

Practitioner checklist

  • Obtain the enterprise risk strategy, scales and register template from ERM.
  • Derive measurable ICT tolerances from each relevant appetite statement.
  • Write every register entry in "if X occurs, then Y happens" form with a business effect.
  • Include identity, supplier and privacy risks, not only cyber controls gaps.
  • Assign owners with authority to accept risk.
  • Agree quarterly ERP input and out-of-cycle escalation criteria.
  • Define KRIs with thresholds for each high-priority risk.
  • Map your programme to SP 800-221A outcomes and CSF 2.0 GV.RM separately.
  • Review the SP 800-221 Rev. 1 draft and decide whether to comment by 7 December 2026.

Standards and references

Related NHI Mgmt Group resources: Cyber Risk Quantification Guide · Risk Management Guide · Risk Register Template · Key Risk Indicators for Cyber Risk 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.