NIST Cybersecurity Framework 2.0
Voluntary framework for managing and reducing cybersecurity risk, organized around six core functions
NIST Cybersecurity Framework 2.0 is a compliance framework from United States with 7 domains and 106 controls that map to 303 other frameworks. The largest domains are GV - Govern (28 controls), PR - Protect (22 controls), ID - Identify (21 controls). Every control below carries what it requires and what an assessor expects to see.
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 (7)
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 | The estimated impact and scope of adverse events are understood |
| NIST-CSF-DE.AE-06 | Information on adverse events is provided to authorized staff and tools |
| NIST-CSF-DE.AE-07 | Cyber threat intelligence and other contextual information are integrated into the analysis |
| NIST-CSF-DE.AE-08 | Incidents are declared when adverse events meet the defined incident 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 and services are monitored to find potentially adverse events |
| NIST-CSF-DE.CM-09 | Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events |
GV - Govern
Establish and monitor cybersecurity risk management strategy, expectations, and policy
| Code | Title |
|---|---|
| NIST-CSF-GV.OC-01 | The organizational mission is understood and informs cybersecurity risk management |
| NIST-CSF-GV.OC-02 | Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered |
| NIST-CSF-GV.OC-03 | Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed |
| NIST-CSF-GV.OC-04 | Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated |
| NIST-CSF-GV.OC-05 | Outcomes, capabilities, and services that the organization depends on are understood and communicated |
| NIST-CSF-GV.PO-01 | Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced |
| NIST-CSF-GV.PO-02 | Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission |
| NIST-CSF-GV.RM-01 | Risk management objectives are established and agreed to by organizational stakeholders |
| NIST-CSF-GV.RM-02 | Risk appetite and risk tolerance statements are established, communicated, and maintained |
| NIST-CSF-GV.RM-03 | Cybersecurity risk management activities and outcomes are included in enterprise risk management processes |
| NIST-CSF-GV.RM-04 | Strategic direction that describes appropriate risk response options is established and communicated |
| NIST-CSF-GV.RM-05 | Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties |
| NIST-CSF-GV.RM-06 | A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated |
| NIST-CSF-GV.RM-07 | Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions |
| NIST-CSF-GV.RR-01 | Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving |
| NIST-CSF-GV.RR-02 | Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced |
| NIST-CSF-GV.RR-03 | Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies |
| NIST-CSF-GV.RR-04 | Cybersecurity is included in human resources practices |
| NIST-CSF-GV.SC-01 | A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders |
| NIST-CSF-GV.SC-02 | Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally |
| NIST-CSF-GV.SC-03 | Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes |
| NIST-CSF-GV.SC-04 | Suppliers are known and prioritized by criticality |
| NIST-CSF-GV.SC-05 | Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties |
| NIST-CSF-GV.SC-06 | Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships |
| NIST-CSF-GV.SC-07 | The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship |
| NIST-CSF-GV.SC-08 | Relevant suppliers and other third parties are included in incident planning, response, and recovery activities |
| NIST-CSF-GV.SC-09 | Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle |
| NIST-CSF-GV.SC-10 | Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement |
Govern
| Code | Title |
|---|---|
| NIST-CSF-GV.OV-01 | Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction |
| NIST-CSF-GV.OV-02 | The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks |
| NIST-CSF-GV.OV-03 | Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed |
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 the organization's authorized network communication and internal and external network 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 on the mission |
| NIST-CSF-ID.AM-07 | Inventories of data and corresponding metadata for designated data types are maintained |
| NIST-CSF-ID.AM-08 | Systems, hardware, software, services, and data are managed throughout their life cycles |
| NIST-CSF-ID.IM-01 | Improvements are identified from evaluations |
| NIST-CSF-ID.IM-02 | Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties |
| NIST-CSF-ID.IM-03 | Improvements are identified from execution of operational processes, procedures, and activities |
| NIST-CSF-ID.IM-04 | Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved |
| 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 and sources |
| NIST-CSF-ID.RA-03 | Internal and external threats to the organization are identified and recorded |
| NIST-CSF-ID.RA-04 | Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded |
| NIST-CSF-ID.RA-05 | Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization |
| 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 | Processes for receiving, analyzing, and responding to vulnerability disclosures are established |
| NIST-CSF-ID.RA-09 | The authenticity and integrity of hardware and software are assessed prior to acquisition and use |
| NIST-CSF-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 by the organization |
| 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 in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties |
| NIST-CSF-PR.AA-06 | Physical access to assets is managed, monitored, and enforced commensurate with risk |
| NIST-CSF-PR.AT-01 | Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind |
| NIST-CSF-PR.AT-02 | Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind |
| 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 logical access and usage |
| 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 are prevented |
| NIST-CSF-PR.PS-06 | Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle |
RC - Recover
Restore assets and operations affected by a cybersecurity incident
| Code | Title |
|---|---|
| NIST-CSF-RC.CO-03 | Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders |
| NIST-CSF-RC.CO-04 | Public updates on incident recovery are shared using approved methods and messaging |
| NIST-CSF-RC.RP-01 | The recovery portion of the incident response plan is executed once initiated from the incident response process |
| NIST-CSF-RC.RP-02 | Recovery actions are selected, scoped, prioritized, and performed |
| NIST-CSF-RC.RP-03 | The integrity of backups and other restoration assets is verified before using them for restoration |
| NIST-CSF-RC.RP-04 | Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms |
| NIST-CSF-RC.RP-05 | The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed |
| NIST-CSF-RC.RP-06 | The end of incident recovery is declared based on criteria, and incident-related documentation is completed |
RS - Respond
Take action regarding a detected cybersecurity incident
| Code | Title |
|---|---|
| NIST-CSF-RS.AN-03 | Analysis is performed to establish what has taken place during an incident and the root cause of the incident |
| NIST-CSF-RS.AN-06 | Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved |
| NIST-CSF-RS.AN-07 | Incident data and metadata are collected, and their integrity and provenance are preserved |
| NIST-CSF-RS.AN-08 | An incident's magnitude is estimated and validated |
| 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 once an incident is declared |
| 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 | The criteria for initiating incident recovery are applied |
| NIST-CSF-RS.MI-01 | Incidents are contained |
| NIST-CSF-RS.MI-02 | Incidents are eradicated |
Your Compliance Coverage
If you comply with NIST Cybersecurity Framework 2.0, you already cover:
NIST SP 800-53 Rev 5
100%
106 controls mapped
Compare →Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1
98%
104 controls mapped
Compare →NIST SP 800-53 Rev 5 MODERATE
98%
104 controls mapped
Compare →+ 300 more: FedRAMP Moderate (98%), NIST SP 800-53 Revision 5.1 HIGH (98%)
See all 303 mapped frameworks ↓Maps to 303 other frameworks
What is NIST Cybersecurity Framework 2.0 and who does it apply to?
NIST Cybersecurity Framework 2.0 is a compliance framework from United States with 7 domains and 106 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.
What does NIST Cybersecurity Framework 2.0 actually require?
NIST Cybersecurity Framework 2.0 has 106 controls organised across 7 domains. The largest domains are GV - Govern (28 controls), PR - Protect (22 controls), ID - Identify (21 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of NIST Cybersecurity Framework 2.0 do I already cover?
NIST Cybersecurity Framework 2.0 maps to 303 other compliance frameworks. The top mapping partners are NIST SP 800-53 Rev 5 (100% coverage), Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 (98% coverage), NIST SP 800-53 Rev 5 MODERATE (98% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement NIST Cybersecurity Framework 2.0?
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 106 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 686 frameworks.
Get Started Free →Free forever — no credit card required