NIST Cybersecurity Framework 2.0, explained: Govern, wider scope, Profiles and Tiers
CSF 2.0, published on February 26, 2024, adds a sixth Function, Govern, drops the critical-infrastructure title, moves its references online and keeps Profiles and Tiers as the way an organization states where it is and where it wants to be.
What the framework is
The NIST Cybersecurity Framework (CSF) 2.0 is a taxonomy of high-level cybersecurity outcomes that any organization can use to understand, assess, prioritize and communicate its cybersecurity work [1]. It does not prescribe how to reach those outcomes; it links to online resources that suggest practices and controls [1]. NIST published it as Cybersecurity White Paper 29 on February 26, 2024 [1] [4].
It has three parts. The Core is a hierarchy of Functions, Categories and Subcategories. Organizational Profiles describe an organization’s current or target posture in terms of the Core. Tiers characterize how rigorous its cybersecurity risk governance and management practices are [1]. NIST says the Core is not a checklist, and that the order and size of its parts imply neither sequence nor importance [1].
What changed from Version 1.1
Version 1.1 was dated April 16, 2018 and refined Version 1.0 of February 2014. Its title was Framework for Improving Critical Infrastructure Cybersecurity, and it traced its origin to Executive Order 13636 and the Cybersecurity Enhancement Act of 2014 [2]. Four changes stand out in 2.0.
1. A sixth Function: Govern
Version 1.1 organized its Core under five Functions: Identify, Protect, Detect, Respond and Recover [2]. CSF 2.0 adds GOVERN, defined as the organization’s cybersecurity risk management strategy, expectations and policy being established, communicated and monitored [1]. It informs how the organization achieves and prioritizes the outcomes of the other five Functions, and NIST describes governance as the way cybersecurity is folded into enterprise risk management [1].
GOVERN has six Categories [1]:
- Organizational Context (GV.OC)
- Risk Management Strategy (GV.RM)
- Roles, Responsibilities, and Authorities (GV.RR)
- Policy (GV.PO)
- Oversight (GV.OV)
- Cybersecurity Supply Chain Risk Management (GV.SC)
Several of these had homes elsewhere before. Version 1.1 listed Governance (ID.GV), Risk Management Strategy (ID.RM) and Supply Chain Risk Management (ID.SC) as Categories under Identify [2]. In 2.0, supply chain risk management sits under GOVERN as GV.SC [1]. NIST’s release on the update described a new focus on governance, presenting cybersecurity as a major source of enterprise risk that senior leaders should weigh alongside finance and reputation [3].
2. A reshaped Core
Counting the category tables in the two documents, Version 1.1 had 23 Categories and 2.0 has 22 [1] [2]. Outside GOVERN, 2.0 groups Protect into Identity Management, Authentication, and Access Control; Awareness and Training; Data Security; Platform Security; and Technology Infrastructure Resilience, and gives Detect two Categories, Continuous Monitoring and Adverse Event Analysis [1]. Subcategory numbering in 2.0 deliberately has gaps: a gap marks a 1.1 Subcategory that was moved [1]. NIST also offers the 2.0 Core in a legacy format similar to 1.1, and a spreadsheet overview of the Core changes from 1.1 to 2.0, added to the publication page in September 2024 [1] [4].
3. A scope stated for every organization
The 2.0 document states plainly that the critical-infrastructure title is not used for 2.0 [1]. NIST’s release says the framework now explicitly aims to help all organizations, beyond critical infrastructure, its original target audience, and that it is designed for organization types from the smallest schools and nonprofits to the largest agencies and corporations [3]. The wider scope was not wholly new: Version 1.1 already said it could be used by organizations in any sector of the economy or society, and outside the United States [2].
4. References and examples moved online
In Version 1.1, Informative References were one of the four elements of the Core itself [2]. In 2.0, Informative References, Implementation Examples and Quick-Start Guides are online resources that NIST can update more often than the framework document [1]. Informative References map the Core to other standards, guidelines and regulations; Implementation Examples are notional, action-oriented steps for reaching an outcome; Quick-Start Guides are short documents on particular topics or audiences [1]. NIST’s release said the catalog of references could cross-reference the framework to more than 50 other cybersecurity documents [3].
Profiles: where you are and where you are going
Every Organizational Profile includes a Current Profile, a Target Profile, or both [1]. The Current Profile records the outcomes the organization is achieving or attempting, and how far. The Target Profile records the outcomes it has chosen and prioritized, taking into account expected changes such as new requirements, new technology and threat trends [1].
NIST sets out a five-step cycle: scope the Profile; gather the information needed; create it; analyze the gaps between current and target and write an action plan; then carry out the plan and update the Profile [1]. A Community Profile is a published baseline of outcomes for a sector, subsector, technology, threat type or other shared use case, and can serve as the starting point for an organization’s Target Profile [1]. NIST continues to publish them; as checked on November 14, 2026, its framework site listed a draft Community Profile for federal Open Radio Access Network deployments open for comment [5].
Tiers: how rigorous the practices are
Tiers are optional. An organization can use them to inform its Current and Target Profiles [1]. There are four: Partial (Tier 1), Risk Informed (Tier 2), Repeatable (Tier 3) and Adaptive (Tier 4), describing a progression from informal, ad hoc responses to approaches that are agile, risk-informed and continuously improving [1]. Version 1.1 used the same four names [2]. In 2.0 each Tier is illustrated for two things: cybersecurity risk governance, which maps to GOVERN, and cybersecurity risk management, which maps to the other five Functions [1].
NIST says Tiers should complement an organization’s risk management method, not replace it, and that moving to a higher Tier is encouraged when risks or mandates are greater or when a cost-benefit analysis shows a feasible, cost-effective reduction in risk [1].
Who uses it, and how binding it is
NIST names those who build and lead cybersecurity programs as the primary audience, and lists executives, boards, acquisition staff, risk managers, lawyers and auditors among other users, along with regulators and associations that set priorities [1]. NIST calls it a resource that may be adopted voluntarily and through governmental policies and mandates [1]. Where a regulator, contract or customer refers to it, that instrument decides what is required, and counsel can say which apply. This page explains the framework and is not legal advice.
Moraph’s teams help organizations with work like this; see our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.