SC-24—Fail in Known State
High
>Control Description
Fail to a ⚙organization-defined known system state for the following failures on the indicated components while preserving ⚙organization-defined system state information in failure: ⚙list of organization-defined types of system failures on organization-defined system components.
>FedRAMP Baseline Requirements
No FedRAMP-specific parameter values or requirements for this baseline.
>Discussion
Failure in a known state addresses security concerns in accordance with the mission and business needs of organizations. Failure in a known state prevents the loss of confidentiality, integrity, or availability of information in the event of failures of organizational systems or system components. Failure in a known safe state helps to prevent systems from failing to a state that may cause injury to individuals or destruction to property.
Preserving system state information facilitates system restart and return to the operational mode with less disruption of mission and business processes.
>Cross-Framework Mappings
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What policies govern the implementation of fail in known state?
- •How are system and communications protection requirements defined and maintained?
- •Who is responsible for configuring and maintaining the security controls specified in SC-24?
Technical Implementation:
- •How is fail in known state technically implemented in your environment?
- •What systems, tools, or configurations enforce this protection requirement?
- •How do you ensure that fail in known state remains effective as the system evolves?
Evidence & Documentation:
- •What documentation demonstrates the implementation of SC-24?
- •Can you provide configuration evidence or system diagrams showing this protection control?
- •What logs or monitoring data verify that this control is functioning correctly?
Ask AI
Configure your API key to use AI features.