NIST Cybersecurity Framework 2.0
A voluntary framework organized around six functions — Govern, Identify, Protect, Detect, Respond, Recover — published in February 2024. Version 2.0 added the Govern function and broadened scope beyond critical infrastructure to organizations of all sizes and sectors.
Why it matters for autonomous finance
The security counterpart to the AI-specific frameworks, and it shares the NIST AI RMF's structural insight: Govern comes first, because organizational accountability precedes technical control. For agentic systems the relevant surfaces are supply chain and detection — a model, its weights, its training data and its retrieval corpus are all supply chain, and poisoning any of them is a security event that presents as a model quality problem.
What it does not cover
General cybersecurity, not AI governance. It will harden the infrastructure an agent runs on and has nothing to say about whether the agent should have acted. Mapping it to AI risk requires the AI RMF alongside it; neither is sufficient alone, and claiming CSF alignment as an AI governance answer is a common overclaim.
No model behavior, no authority, no agent identity. Every entry in this register carries this section. A standard read past its scope is worse than no standard, because it produces confidence without coverage.
Read it
Other standards in the register
Source and provenance
- Issuing body
- US National Institute of Standards and Technology
- Canonical source
- https://www.nist.gov/cyberframework
- Version
- NIST Cybersecurity Framework 2.0
- Dates
- published February 2024
- Last verified
- Next review due
- Recorded claims
- nist-csf-2 (2026-08-02)
- Content held
- This corpus holds no copy of the source's text; the record is a citation, and no content digest can be given.
- Third-party material
- The framework, its text, identifiers and version belong to its issuing body (US National Institute of Standards and Technology). This corpus cites it, reproduces none of its text, and grants no rights in it.
- This corpus's work
- The summary, why-it-matters, caveat, gap statement and MARQUE mapping on this page are this corpus's own editorial work, under the terms at https://qistrust.com/license/.
Dates are when each recorded claim was last checked against its primary source (the verification register), not when this build ran; last verified is the oldest of them. The same record, field for field, is in api/provenance.json (qis-provenance-1) and in this page's structured data.