🇺🇸 United States · Global · Framework guide

NIST CSF 2.0: the six functions and how to turn them into a programme

The Cybersecurity Framework is the most widely used way to describe a security programme to a board, a regulator or a customer in a language they already know. Version 2.0 added governance as a function and extended the framework to every organisation, not only critical infrastructure. This guide explains the structure, the tiers and profiles, and how to use it to drive real controls rather than a colour-coded poster.

PublisherNational Institute of Standards and Technology (NIST)
Current versionCSF 2.0, published 26 February 2024 (replaces 1.1 of 2018)
Structure6 functions, 22 categories, 106 subcategories (outcomes)
FunctionsGovern, Identify, Protect, Detect, Respond, Recover
Tiers1 Partial, 2 Risk Informed, 3 Repeatable, 4 Adaptive (describe governance and risk management rigour, not maturity of controls)
CompanionsInformative references to SP 800-53, ISO 27001, CIS Controls and others; implementation examples; quick-start guides; community profiles

The CSF describes outcomes, not controls. “Identities and credentials for authorized users, services, and hardware are managed by the organization” is a subcategory; how you achieve it, and how an assessor checks it, comes from the informative references such as SP 800-53 or ISO 27001. That is both its strength, because any organisation can adopt it, and its trap, because a self-assessment against outcomes without evidence is easy to inflate.

Version 2.0 made two changes that matter in practice. Govern became a function of its own, covering strategy, roles, policy, oversight and supply-chain risk, and the framework now addresses all organisations. Profiles, which compare a current state against a target state, became the recommended way to plan and report.

The six functions

Govern (GV)

Organisational context, risk management strategy, roles and responsibilities, policy, oversight, and cybersecurity supply chain risk management. New in 2.0 and placed at the centre because it informs the other five.

Identify (ID)

Asset management, risk assessment and improvement: knowing what you have, what threatens it and what you will do about it.

Protect (PR)

Identity management and access control, awareness and training, data security, platform security, and technology infrastructure resilience.

Detect (DE)

Continuous monitoring and adverse event analysis: finding and characterising potentially harmful events.

Respond (RS)

Incident management, analysis, reporting and communication, and mitigation.

Recover (RC)

Incident recovery plan execution and recovery communication: restoring operations and telling stakeholders.

The implementation tiers

  1. Tier 1 Partial. Ad hoc risk management, limited awareness of cyber risk at organisational level, no formal supply-chain consideration.
  2. Tier 2 Risk Informed. Management approves practices but they are not organisation-wide policy; cyber risk awareness exists but is inconsistent.
  3. Tier 3 Repeatable. Formal policy, organisation-wide approach, regular updates as risk changes, supply-chain risk managed.
  4. Tier 4 Adaptive. Practices adapt from lessons learned and predictive indicators; cyber risk is part of enterprise decision-making and budgeting.

Who it applies to

Any organisation. In the United States it is the default language of boards, regulators and insurers: the SEC’s cybersecurity disclosure rules, sector regulators and the NIST Privacy Framework all reference it. Critical infrastructure operators, state and local government, healthcare and financial services use it directly; many international organisations adopt it alongside ISO 27001 to report to US customers and parents.

How GRCorb covers NIST Cybersecurity Framework 2.0

From scope to evidence, in one system

CSF outcomes as the reporting layer

GRCorb carries all 106 subcategories and maps them to the controls that achieve them in whichever frameworks you run, so a CSF profile is generated from control status and evidence rather than scored by opinion.

Current and target profiles

Set a target tier and profile per function; the gap view shows which subcategories are below target, which controls close the gap and what each would cost, which is the material a board roadmap is built from.

Evidence instead of self-assessment

Technical outcomes in Protect and Detect are evidenced from Microsoft 365, Entra ID, Intune, Defender, CrowdStrike, AWS, Azure, Google Cloud and your SIEM, so the profile reflects live configuration.

Board and CISO dashboards by function

Executive dashboards present posture by Govern, Identify, Protect, Detect, Respond and Recover, the view most US boards already expect.

Crosswalk to 800-53, ISO 27001 and SOC 2

Because the CSF is mapped to the underlying control frameworks, an organisation certified to ISO 27001 or holding a SOC 2 report gets a CSF profile from the evidence it already has.

Frequently asked questions

Can we be certified to the CSF?

No. NIST does not certify and the framework is voluntary. Organisations self-assess, sometimes with a third-party assessment, and report a profile and tier. For a certifiable standard, pair it with ISO 27001 or a SOC 2 report.

What changed from 1.1 to 2.0?

The Govern function was added, supply-chain risk management was expanded, the scope was widened from critical infrastructure to all organisations, and NIST published implementation examples, quick-start guides and community profiles. Categories were reorganised, so 1.1 mappings need to be redone.

Are tiers the same as maturity levels?

Not quite. Tiers describe how rigorously an organisation governs and manages cyber risk, not how many controls it has implemented. An organisation can be Tier 3 with real control gaps, which is why profiles, not tiers, are used to plan improvement.

CSF or ISO 27001?

The CSF is a way to describe and communicate a programme; ISO 27001 is a certifiable management-system standard with specific controls. Many organisations use the CSF for board reporting and ISO 27001 as the control set underneath, and GRCorb maps between them.

Related frameworks

Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.