NIST CSF 2.0 expanded the framework with a new Govern function and broader applicability. Here is what changed, what stayed the same, and how to use it effectively.
The National Institute of Standards and Technology released version 2.0 of the Cybersecurity Framework in February 2024 — the first major update since the framework launched in 2014. For security teams that have been using CSF 1.1, the update introduces meaningful changes worth understanding. For organizations new to the framework, CSF 2.0 is the right place to start.
What the NIST CSF Is
The NIST Cybersecurity Framework is a voluntary framework that provides a common language and structured approach for managing cybersecurity risk. It was originally developed for critical infrastructure sectors but has been widely adopted across industries and organization sizes.
The framework is organized around functions — high-level categories of cybersecurity activity — that provide a lifecycle view of how organizations manage risk. CSF 2.0 expands the framework from five functions to six.
The Six Functions of CSF 2.0
Govern (new in 2.0). Establishes and monitors the organization's cybersecurity risk management strategy, expectations, and policy. This function recognizes that cybersecurity is fundamentally a governance and risk management challenge, not just a technical one. It covers organizational context, risk management strategy, roles and responsibilities, policy, oversight, and supply chain risk management.
Identify. Develops an organizational understanding of cybersecurity risk to systems, people, assets, data, and capabilities. Asset management, risk assessment, and improvement planning live here.
Protect. Implements safeguards to ensure delivery of critical services. Identity management, access control, awareness training, data security, and platform security are covered in this function.
Detect. Develops and implements activities to identify cybersecurity events. Continuous monitoring and adverse event analysis fall under Detect.
Respond. Takes action regarding a detected cybersecurity incident. Incident management, analysis, mitigation, and communication are the core activities.
Recover. Maintains plans for resilience and restores capabilities or services impaired by a cybersecurity incident. Recovery planning and communication are the focus.
What Changed in Version 2.0
The Govern function is the most significant addition. CSF 1.1 treated governance as a cross-cutting concern embedded in other functions. CSF 2.0 elevates it to a standalone function, reflecting the reality that cybersecurity risk management requires explicit organizational commitment, clear accountability, and integration with enterprise risk management.
Broader applicability. CSF 1.1 was explicitly designed for critical infrastructure. CSF 2.0 is designed for all organizations — any sector, any size, any maturity level. The language and examples reflect this broader scope.
Supply chain risk management expanded. CSF 2.0 gives significantly more attention to cybersecurity supply chain risk management (C-SCRM), recognizing that third-party risk is one of the most significant and undermanaged areas of exposure for most organizations.
Implementation Examples added. CSF 2.0 introduces Implementation Examples — concise, actionable steps for each subcategory. These are not requirements but practical illustrations of how organizations can meet the intent of each control.
Tiers clarified. The four implementation tiers (Partial, Risk Informed, Repeatable, Adaptive) are clarified to describe the rigor and sophistication of an organization's risk management practices, not a maturity score to optimize.
How to Use the Framework Effectively
The most common misuse of NIST CSF is treating it as a compliance checklist — working through every subcategory and marking it complete. That approach produces documentation, not security.
The framework is designed to be used as a risk management tool. Here is how to use it effectively:
Start with a Current Profile. Map your existing cybersecurity activities to the framework functions and categories. Be honest about gaps and inconsistencies. This is your baseline.
Define a Target Profile. Based on your risk assessment, business objectives, and compliance requirements, define where you need to be. Not every subcategory needs to be fully implemented — prioritize based on risk.
Identify and prioritize gaps. The gap between your Current Profile and Target Profile is your roadmap. Prioritize based on risk reduction potential and business impact.
Use the framework for communication. One of CSF's most underutilized features is its value as a communication tool. The function-based language translates technical security activities into business terms that resonate with executives and boards.
Mapping CSF to Other Frameworks
CSF 2.0 is designed to complement, not replace, other standards. NIST maintains reference mappings between CSF and NIST SP 800-53, ISO 27001, CIS Controls, and other frameworks. If your organization is pursuing SOC 2, ISO 27001, or CMMC, CSF can serve as an organizing framework that helps you see how your compliance work fits into a broader risk management picture.
The GRC2 Approach to CSF Implementation
We use NIST CSF as the organizing framework for most of our security program engagements. It provides the right level of structure without being prescriptive about implementation, which allows us to tailor the program to each organization's specific risk profile and business context.
Whether you are implementing CSF for the first time or updating an existing program to CSF 2.0, the key is starting with risk — not controls.
Related reading: Building a security program from scratch | SOC 2 compliance guide | GRC2 security and risk management services
Explore Topics
Written by
GRC2 Advisory Team
Content creator and writer sharing insights and stories.