id: "CP-04(05)" title: "Self-challenge" family: "CP" family_name: "Contingency Planning" sort_id: "cp-04.05" priority: "P2" implementation_level: "system" parent: "CP-04" enhancement: True
Statement
Employ {{ insert: param, cp-04.05_odp.01 }} to {{ insert: param, cp-04.05_odp.02 }} to disrupt and adversely affect the system or system component.
Guidance
Often, the best method of assessing system resilience is to disrupt the system in some manner. The mechanisms used by the organization could disrupt system functions or system services in many ways, including terminating or disabling critical system components, changing the configuration of system components, degrading critical functionality (e.g., restricting network bandwidth), or altering privileges. Automated, on-going, and simulated cyber-attacks and service disruptions can reveal unexpected functional dependencies and help the organization determine its ability to ensure resilience in the face of an actual cyber-attack.
Assessment Objective
{{ insert: param, cp-04.05_odp.01 }} are employed to disrupt and adversely affect the {{ insert: param, cp-04.05_odp.02 }}.
Contingency planning policy
procedures addressing system recovery and reconstitution
contingency plan
contingency plan test documentation
contingency plan test results
system security plan
other relevant documents or records
Organizational personnel with contingency plan testing responsibilities
organizational personnel with system recovery and reconstitution responsibilities
organizational personnel with information security responsibilities
Organizational processes for contingency plan testing
mechanisms supporting contingency plan testing