NIST CSF 2.0 and the Govern Function — and How It Relates to NIST SP 800-53

NIST Cybersecurity Framework 2.0, released in February 2024, organizes cybersecurity outcomes into six functions — Govern, Identify, Protect, Detect, Respond and Recover. The new Govern function addresses strategy, roles, policy, oversight and supply chain risk. The CSF describes outcomes; NIST SP 800-53 provides a detailed catalog of controls that can be used to achieve them.

The NIST Cybersecurity Framework has been the most widely used way to describe and measure cybersecurity programs in the United States for more than a decade. Version 2.0, released in February 2024, made the most significant changes since the framework's introduction — most visibly, a new function called Govern.

What changed in CSF 2.0

  • A sixth function. The original five functions — Identify, Protect, Detect, Respond and Recover — are joined by Govern.
  • A broader audience. The framework is explicitly intended for organizations of all sizes and sectors, not just critical infrastructure.
  • More implementation guidance. NIST added implementation examples, quick-start guides and an online reference tool with mappings to other frameworks.
  • Greater emphasis on supply chain risk. Cybersecurity supply chain risk management is now a category within Govern.

The Govern function

Govern addresses how an organization's cybersecurity risk management strategy, expectations and policy are established, communicated and monitored. Its categories cover:

  • Organizational context — understanding the mission, stakeholders and legal and regulatory requirements
  • Risk management strategy — priorities, risk appetite and tolerance
  • Roles, responsibilities and authorities — who is accountable for cybersecurity outcomes
  • Policy — establishing and communicating cybersecurity policy
  • Oversight — reviewing results to adjust strategy
  • Cybersecurity supply chain risk management — managing risks from suppliers and third parties

Govern sits at the center of the framework because it informs everything else. It also gives boards and executives a natural entry point: these are questions leadership must answer, not just the security team.

Using profiles to drive improvement

The most practical way to use the CSF is through profiles:

  1. Current profile — where you are today for each relevant outcome.
  2. Target profile — where you need to be, based on risk, requirements and business goals.
  3. Gap analysis and action plan — the prioritized work that closes the gap.

Profiles turn the framework into a roadmap with measurable progress and a common language for reporting to leadership.

How CSF relates to NIST SP 800-53

The CSF and SP 800-53 are complementary, not competing:

NIST CSF 2.0 NIST SP 800-53 Rev. 5
What it is Framework of cybersecurity outcomes Catalog of security and privacy controls
Level of detail High-level outcomes (functions, categories, subcategories) Detailed controls and enhancements
Primary use Strategy, measurement and communication Control selection, implementation and assessment
Typical users All organizations; leadership and security teams Federal systems, contractors and organizations needing control-level rigor

Think of the CSF as describing what good looks like, and SP 800-53 as one detailed way to build and test it. Many organizations use the CSF to set direction and report maturity, while implementing controls from SP 800-53, the CIS Controls, ISO 27001 or another catalog — whichever best fits their obligations.

Getting started

  1. Define scope — the whole organization or a specific business unit.
  2. Assess your current profile, starting with Govern.
  3. Set a target profile grounded in risk and requirements.
  4. Prioritize improvements by risk reduction, cost and dependencies.
  5. Report progress to leadership using the CSF's functions and categories.

The bottom line

CSF 2.0 makes cybersecurity governance explicit. Use the Govern function to align leadership on strategy and accountability, use profiles to measure and plan, and pair the CSF with a control catalog like SP 800-53 to turn outcomes into implemented, testable controls.

Frequently asked questions

Is NIST CSF mandatory?

For most private organizations the CSF is voluntary, though it is widely referenced by regulators, insurers and customers. Federal agencies are subject to separate requirements.

What are CSF tiers?

Tiers (Partial, Risk Informed, Repeatable, Adaptive) describe the rigor of an organization's cybersecurity risk governance and management practices. They are distinct from profiles, which describe specific outcomes.

Does CSF 2.0 map to other frameworks?

Yes. NIST provides informative references and mappings, including to SP 800-53, through its online reference tool.

This article is for general information only and does not constitute legal, accounting or other professional advice. Requirements change; consult the cited sources and a qualified advisor about your specific situation.

Formos Consulting Risk, compliance, cybersecurity and transformation advisors

Keep reading

Related insights

All insights

Let’s talk about what you need.

Tell us where you are and where you need to be. A senior member of our team will follow up to talk through options.