Applicable (Y)es / (N)o |
(C)onfidentiality |
(I)ntegrity |
(A)vailability |
RPN (C+I+A) |
(S)atisfactory |
||||||
L1 |
M2 |
H3 |
L1 |
M2 |
H3 |
L1 |
M2 |
H3 |
(O)ther than satisfactory +## |
||
|
|
|
|
|
|
|
|
|
|
|
|
###
sc-24 |
fail in known state |
|
|
assessment objective: Determine if: |
|
sc-24[1] |
the organization defines a known-state to which the information system is to fail in the event of a system failure; |
|
sc-24[2] |
the organization defines types of failures for which the information system is to fail to an organization-defined known-state; |
|
sc-24[3] |
the organization defines system state information to be preserved in the event of a system failure; |
|
sc-24[4] |
the information system fails to the organization-defined known-state for organization-defined types of failures; and |
|
sc-24[5] |
the information system preserves the organization-defined system state information in the event of a system failure. |
|
potential assessment methods and objects: Examine: [select from: System and communications protection policy; procedures addressing information system failure to known state; information system design documentation; information system configuration settings and associated documentation; list of failures requiring information system to fail in a known state; state information to be preserved in system failure; information system audit records; other relevant documents or records]. Interview: [select from: System/network administrators; organizational personnel with information security responsibilities; system developer]. Test: [select from: Automated mechanisms supporting and/or implementing fail-in-known state capability; automated mechanisms preserving system state information in the event of a system failure]. |