| 2 minute read

Focusing In On the New “Govern” Function in NIST CSF 2.0

nist 2.0

In February 2024, the National Institute of Standards and Technology (NIST) released Version 2.0 of the Cybersecurity Framework (CSF or the Framework) which is the first significant update to the Framework since 2014 when it was first created.

Although the CSF is voluntary, it has become a key standard for assessing the maturity and management of a cybersecurity program and its related risk. While there are multiple enhancements in CSF 2.0, the “Govern” function is the change that may have the largest impact, as this function should help organizations and compliance teams map and meet various laws and regulations while managing their cyber programs.

The core of the CSF is organized into six key functions: Identify, Protect, Detect, Respond, Recover, and Govern. The new Govern function stresses the importance of governance activities being included within and/or aligned with risk management and compliance strategies alike. It indicates an increased expectation for organizations to understand and document their business environment, cybersecurity strategy, risk analysis, and supply chain risk management. In addition to establishing policies, procedures, and strategies around these areas, equal importance revolves around identifying proper roles and responsibilities for these activities and oversight strategies for leadership, board of directors, or similar key stakeholders.

Risk management is mentioned in many frameworks, laws, and regulations related to cybersecurity, but without a solid process of ongoing evaluation and analysis, many organizations fall short on these practices. The new Govern function is going to help tackle this issue, pushing organizations to perform risk management in a more comprehensive manner. For example, there is a “Risk Management Strategy” category, and its subcategories indicate that risk management activities and outcomes should be included in enterprise risk management processes, and that organizations should establish and communicate a “standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks.”

Additionally, the “Roles, Responsibilities, and Authorities” category states that “organizational leadership is responsible and accountable for cybersecurity risk.” If you look more closely, an implementation example specifically notes the role of the board of directors, demonstrating a broader expectation that senior leadership at the highest level has a role in managing cybersecurity risk throughout the organization. Sound familiar? This message has been being conveyed by regulators and industry experts for a while now and if you haven’t done so already, it’s time to make sure those overseeing your cybersecurity program have appropriate knowledge to do so, either through training or personal experience.

Another familiar topic is presented within the Govern function’s “Supply Chain Risk Management” category. Its focus is on gaining understanding of your third-party ecosystem and then ensuring that the proper controls to manage the various risks are implemented through policy, people, technology, and processes. The companies that make up your supply chain should be documented, risk ranked, and assessed both before partnering with them, and regularly thereafter. If they are a critical part of your organization’s systems or processes, they should be included in incident response, business contingency, and disaster recovery planning.

Here is the full break down of the Govern function, including the six categories and 31 subcategories:

NIST 2.0 p 1

NIST 2.0 p2

NIST 2.0 p 3

As organizations conduct assessments leveraging CSF 2.0, organizations should consider reviewing the “Implementation Examples” and assess the extent to which their policies and procedures align. The new Implementation Examples will arm organizations to more effectively and efficiently apply 2.0 of the Framework.

NIST has also created a CSF 2.0 Resource Center that includes quick start guidance, profiles, and informative references to help organizations as they work with the Framework. These resources can be found on NIST’s website at https://www.nist.gov/cyberframework.

Blog Articles

The CDK Incident and Recommended Actions from Avalon Cyber

Thousands of car dealerships’ operations slowed to a halt last Wednesday as their core dealer management system, CDK, shut down. CDK Global announced that they were investigating a cyber incident and “Out of an abundance of caution and concern for our customers, we have shut down most of our systems and are working diligently to get everything up and running as quickly as possible” according to spokesperson, Lisa Finney. The company said later that day that most of their critical systems were back online, but the next day they announced that another incident had happened.

Get Ready for the New 36-Hour Cyber Breach Notification Rule for Financial Institutions

If you’re in the financial sector, no doubt you’ve already heard, and hopefully, are prepared or preparing for, the new federal banking rule regarding cyber breach notifications. This new rule, which took effect April 1, 2022, with full compliance required by May 1, 2022, requires banking organizations and bank service providers to notify banking regulators within 36 hours after a notification event, which is the tightest timeframe in U.S. history.

Cybercriminals Never Sleep (And Neither Do We)

According to the latest cybersecurity industry research, market demand for Managed Detection and Response (MDR) services continues to climb. In fact, experts forecast that by 2024, 40% of midsize enterprises will use MDR as their only managed security service. That might sound like a large percentage, but because of the continued escalation of cyberattacks, more and more companies are realizing the importance of hiring experts to boost their cybersecurity posture.