Framework · Cybersecurity · Voluntary
NIST CSF 2.0: functions, categories and how to assess your tier
The NIST Cybersecurity Framework (CSF) 2.0 is voluntary guidance from the US National Institute of Standards and Technology for managing cybersecurity risk. Published in February 2024, it organises outcomes into 6 functions, 22 categories and 106 subcategories. There is no certification; you assess yourself with profiles and tiers.
What you need to know about NIST CSF 2.0
Who uses NIST CSF 2.0?
It is voluntary, but these organisations commonly adopt it.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does NIST CSF 2.0 cover?
NIST CSF 2.0 describes cybersecurity outcomes in six functions. Govern sits at the centre and shapes the other five, which follow the life of a cyber risk from identifying it to recovering from an incident.
Govern
Strategy, risk appetite, roles, policy, oversight and supply chain risk.
In QULDEX: Board-ready reporting from live dataIdentify
Assets, risk assessment and improvement.
In QULDEX: Asset and risk registers linkedProtect
Access, training, data, platforms and resilience.
In QULDEX: Recurring evidence on scheduleDetect
Continuous monitoring and adverse event analysis.
In QULDEX: Monitoring evidence sampled by assessorsRespond
Incident management, analysis, communication and mitigation.
In QULDEX: Incidents tracked with ownersRecover
Recovery plan execution and communication.
In QULDEX: Recovery tests with resultsTiers 1–4
Partial, risk informed, repeatable, adaptive.
In QULDEX: Tier estimate on the dashboardWhat are the NIST CSF 2.0 categories?
CSF 2.0 has 22 categories across its 6 functions, each broken into subcategories (106 in total). Select any category to see the outcome it describes, typical evidence and the matching ISO 27001, SOC 2 and CIS controls.
Showing up to 6 per group. Search, filter, or open a group to see all 22.
Govern 6
GV.OCOrganizational contextNew or reshaped in 2.0Understand the mission, stakeholder expectations, dependencies and legal requirements that shape cybersecurity risk decisions.
In QULDEXContext and dependencies are recorded once and drive the target profile.
- Typical evidence
- Mission and dependency analysis
- Maps to
- ISO 27001 4.14.2
GV.RMRisk management strategyNew or reshaped in 2.0Set and communicate risk priorities, appetite, tolerance and assumptions.
In QULDEXRisk appetite and tolerance live in the risk register beside each risk.
- Typical evidence
- Risk appetite statement
- Maps to
- ISO 27001 6.1
GV.RRRoles, responsibilities and authoritiesNew or reshaped in 2.0Set cybersecurity roles, responsibilities and authorities, with leadership accountable.
In QULDEXOwners are assigned per category with approval history.
- Typical evidence
- RACI, role descriptions
- Maps to
- ISO 27001 5.3A.5.2SOC 2 CC1.3
GV.POPolicyNew or reshaped in 2.0Set, communicate, enforce and review cybersecurity policy.
In QULDEXPolicies are versioned with approvals and linked to the categories they support.
- Typical evidence
- Approved policy set
- Maps to
- ISO 27001 5.2A.5.1
GV.OVOversightNew or reshaped in 2.0Use results of risk management activities to adjust strategy.
In QULDEXBoard and leadership reviews are packaged from live readiness data.
- Typical evidence
- Leadership review minutes
- Maps to
- ISO 27001 9.3
GV.SCCybersecurity supply chain risk managementNew or reshaped in 2.0Identify, assess and manage risks from suppliers and third parties.
In QULDEXEach supplier gets one record with assessment, contract and renewal date.
- Typical evidence
- Supplier inventory and assessments
- Maps to
- ISO 27001 A.5.19–A.5.23SOC 2 CC9.2CIS 15
Identify 3
ID.AMAsset managementIdentify and manage hardware, software, services, data and systems in line with their importance.
In QULDEXAsset inventories attach as evidence and link to controls.
- Typical evidence
- Asset and software inventories
- Maps to
- ISO 27001 A.5.9CIS 1CIS 2
ID.RARisk assessmentUnderstand cybersecurity risk to the organisation, assets and individuals.
In QULDEXThe risk register holds assessments; scan results feed it.
- Typical evidence
- Risk assessment, vulnerability scans
- Maps to
- ISO 27001 6.1.2A.8.8SOC 2 CC3.2CIS 7
ID.IMImprovementNew or reshaped in 2.0Identify improvements from evaluations, tests and incidents.
In QULDEXImprovements become tracked CAPA items.
- Typical evidence
- Improvement log
- Maps to
- ISO 27001 10.110.2
Protect 5
PR.AAIdentity management, authentication and access controlLimit access to assets to authorised users, services and hardware.
In QULDEXAccess reviews run as recurring tasks; revocations become tracked actions.
- Typical evidence
- Access reviews, MFA settings
- Maps to
- ISO 27001 A.5.15–A.5.18A.8.5SOC 2 CC6.1–CC6.3CIS 5CIS 6
PR.ATAwareness and trainingGive personnel the awareness and skills to do cybersecurity-related tasks.
In QULDEXTraining completion is imported and checked against headcount.
- Typical evidence
- Training completion records
- Maps to
- ISO 27001 A.6.3SOC 2 CC1.4CIS 14
PR.DSData securityManage data in line with risk strategy to protect confidentiality, integrity and availability.
In QULDEXEncryption and backup evidence is collected on schedule.
- Typical evidence
- Encryption settings, backup tests
- Maps to
- ISO 27001 A.8.13A.8.24SOC 2 CC6.7A1.2CIS 3CIS 11
PR.PSPlatform securityNew or reshaped in 2.0Manage hardware, software and services of physical and virtual platforms securely.
In QULDEXConfiguration baselines and patch evidence attach per platform.
- Typical evidence
- Hardening baselines, patch records
- Maps to
- ISO 27001 A.8.9A.8.19CIS 4
PR.IRTechnology infrastructure resilienceNew or reshaped in 2.0Manage security architectures to protect assets and keep the organisation resilient.
In QULDEXResilience tests and network segmentation evidence are scheduled.
- Typical evidence
- Network diagrams, resilience tests
- Maps to
- ISO 27001 A.8.14A.8.20–A.8.22CIS 12
Detect 2
DE.CMContinuous monitoringMonitor assets to find anomalies, indicators of compromise and other adverse events.
In QULDEXMonitoring evidence is collected on schedule and sampled by assessors.
- Typical evidence
- SIEM coverage, alert reviews
- Maps to
- ISO 27001 A.8.16SOC 2 CC7.2CIS 13
DE.AEAdverse event analysisAnalyse anomalies and potential adverse events to characterise them and detect incidents.
In QULDEXEvent triage records link to incidents in the same workspace.
- Typical evidence
- Triage records
- Maps to
- ISO 27001 A.5.25SOC 2 CC7.3
Respond 4
RS.MAIncident managementManage responses to detected incidents.
In QULDEXIncidents are logged with owners, timelines and evidence.
- Typical evidence
- Incident tickets, response plan
- Maps to
- ISO 27001 A.5.24A.5.26SOC 2 CC7.4CIS 17
RS.ANIncident analysisInvestigate to support effective response and forensics.
In QULDEXInvestigation notes and evidence stay linked to the incident.
- Typical evidence
- Investigation records
- Maps to
- ISO 27001 A.5.28
RS.COIncident response reporting and communicationCoordinate response with internal and external stakeholders as required by law and policy.
In QULDEXNotifications and deadlines are tracked per incident.
- Typical evidence
- Notification records
- Maps to
- ISO 27001 A.5.5A.5.26
RS.MIIncident mitigationContain incidents and reduce their effects.
In QULDEXContainment actions are tracked to closure.
- Typical evidence
- Containment records
- Maps to
- ISO 27001 A.5.26
Recover 2
RC.RPIncident recovery plan executionRestore assets and operations affected by incidents.
In QULDEXRecovery tests and actual recoveries are logged with results.
- Typical evidence
- Recovery plan, test results
- Maps to
- ISO 27001 A.5.29A.5.30SOC 2 A1.3CIS 11
RC.COIncident recovery communicationCoordinate restoration activities with internal and external parties.
In QULDEXRecovery communications are recorded against the incident.
- Typical evidence
- Recovery communications
- Maps to
- ISO 27001 A.5.26
Nothing matches that search.
Category identifiers and names follow NIST CSWP 29 (CSF 2.0). Summaries are QULDEX paraphrases; the NIST text is the authority. "New or reshaped" marks categories introduced or substantially restructured in 2.0.
How do you implement and assess NIST CSF 2.0?
There is no certification. You build a current profile, set a target profile, close the gaps and reassess, often with an independent assessor. A first cycle usually takes 3 to 6 months.
Set scope and priorities (Govern)
Agree mission priorities, risk appetite, roles and which parts of the organisation are in scope.
Build your current profile
Rate how well you achieve each category and subcategory today, with evidence.
Assess risk and set a target profile
Decide which outcomes and tier you need, based on risk, law and customers.
Plan and close the gaps
Turn the difference between profiles into a prioritised action plan with owners.
Independent assessment (optional)
An internal audit team or third party tests evidence against the target profile.
Report to leadership and repeat
QuarterlyTrack gap closureYearlyRefresh current profileOn changeUpdate target profile
Durations are typical planning ranges from QULDEX delivery. NIST does not certify organisations or assessors.
What documents does a NIST CSF 2.0 program need?
CSF doesn't mandate documents, but assessors and leadership expect these artifacts to show the program is real.
| Artifact | CSF element | Where it lives in QULDEX |
|---|---|---|
| Current profile | Profiles | Pre-mapped control library |
| Target profile | Profiles | Program dashboard |
| Risk appetite and strategy | GV.RM | Risk register |
| Roles and responsibilities | GV.RR | Program setup |
| Cybersecurity policies | GV.PO | Evidence vault · policy library |
| Supplier risk program | GV.SC | Vendor register |
| Asset inventory | ID.AM | Evidence vault |
| Action plan for gaps | ID.IM | CAPA automation |
| Incident response plan | RS.MA | Evidence vault |
| Recovery plan and tests | RC.RP | Evidence vault |
NIST provides profile templates and quick-start guides; QULDEX holds them as structured records.
How long does NIST CSF 2.0 take and what drives the effort?
A first current and target profile usually takes 2 to 3 months; closing gaps depends on the target tier. Effort grows with the number of business units, systems and critical suppliers.
Where the time goes
Bars show the upper end of each range on one scale (6 months = full width).
What changes the effort
- Target tier: moving from Tier 2 to Tier 3 means repeatable, documented processes
- Business units: each unit may need its own profile
- Supply chain: GV.SC grows with each critical supplier
- Existing ISO 27001 or SOC 2: reused controls fill many subcategories
- Assessment depth: an independent assessment adds testing and sampling
Which NIST CSF tier are you closest to?
Answer eight questions to estimate your tier and the categories to improve first. Nothing you enter leaves this page.
How NIST CSF 2.0 maps to ISO 27001, SOC 2 and CIS Controls
CSF describes outcomes; ISO 27001, SOC 2 and CIS Controls describe how to achieve them. NIST publishes informative references for these mappings, so one tested control can count toward all of them.
NIST CSF 2.0 vs ISO 27001 at a glance
| NIST CSF 2.0 | ISO 27001 | |
|---|---|---|
| What it is | Voluntary outcome framework | Certifiable management-system standard |
| Who publishes it | NIST (US government) | ISO and IEC |
| Result | Current and target profiles, tier estimate | Certificate from an accredited body |
| Cost to access | Free | Standard must be purchased |
| Structure | 6 functions, 22 categories, 106 subcategories | Clauses 4–10 plus 93 Annex A controls |
| Best for | Common language, board reporting, US context | Proof to customers worldwide |
| In QULDEX | QULDEX maps CSF subcategories to ISO 27001 controls so one evidence set supports both. | |
Category crosswalk
| NIST CSF 2.0 | ISO 27001:2022 | SOC 2 | CIS v8.1 | Shared evidence |
|---|---|---|---|---|
| GV.RR Roles | A.5.2 | CC1.3 | — | RACI |
| GV.SC Supply chain | A.5.19–A.5.23 | CC9.2 | 15 | Supplier assessments |
| ID.AM Assets | A.5.9 | CC6.1 | 1 · 2 | Asset inventories |
| ID.RA Risk assessment | 6.1.2 · A.8.8 | CC3.2 · CC7.1 | 7 | Risk register, scans |
| PR.AA Access control | A.5.15–A.5.18 · A.8.5 | CC6.1–CC6.3 | 5 · 6 | Access reviews, MFA |
| PR.AT Training | A.6.3 | CC1.4 · CC2.2 | 14 | Training records |
| PR.DS Data security | A.8.13 · A.8.24 | CC6.7 · A1.2 | 3 · 11 | Encryption, backups |
| DE.CM Monitoring | A.8.16 | CC7.2 | 13 | SIEM reviews |
| RS.MA Incidents | A.5.24–A.5.26 | CC7.3–CC7.5 | 17 | Incident records |
| RC.RP Recovery | A.5.29 · A.5.30 | A1.3 | 11 | Recovery tests |
Indicative mapping aligned to NIST's informative references approach. The full crosswalk is in the QULDEX control library.
How QULDEX runs NIST CSF 2.0 from current profile to board report
QULDEX is NIST CSF compliance and audit management software built from EGV Group's audit delivery, used by the organisation and by the assessors who test it. Pick your role to see who does what.
For CISOs and security teams adopting CSF 2.0.
- ScopeSet prioritiesMission, risk appetite and scope recorded once
- Current profileRate each categoryProfile scoring with evidence per subcategory
- Target profileChoose the target tierGap view between current and target
- Close gapsRun the action planGaps become CAPA items with owners
- AssessmentHost the assessorControlled, logged evidence sharing
- ReportBrief the boardCISO dashboard with tier trend
For cyber consultants and internal audit teams.
- ScopeRun the assessmentA reusable CSF 2.0 assessment template
- Current profileScore with evidenceEvidence requests with review states
- Target profileRecommend targetsTarget profiles per client or unit
- Close gapsTrack remediationAction plans across clients
- AssessmentTest controlsSampling and findings in the audit workspace
- ReportReport to leadershipBoard-ready reports
For third parties assessing CSF alignment.
- PlanningAgree scope and targetScope and target profile in a standard format
- FieldworkReview evidenceView-only evidence access with download control and an access log
- TestingSample controlsSampling per subcategory
- FindingsRecord gapsFindings linked to categories
- ReportIssue the assessmentTraceable workpapers
- Next cycleReassessHistory kept for the next year
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →How do you run a NIST CSF 2.0 audit?
A NIST CSF audit checks, with evidence, how far each CSF outcome is achieved and where the gaps are. It is an assessment against your own target profile; there is no pass or fail and no certificate.
Set the scope
Decide which business units, systems and suppliers the audit covers, and which of the 22 categories apply.
Collect evidence for each subcategory
Gather the policy, record or system output that shows each outcome is met, and link it to the subcategory it supports.
Test and rate each outcome
Rate every subcategory as achieved, partly achieved or not achieved, and note what the rating is based on. The result is your current profile.
Compare with the target profile
Set the outcomes and tier the organisation needs, then list every gap between current and target.
Report findings and track the fixes
Record each gap as a finding with an owner and a due date, and follow it until the fix is verified.
NIST CSF 2.0 questions people ask
How do you audit against NIST CSF 2.0?
A NIST CSF audit is an assessment, not a certification audit. You set the scope, record how well each of the 106 subcategories is achieved today with evidence, compare that current profile with a target profile, and report the gaps with an action plan. An independent assessor can run it, but NIST issues no certificate.
What is new in NIST CSF 2.0?
CSF 2.0 adds a sixth function, Govern, widens the scope beyond critical infrastructure to all organisations, expands supply chain risk management, and adds quick-start guides and implementation examples.
Can you get NIST CSF certified?
No. NIST does not certify organisations. You can self-assess or have a third party assess your alignment against a target profile.
What are the 6 functions of NIST CSF 2.0?
Govern, Identify, Protect, Detect, Respond and Recover.
What are NIST CSF tiers?
Tiers describe how rigorous your cybersecurity risk governance and management are: Tier 1 Partial, Tier 2 Risk Informed, Tier 3 Repeatable, Tier 4 Adaptive.
Is NIST CSF mandatory?
It is voluntary for most organisations, though some regulators, contracts and sector bodies require or reference it.
How does NIST CSF relate to ISO 27001?
CSF describes outcomes; ISO 27001 is a certifiable management system with controls that achieve many of them. NIST publishes mappings between them.
Can QULDEX run NIST CSF alongside ISO 27001 and SOC 2?
Yes. CSF subcategories, ISO 27001 controls and SOC 2 criteria are mapped once, so the same evidence supports each.
Go deeper on NIST CSF 2.0
NIST CSF 2.0: the Govern function explained
What Govern adds and how to evidence it.
blog.quldex.comNIST frameworks hub
CSF, 800-53 and AI RMF articles in one place.
blog.quldex.comAudit evidence naming convention
A file-naming scheme that lets assessors sample without asking.
blog.quldex.comAudit sampling size for compliance
How many samples assessors pull, and why.
References
- NIST CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0, 26 February 2024. nist.gov
- NIST CSF 2.0 Quick-Start Guides and Implementation Examples. nist.gov
- NIST Informative References (OLIR) for CSF 2.0. nist.gov
- CIS Critical Security Controls v8.1. cisecurity.org
- ISO/IEC 27001:2022. iso.org
Reviewed by
Page history
- : Rebuilt with all 22 categories, tier estimate, profiles path and crosswalk
- : Page first published
Estimate your NIST CSF tier in 2 minutes
Answer eight questions and get a tier estimate with the categories to improve first. No sales call needed to see the result.