Skip to main content

NIST Cybersecurity Framework 1.1 Overview

Understand the five core functions of NIST CSF 1.1 and how they support cybersecurity maturity.

Updated over 5 months ago

Overview

The NIST Cybersecurity Framework (CSF) 1.1 provides a standardized approach to managing and reducing cybersecurity risk. It helps organizations assess their current security posture and define actionable steps to improve resilience. This article outlines the five key functions of CSF 1.1, which form the foundation of Hyver’s maturity assessment for this version of the framework.


The Five NIST CSF 1.1 Functions

Each function represents a high-level area of cybersecurity management. Together, they provide a lifecycle approach to handling cyber threats.

1. Identify

Establishes an understanding of your organization’s cybersecurity risk.

  • Involves identifying systems, people, assets, data, and capabilities

  • Helps prioritize cybersecurity efforts aligned with risk tolerance and business needs


2. Protect

Implements safeguards to ensure the delivery of critical services.

  • Includes controls like access management, data protection, and security training

  • Aims to limit the potential impact of cybersecurity events


3. Detect

Defines actions to identify cybersecurity events.

  • Involves continuous monitoring, anomaly detection, and system alerts

  • Enables timely discovery of threats


4. Respond

Outlines response activities once an incident is detected.

  • Includes incident management, communication plans, and mitigation strategies

  • Helps contain and minimize damage


5. Recover

Focuses on restoring operations and capabilities after an incident.

  • Involves recovery planning, system restoration, and improvement efforts

  • Supports organizational resilience and post-incident learning


Wrap-up / Next Steps

NIST CSF 1.1 provides a flexible, structured foundation for cybersecurity planning. In Hyver, these five functions guide your maturity assessment and help you identify gaps and strengths across your security lifecycle.

Did this answer your question?