Skip to content
Cyber Defense Technologies

Compliance

NIST CSF 2.0 for Defense Suppliers: Putting "Govern" to Work

Version 2.0 of the NIST Cybersecurity Framework added a sixth function, Govern, that puts cybersecurity strategy, roles, policy, oversight and supply chain risk in front of leadership. What Govern asks for, why it matters to suppliers in the defense industrial base, and a practical way to adopt it.

By Cyber Defense Technologies November 18, 2026 4 min read

Most cybersecurity frameworks tell you what to protect and how. Fewer tell you who decides, how much risk is acceptable, and how leadership knows whether the program is working. That gap is why so many security programs are strong on tools and weak on direction.

Version 2.0 of the NIST Cybersecurity Framework (CSF), released in February 2024, addresses it directly with a new function: Govern.

From five functions to six

The original CSF organized cybersecurity outcomes into five functions: Identify, Protect, Detect, Respond and Recover. CSF 2.0 keeps them and adds Govern, which NIST describes as informing how the organization achieves and prioritizes the outcomes of the other five.

The six functions of NIST CSF 2.0

  1. 1 Govern

    Strategy, roles, policy, oversight and supply chain risk. New in 2.0.

  2. 2 Identify

    Understand assets, risks and improvement opportunities.

  3. 3 Protect

    Safeguard assets with identity, training, data and platform security.

  4. 4 Detect

    Find and analyze possible attacks and compromises.

  5. 5 Respond

    Act on detected incidents.

  6. 6 Recover

    Restore assets and operations after an incident.

Govern sits at the center and informs how the other five are prioritized.

CSF 2.0 also widened its audience. The original framework was written with critical infrastructure in mind; version 2.0 is explicitly for organizations of every size and sector, with quick-start guides for small businesses.

What Govern covers

Govern has six categories:

  • Organizational context (GV.OC): understanding the mission, stakeholders, and legal, regulatory and contractual requirements that shape cybersecurity decisions.
  • Risk management strategy (GV.RM): priorities, constraints, risk tolerance and assumptions, written down and used.
  • Roles, responsibilities and authorities (GV.RR): who is accountable for cybersecurity risk, starting with leadership, and whether they have the resources to act.
  • Policy (GV.PO): policies that reflect the strategy and are communicated and enforced.
  • Oversight (GV.OV): how results are reviewed and the strategy adjusted.
  • Cybersecurity supply chain risk management (GV.SC): how the organization manages the risk that comes from suppliers and partners.

None of these require new technology. They require decisions, and someone with the authority to make them.

Why it matters to defense suppliers

Customers are asking. Primes and government customers increasingly want to know not just which controls you have, but who owns cyber risk, how incidents are escalated, and how you manage your own suppliers. Govern gives you a structured answer.

You are part of someone else's supply chain. The GV.SC category is how your customers manage you. Understanding it shows you what they will ask, and applying it to your own suppliers closes the gaps attackers use, as we described in Software Supply Chain Attacks.

It connects compliance to the business. Contractual requirements, such as protecting controlled information under DFARS 252.204-7012, are part of organizational context. Govern puts them in the same picture as revenue, mission and risk, so they get resourced like business obligations instead of IT chores.

It makes the other functions work. Detection without an escalation path, or recovery without a decision on acceptable downtime, fails when it matters. Govern supplies those decisions in advance.

A practical way to adopt Govern

  1. Name an accountable executive. One senior leader owns cybersecurity risk and reports on it to the rest of leadership.
  2. Write down your risk appetite. In plain language: which systems and data matter most, what downtime is tolerable, what risks you will not accept.
  3. Map your obligations. List the contractual, legal and regulatory requirements that apply, including flow-downs from primes.
  4. Build a current profile. Using the CSF categories, record where you are today. Be honest; this is for you.
  5. Build a target profile. Decide where you need to be in 12 to 24 months, based on risk and obligations, not on doing everything.
  6. Close the gaps in priority order, with owners and dates. Our guide to Plans of Action and Milestones works for any gap list.
  7. Review on a schedule. Leadership reviews progress, incidents and changes in risk at least quarterly, and adjusts the target.
  8. Extend it to suppliers. Identify your critical suppliers and what you require of them.

How CSF fits with other requirements

CSF is voluntary and outcome-based. It does not replace specific requirements such as NIST SP 800-171 or NIST SP 800-53, but it organizes them. NIST publishes mappings from CSF 2.0 to other frameworks, so a single CSF profile can show how your program meets several sets of requirements at once.

How CDT can help

CDT helps organizations build CSF profiles, set up governance that leadership can actually run, and connect it to their contractual obligations through our security control assessments and program protection services.

Sources

Let's talk

Ready to strengthen your security posture?

Talk with a CDT engineer about your mission, your systems and your deadlines. We'll tell you honestly what it takes.