NIST Cybersecurity Framework 2.0
Voluntary framework for managing and reducing cybersecurity risk, organized around six core functions
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (12)
DE - Detect
Find and analyze possible cybersecurity attacks and compromises
| Code | Title |
|---|---|
| NIST-CSF-DE.AE-02 | Potentially adverse events are analyzed to better understand associated activities |
| NIST-CSF-DE.AE-03 | Information is correlated from multiple sources |
| NIST-CSF-DE.AE-04 | Estimated impact and scope of adverse events are understood |
| NIST-CSF-DE.AE-06 | Information on adverse events is provided to authorized staff |
| NIST-CSF-DE.AE-07 | Cyber threat intelligence and contextual information are integrated into analysis |
| NIST-CSF-DE.AE-08 | Incidents are declared when adverse events meet defined criteria |
| NIST-CSF-DE.CM-01 | Networks and network services are monitored to find potentially adverse events |
| NIST-CSF-DE.CM-02 | The physical environment is monitored to find potentially adverse events |
| NIST-CSF-DE.CM-03 | Personnel activity and technology usage are monitored to find potentially adverse events |
| NIST-CSF-DE.CM-06 | External service provider activities are monitored to find potentially adverse events |
| NIST-CSF-DE.CM-09 | Computing hardware and software are monitored to find potentially adverse events |
Detect
| Code | Title |
|---|---|
| DE.AE-02 | Adverse events are analyzed to understand activities |
| DE.AE-03 | Information is correlated from multiple sources |
| DE.AE-04 | Impact and scope of adverse events are understood |
| DE.AE-06 | Adverse event information is provided to authorized staff |
| DE.AE-07 | Threat intelligence is integrated into event analysis |
| DE.AE-08 | Incidents are declared based on defined criteria |
| DE.CM-01 | Networks and network services are monitored |
| DE.CM-02 | Physical environment is monitored |
| DE.CM-03 | Personnel activity and technology usage are monitored |
| DE.CM-06 | External service provider activities are monitored |
| DE.CM-09 | Computing hardware, software, runtime, and data are monitored |
GV - Govern
Establish and monitor cybersecurity risk management strategy, expectations, and policy
| Code | Title |
|---|---|
| NIST-CSF-GV.OC-01 | Organizational context for cybersecurity risk management is understood |
| NIST-CSF-GV.OC-02 | Internal and external stakeholders are understood |
| NIST-CSF-GV.OC-03 | Legal, regulatory, and contractual requirements are understood |
| NIST-CSF-GV.OC-04 | Critical objectives, capabilities, and services are understood |
| NIST-CSF-GV.OC-05 | Outcomes and dependencies of critical services are understood |
| NIST-CSF-GV.PO-01 | Cybersecurity risk management policy is established based on context and strategy |
| NIST-CSF-GV.PO-02 | Policy is reviewed, updated, communicated, and enforced |
| NIST-CSF-GV.RM-01 | Risk management objectives are established and agreed upon |
| NIST-CSF-GV.RM-02 | Risk appetite and risk tolerance statements are established |
| NIST-CSF-GV.RM-03 | Cybersecurity risk management activities and outcomes are included in enterprise risk |
| NIST-CSF-GV.RM-04 | Strategic direction for cybersecurity risk management is established |
| NIST-CSF-GV.RM-05 | Communication lines for cybersecurity risk management are established |
| NIST-CSF-GV.RM-06 | A standardized method for calculating and expressing cybersecurity risk is established |
| NIST-CSF-GV.RM-07 | Opportunities for improvements are identified from risk assessments |
| NIST-CSF-GV.RR-01 | Organizational leadership is responsible for cybersecurity risk management |
| NIST-CSF-GV.RR-02 | Roles and responsibilities for cybersecurity risk management are established |
| NIST-CSF-GV.RR-03 | Adequate resources are allocated for cybersecurity risk management |
| NIST-CSF-GV.RR-04 | Cybersecurity is included in human resources practices |
| NIST-CSF-GV.SC-01 | Cybersecurity supply chain risk management program is established |
| NIST-CSF-GV.SC-02 | Cybersecurity roles and responsibilities for suppliers are established |
| NIST-CSF-GV.SC-03 | Supply chain risk management is integrated into risk management |
| NIST-CSF-GV.SC-04 | Suppliers are known and prioritized by criticality |
| NIST-CSF-GV.SC-05 | Requirements are established and managed for suppliers |
| NIST-CSF-GV.SC-06 | Planning and due diligence are performed to reduce supply chain risks |
| NIST-CSF-GV.SC-07 | Supply chain risk management is verified throughout supplier relationships |
| NIST-CSF-GV.SC-08 | Relevant suppliers and partners are included in incident planning |
| NIST-CSF-GV.SC-09 | Supply chain security practices are integrated into security program |
| NIST-CSF-GV.SC-10 | Cybersecurity supply chain risk management plans include provisions for post-acquisition activities |
Govern
| Code | Title |
|---|---|
| GV.OC-01 | Organizational mission informs cybersecurity risk management |
| GV.OC-02 | Internal and external stakeholders are understood |
| GV.OC-03 | Legal, regulatory, and contractual requirements are understood and managed |
| GV.OC-04 | Critical objectives, capabilities, and services external stakeholders depend on are understood |
| GV.OC-05 | Outcomes, capabilities, and services organization depends on are understood |
| GV.OV-01 | Risk management strategy outcomes are reviewed |
| GV.OV-02 | Risk management strategy is reviewed for coverage |
| GV.OV-03 | Risk management performance is evaluated |
| GV.PO-01 | Policy for managing cybersecurity risks is established |
| GV.PO-02 | Policy is reviewed, updated, communicated, and enforced |
| GV.RM-01 | Risk management objectives are established and agreed |
| GV.RM-02 | Risk appetite and tolerance statements are established |
| GV.RM-03 | Cybersecurity risk is included in enterprise risk management |
| GV.RM-04 | Strategic direction for risk response options is established |
| GV.RM-05 | Lines of communication for cybersecurity risks are established |
| GV.RM-06 | Standardized risk calculation method is established |
| GV.RM-07 | Strategic opportunities are characterized as positive risks |
| GV.RR-01 | Organizational leadership is responsible and accountable for cybersecurity risk |
| GV.RR-02 | Roles, responsibilities, and authorities are established |
| GV.RR-03 | Adequate resources are allocated to cybersecurity |
| GV.RR-04 | Cybersecurity is included in human resources practices |
| GV.SC-01 | Cybersecurity supply chain risk management program is established |
| GV.SC-02 | Roles and responsibilities for suppliers are established |
| GV.SC-03 | C-SCRM is integrated into cybersecurity and ERM |
| GV.SC-04 | Suppliers are known and prioritized by criticality |
| GV.SC-05 | Supply chain requirements are in contracts |
| GV.SC-06 | Pre-engagement due diligence is performed |
| GV.SC-07 | Supplier risks are managed over the relationship |
| GV.SC-08 | Suppliers are included in incident response |
| GV.SC-09 | Supply chain security practices are integrated through the lifecycle |
| GV.SC-10 | C-SCRM plans cover end-of-relationship activities |
ID - Identify
Understand current cybersecurity risks to the organization
| Code | Title |
|---|---|
| NIST-CSF-ID.AM-01 | Inventories of hardware managed by the organization are maintained |
| NIST-CSF-ID.AM-02 | Inventories of software, services, and systems managed by the organization are maintained |
| NIST-CSF-ID.AM-03 | Representations of authorized network communication and data flows are maintained |
| NIST-CSF-ID.AM-04 | Inventories of services provided by suppliers are maintained |
| NIST-CSF-ID.AM-05 | Assets are prioritized based on classification, criticality, resources, and impact |
| NIST-CSF-ID.AM-07 | Inventories of data and corresponding metadata are maintained |
| NIST-CSF-ID.AM-08 | Systems, hardware, software, and services are managed throughout their life cycles |
| NIST-CSF-ID.IM-01 | Improvements are identified from security test and exercise results |
| NIST-CSF-ID.IM-02 | Improvements are identified from security assessments |
| NIST-CSF-ID.IM-03 | Improvements are identified from operational activities and incidents |
| NIST-CSF-ID.IM-04 | Incident response plans and other cybersecurity plans are established and maintained |
| NIST-CSF-ID.RA-01 | Vulnerabilities in assets are identified, validated, and recorded |
| NIST-CSF-ID.RA-02 | Cyber threat intelligence is received from information sharing forums |
| NIST-CSF-ID.RA-03 | Internal and external threats are identified and recorded |
| NIST-CSF-ID.RA-04 | Potential impacts and likelihoods of threats exploiting vulnerabilities are identified |
| NIST-CSF-ID.RA-05 | Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk |
| NIST-CSF-ID.RA-06 | Risk responses are chosen, prioritized, planned, tracked, and communicated |
| NIST-CSF-ID.RA-07 | Changes and exceptions are managed, assessed for risk impact, recorded, and tracked |
| NIST-CSF-ID.RA-08 | Effectiveness of risk responses is assessed |
| NIST-CSF-ID.RA-09 | Integrity and accuracy of risk assessment results are verified |
| NIST-CSF-ID.RA-10 | Critical suppliers are assessed on the basis of their risk |
Identify
| Code | Title |
|---|---|
| ID.AM-01 | Inventories of hardware are maintained |
| ID.AM-02 | Inventories of software, services, and systems are maintained |
| ID.AM-03 | Network communication and data flows are maintained |
| ID.AM-04 | Inventories of supplier services are maintained |
| ID.AM-05 | Assets are prioritized by classification and criticality |
| ID.AM-07 | Inventories of data and metadata are maintained |
| ID.AM-08 | Systems, hardware, software, services, and data are managed throughout life cycles |
| ID.IM-01 | Improvements are identified from evaluations |
| ID.IM-02 | Improvements are identified from security tests and exercises |
| ID.IM-03 | Improvements are identified from operational processes |
| ID.IM-04 | Incident response and cybersecurity plans are established and improved |
| ID.RA-01 | Vulnerabilities are identified, validated, and recorded |
| ID.RA-02 | Cyber threat intelligence is received |
| ID.RA-03 | Internal and external threats are identified |
| ID.RA-04 | Impacts and likelihoods are identified |
| ID.RA-05 | Inherent risk informs response prioritization |
| ID.RA-06 | Risk responses are chosen and tracked |
| ID.RA-07 | Changes and exceptions are managed |
| ID.RA-08 | Vulnerability disclosure processes are established |
| ID.RA-09 | Authenticity and integrity of hardware and software are assessed |
| ID.RA-10 | Critical suppliers are assessed prior to acquisition |
PR - Protect
Use safeguards to prevent or reduce cybersecurity risk
| Code | Title |
|---|---|
| NIST-CSF-PR.AA-01 | Identities and credentials for authorized users, services, and hardware are managed |
| NIST-CSF-PR.AA-02 | Identities are proofed and bound to credentials based on the context of interactions |
| NIST-CSF-PR.AA-03 | Users, services, and hardware are authenticated |
| NIST-CSF-PR.AA-04 | Identity assertions are protected, conveyed, and verified |
| NIST-CSF-PR.AA-05 | Access permissions, entitlements, and authorizations are defined and managed |
| NIST-CSF-PR.AA-06 | Physical access to assets is managed, monitored, and enforced |
| NIST-CSF-PR.AT-01 | Personnel are provided awareness and training to perform cybersecurity duties |
| NIST-CSF-PR.AT-02 | Individuals in specialized roles are provided awareness and training |
| NIST-CSF-PR.DS-01 | The confidentiality, integrity, and availability of data-at-rest are protected |
| NIST-CSF-PR.DS-02 | The confidentiality, integrity, and availability of data-in-transit are protected |
| NIST-CSF-PR.DS-10 | The confidentiality, integrity, and availability of data-in-use are protected |
| NIST-CSF-PR.DS-11 | Backups of data are created, protected, maintained, and tested |
| NIST-CSF-PR.IR-01 | Networks and environments are protected from unauthorized access |
| NIST-CSF-PR.IR-02 | The organization's technology assets are protected from environmental threats |
| NIST-CSF-PR.IR-03 | Mechanisms are implemented to achieve resilience requirements in normal and adverse situations |
| NIST-CSF-PR.IR-04 | Adequate resource capacity to ensure availability is maintained |
| NIST-CSF-PR.PS-01 | Configuration management practices are established and applied |
| NIST-CSF-PR.PS-02 | Software is maintained, replaced, and removed commensurate with risk |
| NIST-CSF-PR.PS-03 | Hardware is maintained, replaced, and removed commensurate with risk |
| NIST-CSF-PR.PS-04 | Log records are generated and made available for continuous monitoring |
| NIST-CSF-PR.PS-05 | Installation and execution of unauthorized software is prevented |
| NIST-CSF-PR.PS-06 | Secure software development practices are integrated throughout the SDLC |
Protect
| Code | Title |
|---|---|
| PR.AA-01 | Identities and credentials are managed |
| PR.AA-02 | Identities are proofed and bound to credentials |
| PR.AA-03 | Users, services, and hardware are authenticated |
| PR.AA-04 | Identity assertions are protected and verified |
| PR.AA-05 | Access permissions enforce least privilege and separation of duties |
| PR.AA-06 | Physical access is managed |
| PR.AT-01 | Personnel receive cybersecurity awareness and training |
| PR.AT-02 | Specialized roles receive tailored training |
| PR.DS-01 | Confidentiality, integrity, and availability of data-at-rest are protected |
| PR.DS-02 | Confidentiality, integrity, and availability of data-in-transit are protected |
| PR.DS-10 | Confidentiality, integrity, and availability of data-in-use are protected |
| PR.DS-11 | Backups are created, protected, maintained, and tested |
| PR.IR-01 | Networks and environments are protected from unauthorized access |
| PR.IR-02 | Technology assets are protected from environmental threats |
| PR.IR-03 | Mechanisms support resilience in normal and adverse situations |
| PR.IR-04 | Adequate resource capacity is maintained |
| PR.PS-01 | Configuration management practices are established |
| PR.PS-02 | Software is maintained, replaced, and removed commensurate with risk |
| PR.PS-03 | Hardware is maintained, replaced, and removed commensurate with risk |
| PR.PS-04 | Log records are generated for continuous monitoring |
| PR.PS-05 | Unauthorized software is prevented |
| PR.PS-06 | Secure software development practices are integrated |
RC - Recover
Restore assets and operations affected by a cybersecurity incident
| Code | Title |
|---|---|
| NIST-CSF-RC.CO-03 | Recovery activities and progress are communicated to stakeholders |
| NIST-CSF-RC.CO-04 | Public updates on incident recovery are shared using approved methods |
| NIST-CSF-RC.RP-01 | The recovery portion of the incident response plan is executed |
| NIST-CSF-RC.RP-02 | Recovery actions are selected, scoped, and prioritized |
| NIST-CSF-RC.RP-03 | The integrity of backups is verified before use in restoration |
| NIST-CSF-RC.RP-04 | Critical functions and services are restored to operational capability |
| NIST-CSF-RC.RP-05 | Integrity of restored assets is verified |
| NIST-CSF-RC.RP-06 | End-of-recovery is declared based on criteria and documentation |
RS - Respond
Take action regarding a detected cybersecurity incident
| Code | Title |
|---|---|
| NIST-CSF-RS.AN-03 | Analysis is performed to determine what has taken place during an incident |
| NIST-CSF-RS.AN-06 | Actions performed during an investigation are recorded |
| NIST-CSF-RS.AN-07 | Incident data and metadata are collected and their integrity preserved |
| NIST-CSF-RS.AN-08 | Incidents are analyzed to determine root cause |
| NIST-CSF-RS.CO-02 | Internal and external stakeholders are notified of incidents |
| NIST-CSF-RS.CO-03 | Information is shared with designated internal and external stakeholders |
| NIST-CSF-RS.MA-01 | The incident response plan is executed in coordination with relevant third parties |
| NIST-CSF-RS.MA-02 | Incident reports are triaged and validated |
| NIST-CSF-RS.MA-03 | Incidents are categorized and prioritized |
| NIST-CSF-RS.MA-04 | Incidents are escalated or elevated as needed |
| NIST-CSF-RS.MA-05 | Criteria for initiating incident recovery are applied |
| NIST-CSF-RS.MI-01 | Incidents are contained |
| NIST-CSF-RS.MI-02 | Incidents are eradicated |
Recover
| Code | Title |
|---|---|
| RC.CO-03 | Recovery activities are communicated to internal and external stakeholders |
| RC.CO-04 | Public updates on recovery are shared using approved methods |
| RC.RP-01 | Recovery portion of IR plan is executed |
| RC.RP-02 | Recovery actions are selected, scoped, prioritized, and performed |
| RC.RP-03 | Integrity of backups is verified before restoration |
| RC.RP-04 | Critical functions inform post-incident operational norms |
| RC.RP-05 | Integrity of restored assets is verified |
| RC.RP-06 | End of recovery is declared and documentation completed |
Respond
| Code | Title |
|---|---|
| RS.AN-03 | Analysis establishes what occurred and the root cause |
| RS.AN-06 | Investigation actions are recorded with integrity |
| RS.AN-07 | Incident data and metadata are collected with integrity |
| RS.AN-08 | Incident magnitude is estimated and validated |
| RS.CO-02 | Internal and external stakeholders are notified of incidents |
| RS.CO-03 | Information is shared with designated stakeholders |
| RS.MA-01 | Incident response plan is executed with third parties |
| RS.MA-02 | Incident reports are triaged and validated |
| RS.MA-03 | Incidents are categorized and prioritized |
| RS.MA-04 | Incidents are escalated or elevated as needed |
| RS.MA-05 | Criteria for initiating incident recovery are applied |
| RS.MI-01 | Incidents are contained |
| RS.MI-02 | Incidents are eradicated |
Your Compliance Coverage
If you comply with NIST Cybersecurity Framework 2.0, you already cover:
ISO 27001:2022
39%
82 controls mapped
Compare →NIST SP 800-82 Rev 3 — Guide to OT Security
11%
22 controls mapped
Compare →TISAX — Trusted Information Security Assessment Exchange
10%
21 controls mapped
Compare →+ 647 more: CSA CCM v4 (10%), HKMA Cyber Resilience Assessment Framework (C-RAF) (10%)
See all 650 mapped frameworks ↓Maps to 650 other frameworks
Frequently Asked Questions
What is NIST Cybersecurity Framework 2.0?
NIST Cybersecurity Framework 2.0 is a compliance framework from United States with 12 domains and 209 controls. Voluntary framework for managing and reducing cybersecurity risk, organized around six core functions It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does NIST Cybersecurity Framework 2.0 have?
NIST Cybersecurity Framework 2.0 has 209 controls organised across 12 domains. The largest domains are Govern (31 controls), GV - Govern (28 controls), PR - Protect (22 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does NIST Cybersecurity Framework 2.0 map to?
NIST Cybersecurity Framework 2.0 maps to 650 other compliance frameworks. The top mapping partners are ISO 27001:2022 (39% coverage), NIST SP 800-82 Rev 3 — Guide to OT Security (11% coverage), TISAX — Trusted Information Security Assessment Exchange (10% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with NIST Cybersecurity Framework 2.0 compliance?
Start your NIST Cybersecurity Framework 2.0 compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about NIST Cybersecurity Framework 2.0 requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 209 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 718 frameworks.
Get Started Free →Free forever — no credit card required