Govern (GV): Setting Cybersecurity Strategy and Accountability
The function CSF 2.0 added to put leadership, risk strategy and supply chain at the center
TL;DR (for busy owners)
- What it is: Govern (GV) is the CSF 2.0 function that sets why and how the organization manages cybersecurity risk: context, risk appetite, roles, policy, oversight and supplier risk. It was added in CSF 2.0 (February 2024) and informs the other five functions.
- Why it matters: Without it, security work is a list of tools rather than a decision the business has made. Most other gaps — unowned systems, unreviewed vendor access, no one accountable for incidents — trace back to governance.
- Quick action: Name one accountable executive for cybersecurity, write down your top five cyber risks, and list the vendors that can access your data or cloud accounts.
The six Govern categories
| Code | Category | In plain English |
|---|---|---|
| GV.OC | Organizational Context | What the business does, what it depends on, and which legal and contractual obligations apply |
| GV.RM | Risk Management Strategy | How much risk you accept and how cyber risk fits into business decisions |
| GV.RR | Roles, Responsibilities, and Authorities | Who decides, who does the work, who is accountable |
| GV.PO | Policy | The written rules, kept current and communicated |
| GV.OV | Oversight | Leadership reviewing whether the strategy is working and adjusting it |
| GV.SC | Cybersecurity Supply Chain Risk Management | Managing risk from suppliers, SaaS vendors and service providers |
Signs Govern is weak
- Security decisions are made ad hoc by whoever notices a problem.
- Nobody can say who approved the last exception to a security rule, or when it expires.
- Third parties have access to production accounts and nobody owns the relationship.
- Leadership hears about security only after an incident or a failed customer questionnaire.
What it looks like in a cloud company
In AWS-centric organizations, governance shows up as concrete decisions: who may create accounts and grant administrator access, which regions are allowed, which data may leave the organization, and which vendors may assume roles in production. Organization-level guardrails (for example service control policies) are governance decisions expressed as code — but only if someone owns them and reviews them.
Fast checks (30–60 minutes)
Govern quick assessment
- A named executive is accountable for cybersecurity risk (GV.RR)
- The top cyber risks and the risk appetite are written down and reviewed at least annually (GV.RM)
- Security policies exist, have owners and were reviewed in the last 12 months (GV.PO)
- Every third party with access to data or cloud accounts is listed with a business owner (GV.SC)
- Leadership receives a regular security update that includes open risks and exceptions (GV.OV)
- Legal, regulatory and contractual security obligations are documented (GV.OC)
Evidence to keep
Records auditors and customers typically ask for
Security roles and responsibilities document (RACI)
Risk register with owners, ratings and decisions
Vendor inventory with access level and review date
Minutes or notes from leadership security reviews
Map to frameworks
NIST CSF 2.0 Govern categories
Where Securitain fits
Supporting evidence from your AWS environment
Third-party and cross-account access
Governance decisions about vendors only work if you know who can actually reach your accounts.
- 1Connect AWS with Securitain's read-only role
- 2Review roles trusted by external accounts and missing ExternalId conditions
- 3Use the results to update your vendor inventory and owners
Securitain analyzes AWS identity, trust and resource-policy configuration. It does not assess governance processes themselves; those remain a leadership responsibility.
Next steps
Start small, then make it routine
Name the accountable executive and build the vendor list first. Then schedule a quarterly 30-minute leadership review of open risks and exceptions — that single habit covers much of GV.OV. The Executive Cyber Risk Brief can structure the first conversation.
Sources & References
- 1.The NIST Cybersecurity Framework (CSF) 2.0 — NIST CSWP 29
Official framework text, published February 26, 2024
- 2.NIST CSF 2.0: Enterprise Risk Management Quick-Start Guide (SP 1303)
Connecting cyber risk to enterprise risk decisions
- 3.NIST Cybersecurity Framework
Framework home and resources
Read-only analysis of IAM identities, permissions and cross-account trust to support governance decisions.
See who can access your AWS accounts