NIST.CSF 2.0
NIST.CSF 2.0
0:
Enterprise Risk Management
Quick-Start Guide
CSF 2.0 provides guidance for reducing cybersecurity risks by helping organizations discuss, organize, and address gaps in their cybersecurity program in a standard way. The cybersecurity
outcomes described in CSF affect cybersecurity, ICT, and enterprise risks. Understanding these dependencies is an essential activity in CSRM, ICT RM, and ERM. The Cybersecurity Risk
Register (CSRR) described in the NIST IR 8286 series of publications enables organizations to identify, manage, and monitor the relationships between discrete risks and aspects of a CSF-
based cybersecurity program that address those risks. The CSRR allows organizations to identify, organize, analyze, and report on cybersecurity risks at the system level. CSF Organizational
Profiles are a natural byproduct of a comprehensive CSRR, because the relative priority of CSF outcomes becomes apparent based on how significant the impacts of identified cybersecurity
risks might be to the organization’s priorities, such as its strategic objectives, products and services, or customers.
NIST Cybersecurity Framework 2.0: Enterprise Risk Management Quick-Start Guide
CSF 2.0 Supports Six Activity Points For Informing,
Implementing, and Monitoring ERM
CSF 2.0 is a valuable guide for helping to review and improve security and privacy considerations as
part of a holistic enterprise risk approach. CSF is most helpful when it is paired with other ERM
elements. For example, as agency officials and corporate boards provide oversight of all relevant
risks, the CSF process helps ensure that cybersecurity strategy is well-executed. Managers plan and
implement risk treatment based on that strategy, record and report progress, and provide agency/
business leaders with information needed for effective operations and mission success.
The Activity Points, which are further described in subsequent pages, include:
• 1 – Leaders define and record enterprise mission, priorities, and risk appetite. Accountability is
assigned for managing both positive and negative types of risk. (GV.OC, GV.RM, GV.SC)
• 2 – Organization-level managers interpret risk appetite into specific guidance regarding security
and privacy requirements, and associated risk tolerance. (GV.RR, GV.PO, ID.RA)
• 3 – Risk strategy and requirements aid implementation of shared security solutions and system-
level controls to achieve an acceptable level of risk. (PROTECT, DETECT, RESPOND, and RECOVER)
• 4 – Risk response outcomes are reflected as residual risk in system-level risk registers as part of
ongoing assessment and continuous monitoring activities. (ID.RA, ID.IM, GV.OV)
Illustration of enterprise risk management integration and coordination
• 5 – Risk registers are normalized and aggregated at the organizational unit level, supporting
from NIST SP 800-221
reporting, analysis, and organization-level adjustment. (ID.IM, GV.OV)
• 6 – Combined risk results from the enterprise are used to maintain an enterprise-level risk
register and risk profile, supporting enterprise business decisions and any adjustments needed
CSF 2.0, as part of a holistic ERM approach, for the risk strategy. (GV.PO, GV.OV)
helps ensure that leaders continually have the Supporting Resources:
information they need for making informed • SP 800-221, Enterprise Impact of Information and Communications Technology Risk: Governing and
Managing ICT Risk Programs Within an Enterprise Risk Portfolio
business/agency decisions. • SP 800-221A, Information and Communications Technology (ICT) Risk Outcomes: Integrating ICT Risk
Management Programs with the Enterprise Risk Portfolio
NIST Cybersecurity Framework 2.0: Enterprise Risk Management Quick-Start Guide
Based on internal and external organizational context, leaders
Aligning enterprise priorities with strategic activity use governance systems to set risk priorities, risk appetite,
and risk strategy. This understanding sets the tone for how the
As senior leaders and organizational managers observe and enterprise conducts, measures, and reports risk management activities and
performance. Actions include processes for aligning priorities and risk direction for
discuss risk management strategy (to take advantage of business partners and other members of the organization’s cybersecurity supply chain.
opportunities and to avoid known threats), they develop a
plan for managing risk to the optimal level. Understanding of objectives and risk appetite enables managers to interpret how to
apply those for their organizational units (OUs). Managers create risk tolerance
statements and metrics, defining a “target state” that will achieve stakeholder
The outcomes in the CSF Govern Function (GV) specifically objectives such as through secure shared infrastructure (e.g., organizationally-tailored
drive actionable planning about how to best manage control baselines, common controls, and monitoring strategy).
various enterprise risks to ICT, including privacy, supply
chain, AI, IoT, and OT on which the entity depends. The direction from leadership and OU management is applied in an operational
context, supporting system-level risk assessment, requirements definition, and
allocation. These enable effective categorization, control selection/implementation,
Beginning with an understanding of what information and and ongoing system-level authorization/monitoring.
technology are most important to the enterprise mission,
leaders define acceptable levels of risk for those assets and Questions to Consider
describe how personnel in various work roles will be Activity Point 1: Where do you draw the mission and strategic priorities of the organization from?
accountable for risk management success. (ID.AM, ID.RA) Do you have a process for defining and expressing risk appetite?
Activity Point 2: How is risk appetite translated into risk tolerance?
This actionable and proactive strategizing also makes clear Are cybersecurity risk management strategy outcomes reviewed to inform and adjust strategy and direction?
to customers and other stakeholders that effective risk Activity Point 3: How are organizational priorities, definition of acceptable risk, and performance requirements
management is a priority, that clear and accountable plans embedded in your system-level risk activities?
are in place to achieve that management, and that Are these translated into control selection, system constraints, reporting requirements, and anomaly detection?
monitoring processes are continually identifying
opportunities for improvement. These plans specifically Related Resources
apply the outcomes described in the CSF Organizational • NIST Risk Management Framework (RMF) for Information System and Organizations - a comprehensive, flexible,
Profile(s), in particular the PROTECT, DETECT, RESPOND, and repeatable, and measurable process to manage information security and privacy risk
RECOVER functions. • NIST IR 8286 series – specifically NIST IR 8286A - Identifying and Estimating Cybersecurity Risk for ERM
• NIST SP 800-30 Rev. 1 – Guide for Conducting Risk Assessments
NIST Cybersecurity Framework 2.0: Enterprise Risk Management Quick-Start Guide
Risk Assessment, Risk Treatment, and Information Sharing Ensure Value and Risk Optimization
Select Risk Response
After selecting and implementing controls and other methods of risk treatment, system-level personnel assess the effectiveness and efficiency of
that treatment (e.g., through the Assess step of the NIST Risk Management Framework). Risk managers evaluate threats and opportunities, in
alignment with risk strategy and direction from enterprise- and organization-level guidance. They determine the benefits of the following
responses: Mitigate, Accept, Avoid, and Transfer for negative risks; Realize, Share, Enhance, and Accept for positive risks.
Analyze and Prioritize Risks
There are benefits to both qualitative and quantitative risk analysis methodologies and even the use of multiple methodologies, based on
enterprise strategy, organization preference, and data availability (ID.RA). The relative priority of various types of risk must be decided upon by
those with appropriate authority, usually through guidance provided through the risk management strategy (GV.RM).
Communicate Risk Findings and Decisions
The cybersecurity risk register (CSRR) provides a location to record and communicate the known system-level threats and vulnerabilities, their
impact on business objectives, and the responses taken or planned. Risk managers share information about residual risk, including metrics that
support ongoing assessment and authorization, and plans of actions & milestones for maintaining the appropriate level of risk based on
stakeholders’ expectations (as expressed in the target state of the Organizational Profiles, especially the GOVERN and IDENTIFY functions).
Questions to Consider
How do CSF Target Profile outcomes (organizational agreement on how to best protect,
detect, respond, and recover) inform system-specific risk assessment and treatment?
How can we estimate likelihood and impact of those risks given the planned outcomes and
knowledge from previous results?
Is our risk response proportionate to the exposure?
Related Resources
• SP 800-221, Enterprise Impact of Information and Communications Technology Risk: Governing
and Managing ICT Risk Programs Within an Enterprise Risk Portfolio
• NIST IR 8286A, Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management
• Risk Detail Schema Risk Detail CSRR Schema
NIST Cybersecurity Framework 2.0: Enterprise Risk Management Quick-Start Guide
Feedback from CSF Informative References and the MEA cycle help
monitor and adjust risk response, appetite/tolerance, and policy.
As risk management controls are operated, performance is evaluated and adjusted
to improve effectiveness and efficiency. Feedback from the MEA cycle sometimes
results in more than just adjustments to controls and other Informative References.
Feedback may lead to adjustments in:
• CSF Profile • Risk Tolerance
• Risk Detail Record • Risk Appetite
• Risk Response Description • Policy
• Risk Response • Strategy
This helps report results back to management and enterprise leadership. Results that
particularly reflect operational achievement (key performance indicators, or KPIs)
confirm conformance with the strategy (GV.RM, GV.SC). This also supports personnel
performance monitoring and reporting (GV.RR, GV.PO).
Managers integrate data from normalized and harmonized risk registers and from
organization-level reports, compliance and audit reports. These are considered in
light of non-technology risk management activities (e.g., credit risk, market risk, labor
Questions to Consider
risk). Considering composite outcomes of positive and negative risk management
enables effective balance among investments in and results of risk management How are top cybersecurity risks identified for leadership and recorded in the enterprise risk
activity. Results are reflected in an enterprise risk register (ERR) and an enterprise register?
risk profile (ERP) that provides a prioritized ERR. Are escalation criteria defined to ensure accountability and information sharing? (NIST IR
8286C)
In this way, CSF helps to guide the selection, implementation, and monitoring of Are processes in place to marry system/organization-level risk to enterprise-level
specific controls (such as those in the informative references), and the results ensure considerations?
an effective and ongoing holistic ERM solution for all types of risk. How are enterprise security and privacy risks (including opportunities) aligned with other risk
types?
NIST Cybersecurity Framework 2.0: Enterprise Risk Management Quick-Start Guide
What We Learned* EXPLORE MORE CSF
Risk Appetite – statements expressing a general way of defining risk you can accept
2.0 RESOURCES
Risk Tolerance – statements expressing a specific way of defining risk you cannot accept • CSF 2.0 website
Risk Identification – the process of understanding your risks • CSF 2.0 Organizational
Enterprise Risk Management – the process of managing general high-level risk Profiles
Information and Communications Technology Risk Management – the process of managing various ICT risks • Informative References
• SP 800-53 – security and
Cybersecurity Risk Management – the process of managing specific cybersecurity risks
privacy controls
CSF Govern – one of six high-level outcomes expressed in CSF; oversight to ensure cybersecurity is managed
• SP 800-221 – Integrating ICT
Negative Risks – things that are weaknesses or threats risk management and ERM
Positive Risks – things that are strengths or opportunities • SP 800-221A – Outcome
Framework for Integrating
Cybersecurity Risk Register – a list of your high-priority cybersecurity risks
ICT RM and ERM
Risk Response Description – the place in the CSRR where you note CSF outcomes and Informative Reference implementations
• IR 8286 – Overview of
Cybersecurity Framework Outcome – what cybersecurity capabilities (or activities) you are trying to achieve integrating CSRM and ERM
Informative Reference Implementation – how you implement cybersecurity • IR 8286A – Deep dive on
risk registers
Online Informative References – a catalog of Informative References hosted at a NIST website
• IR 8286B – Prioritizing and
SP 800-53 Control – a security or privacy control from the NIST Special Publication 800-53 controls catalog treating risk responses
Monitor, Evaluate, Adjust – how you actualize cybersecurity; in a Deming Cycle, this is the do, check, act • IR 8286C – Integrating the
Feedback Loop – how you make adjustments and improvements CSF with ERM
*Descriptions provided are intended as plain language. Please see the NIST Glossary for official NIST definitions. • IR 8286D – BIA’s role in ERM