NIST Cybersecurity Framework 2.0
CSF 2.0 organizes cybersecurity outcomes across Govern, Identify, Protect, Detect, Respond, and Recover and can be applied alongside OT-specific guidance.
What the authority record establishes
CSF 2.0 organizes cybersecurity outcomes across Govern, Identify, Protect, Detect, Respond, and Recover and can be applied alongside OT-specific guidance.
Voluntary unless adopted through policy, contract, program, or authority
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
The Govern function and outcome language help connect OT defense evidence to enterprise accountability without replacing the system-specific detail in SP 800-82 or ISA/IEC 62443.
Affected operating stages
- Govern
- Identify
- Protect
- Detect
- Respond
- Recover
Capabilities to examine
Asset Criticality And Operational Context
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for asset criticality and operational context.
Compliance Mapping And Control Evidence
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for compliance mapping and control evidence.
Cyber-Risk Quantification And Executive Reporting
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for cyber-risk quantification and executive reporting.
Incident Response And Recovery Support
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for incident response and recovery support.
Multi-Site Sensor, Data, And Policy Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for multi-site sensor, data, and policy management.
Affected buyer audiences
- executives
- risk leaders
- security leaders
- program owners
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
A framework mapping does not establish implementation, maturity, compliance, or outcome.