|
controlSC-24
Fail in Known State (SC-24)
Fail to a [organization-defined] for the following failures on the indicated components while preserving [organization-defined] in failure: [organization-defined].
Security Baselines
HIGHLOWMODERATE
communicationsencryptionboundary-protectionnetwork
Why These Connect
Maps To4
These are equivalent or closely aligned requirements in other frameworks.
Baselined In1
This control is included in the linked security baseline (LOW, MODERATE, or HIGH).
Supports13
These related controls work together — a change to one may affect the others.
Related Controls(9)
CP-10System Recovery and Reconstitution (CP-10)
LMH
CP-12Safe Mode (CP-12)SC-22Architecture and Provisioning for Name/Address Resolution Service (SC-22)LMH
CP-2Contingency Plan (CP-2)LMH
CP-4Contingency Plan Testing (CP-4)LMH
SA-8Security and Privacy Engineering Principles (SA-8)LMH
SC-7Boundary Protection (SC-7)LMH
SI-13Predictable Failure Prevention (SI-13)SI-17Fail-safe Procedures (SI-17)Cross-Framework Mappings(4)
PR.DS-10PR.DS-10Final
NIST OLIR informative reference — Cybersecurity Framework v2.0 to SP 800-53 Rev 5
PR.IR-03PR.IR-03Final
NIST OLIR informative reference — Cybersecurity Framework v2.0 to SP 800-53 Rev 5
PR.DS-10PR.DS-10Final
NIST OLIR informative reference — Cybersecurity Framework v2.0 to SP 800-53 Rev 5
PR.IR-03PR.IR-03Final
NIST OLIR informative reference — Cybersecurity Framework v2.0 to SP 800-53 Rev 5
Organization-Defined Parameters(3)
Assignmentorganization-defined types of system failures on system components
Assignmentorganization-defined known system state
Assignmentorganization-defined system state information