Govern NIST Cybersecurity Framework 2.0

NIST Cybersecurity Framework: Govern Security Controls

Establish and monitor the organization's cybersecurity risk management strategy, expectations, and policy.

31 controls
6 critical
142h est. effort
6 categories

Organizational Context

Oversight

Policy

Risk Management Strategy

gv-rm-1

Risk management objectives are established and agreed to by organizational stakeholders

Without agreed-upon risk management objectives, different parts of the organization will make securi...

gv-rm-2

Risk appetite and risk tolerance statements are established, communicated, and maintained

Risk appetite and tolerance statements answer the question of how much risk the organization is will...

gv-rm-3

Cybersecurity risk management activities and outcomes are included in enterprise risk management processes

Cybersecurity risk that is managed in isolation from the broader enterprise risk program often fails...

gv-rm-4

Strategic direction that describes appropriate risk response options is established and communicated

When a new risk is identified, teams need to know what response options are available and which are ...

gv-rm-5

Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties

Cybersecurity risks do not respect organizational boundaries. A vulnerability in a supplier's system...

gv-rm-6

A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated

When different teams assess risk using different methods, you end up with an apples-to-oranges risk ...

gv-rm-7

Strategic opportunities (positive risks) are characterized and included in organizational cybersecurity risk discussions

Risk management is usually framed around threats, but security capabilities also create strategic op...

Roles, Responsibilities, and Authorities

Cybersecurity Supply Chain Risk Management

gv-sc-1

A cybersecurity supply chain risk management program is established

Your security is only as strong as your weakest vendor. Third-party software, SaaS tools, and servic...

gv-sc-10

Supply chain risk management plans include provisions for activities after a supplier relationship ends

Ending a vendor relationship is a high-risk security event that most organizations handle poorly. Da...

gv-sc-2

Cybersecurity roles and responsibilities for suppliers and partners are established and coordinated

When a supplier causes a breach or an outage, ambiguity about who is responsible for what turns a ma...

gv-sc-3

Supply chain risk management is integrated into enterprise risk management processes

Vendor risks that live in a separate silo never get prioritized against business risks. When a criti...

gv-sc-4

Suppliers are known and prioritized by criticality

Most organizations have dozens or hundreds of vendors but only a handful that could cause catastroph...

gv-sc-5

Cybersecurity requirements are integrated into contracts with suppliers

A vendor agreement that says nothing about security gives you no leverage when something goes wrong....

gv-sc-6

Due diligence is performed before entering into supplier relationships

The cheapest time to find a security problem with a vendor is before you sign a contract. Once a sup...

gv-sc-7

Risks from suppliers are assessed, monitored, and responded to throughout the relationship

A vendor that passed their security review two years ago may look very different today. They may hav...

gv-sc-8

Relevant suppliers are included in incident planning, response, and recovery activities

Incidents rarely stay within your own perimeter. A breach at a key supplier can trigger your inciden...

gv-sc-9

Supply chain security practices are monitored throughout the technology product and service life cycle

A vendor's security posture at the time of acquisition is not their security posture two years into ...