Skip to content
Cyrrus Consulting Services
ES
Cybersecurity

Cybersecurity governance: what leadership decides under NIST CSF 2.0 and ISO/IEC 27014

When cybersecurity reaches the board, the question is usually technical: which tool to buy. The governance question is a different one: who decides how much risk is accepted, who answers for it and how anyone knows it works. This guide explains how NIST CSF 2.0 and ISO/IEC 27014 frame it.

Cybersecurity governance: what leadership decides under NIST CSF 2.0 and ISO/IEC 27014

The security report reaches the committee with dozens of technical indicators and no decision to make. Or the opposite: a security purchase has to be approved and nobody can say which risk it reduces. In both cases what is missing is governance, not technology.

This guide explains what cybersecurity governance is, what two public references say about the role of leadership, how they differ and what management should decide.

What is cybersecurity governance?

ISO/IEC 27014:2020 defines it by its purpose: it provides guidance on the concepts, objectives and processes of information security governance, by which an organization can evaluate, direct, monitor and communicate its security processes. Its audience is the governing body and top management, plus those who evaluate, direct and monitor an information security management system based on ISO/IEC 27001. It applies to organizations of all types and sizes.

NIST CSF 2.0 places it in the GOVERN function: the organization's cybersecurity risk management strategy, expectations and policy are established, communicated and monitored. That function, NIST says, informs what an organization may do to achieve and prioritize the outcomes of the other five, and is critical for incorporating cybersecurity into enterprise risk management.

In our view, the useful distinction is this: governing is deciding and overseeing (how much risk is accepted, who answers, what is reviewed); managing is running the controls. A company can have good controls without governance, and then it does not know whether they protect what matters.

What does NIST CSF 2.0 say about governance?

NIST published CSF 2.0 on February 26, 2024. It describes it as a taxonomy of high-level cybersecurity outcomes that does not prescribe how to achieve them, usable by any organization regardless of size, sector or maturity. Its six functions are GOVERN, IDENTIFY, PROTECT, DETECT, RESPOND and RECOVER. The document itself clarifies that the outcomes are not a checklist and that the order of the functions does not imply sequence or importance.

Categories of the GOVERN function in NIST CSF 2.0
CodeCategoryWhat it seeks, according to NIST
GV.OCOrganizational contextUnderstand the mission, stakeholder expectations, dependencies and legal and contractual requirements around risk decisions
GV.RMRisk management strategyEstablish priorities, constraints, risk appetite and tolerance, and use them in operational decisions
GV.RRRoles, responsibilities and authoritiesEstablish and communicate who answers, to foster accountability and continuous improvement
GV.POPolicyEstablish, communicate and enforce cybersecurity policy
GV.OVOversightUse risk management results to inform, improve and adjust the strategy
GV.SCSupply chain risk managementIdentify, establish, manage and improve supplier and third-party risk processes

Three outcomes in that table touch leadership directly. GV.RR-01 says organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical and continually improving. GV.RM-02 calls for risk appetite and risk tolerance statements that are established, communicated and maintained. And GV.RR-03 calls for adequate resources allocated to the risk strategy, roles, responsibilities and policies.

Who decides how much cybersecurity risk is accepted?

We help decide which controls the company needs and choose solutions and vendors with criteria defined before seeing proposals.

  • Risk diagnosis before recommending a tool
  • Controls and architecture based on the risks found
Explore cybersecurity
Cyrrus consultant reviewing cybersecurity risks with leadership

What falls to leadership?

CSF 2.0 devotes a section to communication among executives, managers and practitioners. According to NIST, the GOVERN function supports risk communication with executives: they set cybersecurity priorities and objectives, communicate expectations about risk appetite, accountability and resources, and are responsible for integrating cybersecurity risk management with enterprise risk management. In return, practitioners give them key performance and risk indicators so they understand the security posture and adjust the strategy.

ISO/IEC 27014 reaches the same point from the standard's side: its primary audience is the governing body and top management, and its mechanism is the cycle of evaluating, directing, monitoring and communicating.

If leadership only receives technical indicators and makes no decisions about risk, the company is managing cybersecurity, but not governing it.

How do NIST CSF 2.0 and ISO/IEC 27014 differ?

NIST CSF 2.0 and ISO/IEC 27014:2020 side by side
AspectNIST CSF 2.0ISO/IEC 27014:2020
What it isTaxonomy of high-level cybersecurity outcomes; does not prescribe how to achieve themGuidance on the concepts, objectives and processes of information security governance
PublicationFebruary 26, 20242nd edition, December 2020; corrected version April 2022
AudienceAny organization, regardless of size, sector or maturity; also executives and boardsGoverning body and top management; applies to organizations of all types and sizes
AccessPublic NIST publicationStandard sold by ISO

A practical detail: ISO lists 27014:2020 as published but at the revision stage, and announces it will be replaced by a new version under development. Before citing it in a contract or a policy, check which edition is current.

What does cybersecurity governance look like when it works?

The references do not define a set of documents, but each GOVERN category translates into something leadership can ask for and review. In our view, the five most useful are:

A risk appetite and tolerance statement that the board has read and approved (GV.RM). A named owner for each relevant risk, with authority to decide (GV.RR). A current policy, communicated and with a review date (GV.PO). A periodic report with a few indicators that lead to decisions, not to more reading (GV.OV). And a list of critical suppliers with the risk each one represents (GV.SC).

This translation is Cyrrus's judgment; what NIST states is the expected outcome of each category, not the document that proves it.

Vendors compared on the same criteria

We compare cybersecurity solutions and vendors on functional, technical, economic and sustainability criteria, with no manufacturer bias.

  • Criteria defined before seeing vendors
  • Independence from manufacturers
Talk to our team
Leadership team comparing cybersecurity vendors against defined criteria

When does it make sense to ask for outside help?

When nobody in leadership can answer three questions: which cybersecurity risk do we accept and which not, who answers for each one, and which indicator will we review each quarter. Also when security is about to be bought without having defined the risk it is meant to reduce.

If you decide to hire, independence from manufacturers is a selection criterion. To know what to ask, see the guide on signs your company needs cybersecurity help.

What should leadership decide?

There are five management decisions: how much cybersecurity risk the company accepts and who approved it; who answers for each relevant risk; which policy applies today and when it is reviewed; which indicators leadership will receive and how often; and which critical suppliers get a periodic review.

With those answers, the discussion about which tool to buy becomes a discussion about which risk to reduce, which is the one leadership knows how to have.

How we can help

At Cyrrus we help decide which controls the company needs and choose cybersecurity solutions and vendors with criteria defined before seeing proposals: risk diagnosis, controls and architecture, and vendor selection on the same four criteria as every selection.

If the underlying topic is how technology is governed in general, we start with IT strategy; and if the company is evaluating a framework such as COBIT, with a prior guide on when it makes sense to adopt it.

To go deeper: the business continuity plan and its RTO and RPO indicators, and the governance of artificial intelligence.

Jackson Bohorquez, CEO of Cyrrus Consulting Services
Jackson Bohorquez
CEO & Founder, Cyrrus Consulting Services

30 years in strategy and IT: Oracle consultant, IT leader at PepsiCo Latin America, Covidien and Coremar, and founder of Cyrrus in 2017. MBA, Universidad del Norte.

About the author
Published · November 18, 2026
Related service
Cybersecurity

Ready to connect the decision to the execution?

Tell us your organization's challenge. We'll set up a conversation with the right team and tell you straight whether we can help.

Not sure where to start? Request a free diagnostic session