Govern is the part of NIST CSF 2.0 that boards ask about, and the part most organisations assess least honestly. CSF 2.0 (NIST CSWP 29, 26 February 2024) added Govern as a sixth Function and placed it at the centre of the other five, because it decides how Identify, Protect, Detect, Respond and Recover are prioritised and resourced. Many Current Profiles score Govern from the existence of a policy document and a named CISO, which misses most of its 31 outcomes. This guide works through the six Govern Categories at Subcategory level, shows what evidence an assessor should expect, maps Govern to SP 800-53 and ISO/IEC 27001, and covers where non-human identities and AI agents need explicit governance. It is for CISOs, GRC leads, risk managers and internal auditors who already know the CSF basics.
Key takeaways
- Govern sets the rules for the other five Functions. NIST describes it as the Function where cybersecurity risk management strategy, expectations and policy are established, communicated and monitored.
- It has six Categories and 31 Subcategories, and ten of those (GV.SC) are about the supply chain, so third-party risk is a governance outcome, not only an operational one.
- Risk appetite and risk tolerance are separate outcomes. GV.RM-02 expects both statements to be established, communicated and maintained; most organisations have neither in a usable form.
- Evidence beats documents. A Govern assessment should look for decisions that were made using the strategy (exceptions, budget, supplier choices), not only for the strategy itself.
- Machine identities need an accountable owner. GV.RR-02 and GV.PO-01 are where ownership, policy and enforcement for service accounts, API keys and AI agents are anchored.
What it is and who it applies to
The NIST Cybersecurity Framework is voluntary, and Govern inherits that status: no organisation is legally required to meet GV outcomes because they are in the CSF. In practice it applies wherever CSF 2.0 is the organisation's reference model, which includes US federal agencies that use it alongside the Risk Management Framework, critical infrastructure operators, regulated firms that use a sector profile, and private companies that report to their board using CSF Functions. See the NIST CSF 2.0 Guide for the Core, Profiles and Tiers as a whole.
In CSF 1.1, governance sat inside Identify as ID.GV, with risk management strategy in ID.RM and supply chain in ID.SC. CSF 2.0 lifted these out into a separate Function, added Oversight and Organizational Context, and widened supply chain to ten outcomes. NIST's wording is that Govern provides outcomes to inform what an organisation may do to achieve and prioritise the outcomes of the other five Functions. The intended users named in CSWP 29 include boards of directors and executives, and Govern is the Function that supports risk communication with them.
- Executives and boards: set priorities, risk appetite, accountability and resources (GV.RM, GV.RR-01, GV.RR-03).
- CISO and security leadership: translate appetite into tolerance, policy and roles (GV.RM-02, GV.PO, GV.RR-02).
- Enterprise risk, legal and procurement: own the context, legal obligations and supplier outcomes (GV.OC-03, GV.RM-03, GV.SC).
- HR: GV.RR-04 makes cybersecurity part of human resources practices.
- Internal audit: provides independent input to Oversight (GV.OV).
Structure and key requirements
Govern has six Categories. The table gives each with its Subcategory count and the outcomes that are most often missed in assessments. Statement wording is from the CSF 2.0 Core.
| Category | Subcategories | What it requires | Outcomes most often missed |
|---|---|---|---|
| GV.OC Organizational Context | 5 (GV.OC-01 to 05) | Mission, stakeholders, legal and contractual requirements, and dependencies in both directions are understood | GV.OC-04 (services others depend on you for) and GV.OC-05 (what you depend on), which feed resilience and supplier criticality |
| GV.RM Risk Management Strategy | 7 (GV.RM-01 to 07) | Objectives, appetite and tolerance, ERM integration, risk response direction, communication lines, a standard risk method, positive risk | GV.RM-06 (standardised method for calculating and prioritising risk) and GV.RM-07 (strategic opportunities, or positive risks) |
| GV.RR Roles, Responsibilities, and Authorities | 4 (GV.RR-01 to 04) | Leadership accountability and culture, defined roles, adequate resources, cybersecurity in HR practices | GV.RR-03 (resources commensurate with the strategy) and GV.RR-04 (HR practices such as screening, onboarding and exit) |
| GV.PO Policy | 2 (GV.PO-01 to 02) | Policy is established from context and strategy, communicated and enforced, then reviewed and updated | "Enforced": policies with no exception process or no measurement of compliance |
| GV.OV Oversight | 3 (GV.OV-01 to 03) | Strategy outcomes, coverage and risk management performance are reviewed and the strategy adjusted | GV.OV-03 (performance evaluated): board packs that report activity rather than performance against tolerance |
| GV.SC Cybersecurity Supply Chain Risk Management | 10 (GV.SC-01 to 10) | A C-SCRM programme, supplier roles, integration with ERM, supplier criticality, contract requirements, due diligence, ongoing monitoring, incident inclusion, life cycle and post-relationship provisions | GV.SC-04 (suppliers known and prioritised by criticality), GV.SC-08 (suppliers in incident planning) and GV.SC-10 (what happens after a contract ends) |
Risk appetite versus risk tolerance
The CSF 2.0 ERM Quick-Start Guide (SP 1303) distinguishes the two: risk appetite is a general statement of the risk the organisation is willing to accept, and risk tolerance is a more specific statement that can be measured and used by managers. Leaders set appetite; managers translate it into tolerance statements and metrics that define a target state for their units. A usable tolerance statement for identity might read "no production service account without a named owner for more than 14 days" or "no long-lived cloud access key older than 90 days". See the Cyber Risk Appetite Statement Template.
Govern and the Tiers
CSF Tiers characterise the rigour of governance and management practices. CSWP 29 Appendix B describes governance at each Tier, which makes it the natural yardstick for Govern maturity:
| Tier | Governance characteristic (summarised from CSWP 29) | Typical Govern evidence |
|---|---|---|
| Tier 1 Partial | Strategy managed ad hoc; limited awareness of cybersecurity risk and of supplier risk | Policies exist but are not tied to a strategy; no supplier inventory |
| Tier 2 Risk Informed | Practices approved by management but may not be organisation-wide policy | Approved strategy; risk discussed in some business units only |
| Tier 3 Repeatable | Practices formally approved and expressed as policy; organisation-wide approach; regular communication between cybersecurity and non-cybersecurity executives | Policy set with owners and review dates; risk committee minutes; standard risk method |
| Tier 4 Adaptive | Executives monitor cybersecurity risk in the same context as financial and other risks; budgets reflect the risk environment and tolerance | Cyber risks in the enterprise risk register; budget decisions traceable to tolerance breaches |
Identity and NHI requirements
Govern says nothing specific about identities, but several of its outcomes are where machine identity programmes either get a mandate or fail for lack of one. PR.AA in Protect covers identities and credentials for users, services and hardware; Govern decides who owns them and what the tolerance is.
- GV.RR-02 ownership: every service account, workload identity, API key, OAuth integration and AI agent needs an accountable human owner with authority to approve and revoke it. See the NHI Ownership Guide.
- GV.PO-01 and GV.PO-02 policy: the access control and secrets policies should name non-human identities explicitly (creation approval, maximum credential lifetime, rotation, decommissioning) and be updated when new technology such as agentic AI arrives, which is exactly the trigger GV.PO-02 describes.
- GV.RM-02 tolerance: set measurable tolerances for orphaned NHIs, credential age and over-privilege, so the board sees a number against a threshold.
- GV.SC-05 and GV.SC-07 suppliers: SaaS integrations and third-party tokens are supplier risk. Contract requirements should cover how a supplier stores tokens you grant it and how quickly it notifies you of compromise. See the SaaS and OAuth App Governance Guide.
- GV.SC-10 end of relationship: revoking every key, token and federation trust given to a supplier when the contract ends is a Govern outcome, and is often skipped.
- GV.RR-04 HR practices: leaver processes must reach the personal access tokens and API keys a person created, not only their user account.
For a maturity view of NHI governance specifically, see the NHI Governance Maturity Model.
Implementation steps
- Scope and sponsor: agree the scope of the Govern assessment (enterprise or business unit) and an executive sponsor. SP 1308 recommends convening leadership, cybersecurity, ERM and workforce management stakeholders at this stage.
- Build the context (GV.OC): document mission and critical services, a legal and contractual obligations register (for example NIS2, DORA, SEC disclosure or sector rules that apply to you), and inbound and outbound dependencies.
- Write appetite, then tolerance (GV.RM-01, GV.RM-02): have the board or its risk committee approve appetite; have management write tolerance statements with metrics and thresholds for the top risk themes.
- Fix the risk method (GV.RM-06): adopt one scoring method and register format across the organisation so system-level risks can be aggregated into the enterprise risk register, as SP 1303 describes. Quantitative methods are optional; consistency is not. See the Cyber Risk Quantification Guide.
- Assign roles and authorities (GV.RR): publish a RACI covering risk owners, control owners, NHI owners and supplier owners; confirm who can accept risk and up to what level.
- Align policy (GV.PO): map each policy to the strategy, give it an owner and review date, and build an exception process with expiry dates. See the Information Security Policy Template.
- Stand up C-SCRM (GV.SC): create a supplier inventory, apply criticality criteria (importance of service, data sensitivity, degree of system access, per SP 1305), add standard contract clauses and plan exit provisions.
- Close the loop (GV.OV): set a reporting cadence to the board, report performance against tolerance, and record the strategy changes that resulted.
- Re-profile: update the Current Profile at Subcategory level and compare it with the Target Profile to produce the next action plan.
Small versus large organisations: a small business can meet most Govern outcomes with a one-page strategy, a short appetite statement, a supplier list with three criticality levels and an annual owner review (NIST's Small Business Quick-Start Guide, SP 1300, is aimed at this case). Large or regulated organisations need the full register aggregation, a formal risk committee and contract clause libraries, and usually have to show the same evidence to several regulators.
Evidence and assessment
An assessor should test whether each outcome is achieved, not whether a document exists. The table lists evidence that shows an outcome is operating.
| Subcategory | Weak evidence | Strong evidence |
|---|---|---|
| GV.OC-03 legal and contractual requirements | A list of laws | An obligations register with owners, mapped to controls, updated after a new regulation |
| GV.RM-02 appetite and tolerance | A sentence in the strategy | Board-approved appetite plus tolerance metrics that are reported and have triggered escalation |
| GV.RM-03 ERM integration | Cyber listed as one ERM risk | Cyber risks scored with the enterprise method and present in the enterprise risk register and profile |
| GV.RR-01 leadership accountability | CISO job description | Board minutes showing decisions on cyber risk; named executive risk owners |
| GV.RR-03 resources | Budget line | Budget requests and approvals traceable to risk and tolerance gaps |
| GV.PO-01 policy enforced | Signed policy | Compliance measurements and an exception register with expiry dates |
| GV.OV-03 performance reviewed | Quarterly activity report | Trend against tolerance and a record of strategy adjustments |
| GV.SC-04 suppliers prioritised | Procurement vendor list | Inventory with criticality tier, data and access recorded for each supplier |
| GV.SC-10 post-relationship | Termination clause | Exit checklist showing revoked access, keys and data return or destruction |
Metrics that show Govern is working
- Tolerance coverage: percentage of top enterprise cyber risks with a measurable tolerance statement.
- Exceptions: number of open policy exceptions past their expiry date.
- Supplier coverage: percentage of critical suppliers with current due diligence and security contract clauses.
- Ownership: percentage of non-human identities with a named, current owner.
- Board decisions: number of recorded board or committee decisions that changed priorities or budget because of cyber risk reporting.
- Policy currency: percentage of policies reviewed within their stated cycle.
See the Board Cyber Risk Reporting Guide for how to present these.
Mapping to other frameworks
NIST publishes official CSF 2.0 Informative References, including a CSF 2.0 to SP 800-53 Rev 5 mapping, through the CSF 2.0 Reference Tool and the OLIR catalogue; use those files for formal crosswalks. The table below is a practical orientation by control purpose.
| Govern Category | SP 800-53 Rev 5 controls (related) | ISO/IEC 27001:2022 |
|---|---|---|
| GV.OC | PM-11 Mission and Business Process Definition | Clause 4 (context, interested parties) |
| GV.RM | PM-9 Risk Management Strategy, PM-28 Risk Framing | Clause 6.1 (actions to address risks) |
| GV.RR | PM-2 Information Security Program Leadership Role, PM-29 Risk Management Program Leadership Roles, PM-3 Information Security and Privacy Resources, PM-13 Security and Privacy Workforce, PS-9 Position Descriptions | Clauses 5.1 and 5.3; Annex A 5.2, 6.1 to 6.5 |
| GV.PO | The -1 Policy and Procedures control in each family, for example PL-1 and PS-1; PM-1 Information Security Program Plan | Clause 5.2; Annex A 5.1 |
| GV.OV | PM-6 Measures of Performance, PM-14 Testing, Training, and Monitoring, CA-7 Continuous Monitoring | Clauses 9.1 to 9.3 |
| GV.SC | PM-30 Supply Chain Risk Management Strategy, SR-2, SR-3, SR-5, SR-6, SA-4, SA-9, PS-7 | Annex A 5.19 to 5.22 |
For a full CSF and ISO crosswalk see the NIST CSF to ISO 27001 Mapping Guide. For supply chain depth, NIST points Govern users to SP 800-161r1: see the NIST SP 800-161 Cyber Supply Chain Risk Management Guide. For ERM integration, CSWP 29 points to IR 8286 and SP 800-221. In the UK, the Cyber Governance Code of Practice (published 8 April 2025 by DSIT with the NCSC) is aimed at boards and directors and covers similar ground from the board's side. For workforce roles under GV.RR, see the NICE Workforce Framework Guide.
Common pitfalls
- Scoring Govern from documents: a strategy and policy set earns Tier 3 language without any evidence that decisions are made with them. Test for decisions, exceptions and budget traceability.
- Appetite with no tolerance: "we have a low appetite for cyber risk" cannot be measured. Without GV.RM-02 tolerances, Oversight has nothing to compare performance against.
- GV.SC treated as procurement's problem: criticality is set by contract value rather than by data sensitivity and system access, so small suppliers with privileged integrations are rated low.
- No exit governance: contracts end but API keys, OAuth grants and federation trusts survive. GV.SC-10 exists for this.
- Unowned machine identities: roles are defined for people but not for service accounts and agents, so nobody can approve or revoke them.
- Board reporting of activity: counts of phishing tests and patches instead of performance against tolerance; GV.OV-03 is not met.
Practitioner checklist
- Assess all 31 Govern Subcategories individually in the Current Profile, not the six Categories as a block.
- Obtain board or risk committee approval of a risk appetite statement and record it.
- Write measurable tolerance statements, including at least one for non-human identities.
- Adopt one risk scoring method and register format and feed cyber risks into the enterprise risk register.
- Publish a RACI that includes risk acceptance authority and NHI ownership.
- Give every policy an owner, a review date and an exception process with expiry.
- Build a supplier inventory with criticality based on service importance, data sensitivity and system access.
- Add standard security clauses and an exit checklist that revokes credentials and trusts.
- Report performance against tolerance to the board and record the decisions taken.
- Use the official CSF 2.0 Informative References for any formal crosswalk.
Standards and references
- NIST: The NIST Cybersecurity Framework (CSF) 2.0, CSWP 29
- NIST: Cybersecurity Framework 2.0
- NIST: SP 1303 CSF 2.0 Enterprise Risk Management Quick-Start Guide
- NIST: SP 1305 CSF 2.0 Cybersecurity Supply Chain Risk Management Quick-Start Guide
- NIST: SP 1308 CSF 2.0 Cybersecurity, Enterprise Risk Management and Workforce Management Quick-Start Guide
- NIST: CSF 2.0 Informative References
- NIST: SP 800-53 Rev. 5
- UK Government: Cyber Governance Code of Practice
Related NHI Mgmt Group resources: NIST CSF 2.0 Guide · Board Cyber Risk Reporting Guide · Third-Party Risk Management Guide · NHI Ownership Guide · NIST IR 8286 Cybersecurity and ERM Integration Guide