SC-24 Fail in Known State. Fail to a [organization-defined] for the following failures on the indicated components while preserving [organization-defined] in failure: [organization-defined]
Fail in Known State. Fail to a [organization-defined] for the following failures on the indicated components while preserving [organization-defined] in failure: [organization-defined].
5
artefacts
1
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Design and configuration evidence implementing the fail to known state behaviour on the named components · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Test records demonstrating the behaviour for each defined failure type · Document repository
- Evidence that preserved state does not itself leak information or leave access open · Document repository
governing documentDocuments that govern the control
- The defined list of failures that require the system to fail to a known state · Document repository
- The defined known state and the system state information to be preserved in failure · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Failure list covers component crash but not the security function failures that matter most
- Known state undefined, so the system fails open on some paths and closed on others
- Behaviour never tested, so the fail safe design is unverified
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetSC-23 Session authenticity · SC-25 Thin Nodes. Employ minimal functionality and information storage on the following system components: [organization-defined]