What Is the NIST Cybersecurity Framework?
The NIST Cybersecurity Framework (CSF) is a voluntary guidance framework developed by the U.S. National Institute of Standards and Technology. Originally published in 2014 and updated to version 2.0 in February 2024, it provides a structured approach to managing cybersecurity risk that is applicable to organizations of any size, sector, or maturity level.
While NIST CSF originated in the United States, it has become a globally recognized standard. Many European organizations use it alongside EU regulations like NIS2 and DORA, as the framework's structure maps well to these regulatory requirements. The framework is technology-neutral and outcome-focused, making it adaptable to any environment.
NIST CSF 2.0 organizes cybersecurity activities into six core functions: Govern, Identify, Protect, Detect, Respond, and Recover. The addition of "Govern" as a separate function in version 2.0 reflects the growing importance of cybersecurity governance and management accountability — a theme echoed by NIS2's management liability provisions.
The 6 Core Functions
Govern (GV) is the newest function, added in CSF 2.0. It establishes and monitors the organization's cybersecurity risk management strategy, expectations, and policy. It addresses how cybersecurity decisions are made, who is responsible, and how performance is measured. This function underpins all others.
Identify (ID) focuses on developing organizational understanding to manage cybersecurity risk. This includes asset management, risk assessment, business environment understanding, and supply chain risk identification. You cannot protect what you do not know you have.
Protect (PR) outlines safeguards to ensure delivery of critical services. This includes access control, security awareness training, data security, information protection processes, and maintenance of protective technology.
Detect (DE) defines activities to discover cybersecurity events in a timely manner. Effective detection requires security monitoring, anomaly detection, and continuous monitoring of systems and networks.
Respond (RS) covers actions taken regarding a detected cybersecurity incident. This includes response planning, communications, analysis, mitigation, and improvements based on lessons learned.
Recover (RC) addresses activities to maintain resilience and restore any capabilities or services impaired due to a cybersecurity incident. This includes recovery planning, improvements, and communications.
Maturity Levels Explained
Level 1 — Initial: Cybersecurity activities are ad hoc and reactive. There are no formal processes, documentation is minimal or absent, and responses depend on individual heroics rather than systematic approaches. Most startups begin here.
Level 2 — Developing: Some processes exist but are inconsistently applied. Documentation may exist for certain areas but is incomplete. The organization is aware of the need for security but has not yet standardized its approach.
Level 3 — Defined: Processes are documented, standardized, and consistently followed across the organization. Policies are approved by management, roles are assigned, and there is a systematic approach to security. This is often the minimum target for regulatory compliance.
Level 4 — Managed: Security processes are measured using metrics and KPIs. Performance is monitored and reported to management regularly. The organization uses data to make informed decisions about security investments and improvements.
Level 5 — Optimizing: The organization continuously improves its security posture based on lessons learned, threat intelligence, and industry developments. Processes are adaptive and predictive. Security is deeply integrated into business strategy and culture.
Frequently Asked Questions
What maturity level should my organization target?
Most organizations should aim for at least Level 3 (Defined) across all functions as a baseline for regulatory compliance. Level 4 (Managed) is appropriate for organizations in regulated sectors or those handling sensitive data. Level 5 is typically reserved for organizations with mature security programmes in high-risk environments. The right target depends on your risk profile, sector, and regulatory requirements.
How does NIST CSF relate to NIS2 and DORA?
NIST CSF is a framework, while NIS2 and DORA are regulations. The CSF's six functions map well to NIS2 and DORA requirements — for example, NIS2's risk management requirements align with CSF's Identify and Govern functions, and DORA's incident management requirements align with Detect and Respond. Using NIST CSF as your internal framework helps demonstrate compliance with EU regulations.
How often should I reassess maturity?
Conduct a full maturity assessment at least annually. Additionally, reassess specific functions after significant changes (new systems, reorganization, major incidents) or when new regulatory requirements come into effect. Track scores over time to demonstrate improvement to management and auditors.
Is my assessment data stored?
No. All assessment data stays in your browser. Nothing is sent to any server. Take a screenshot or note your scores before leaving the page, as data is lost on refresh or close.
Related Tools
NIS2 Readiness Assessment
Map your maturity to NIS2 compliance requirements.
Security Policy Generator
Generate policies to move from Level 1-2 to Level 3+.
Related Articles
NIS2 Directive Explained
Map your maturity to NIS2 compliance.
How to Write an Incident Response Plan
Respond function starts with a documented plan.
Disclaimer: This is a self-assessment tool for informational purposes. Maturity scores are based on your own evaluation and may differ from formal third-party assessments. NIST CSF is a framework by the National Institute of Standards and Technology. Created by ClevSec.
Last updated: March 2026