SC-25 Thin Nodes. Employ minimal functionality and information storage on the following system components: [organization-defined]
Thin Nodes. Employ minimal functionality and information storage on the following system components: [organization-defined].
5
artefacts
1
held by a system
1
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
- Configuration evidence showing minimal functionality and minimal local information storage on those components · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Verification that data does not accumulate locally, for example through inspection of local storage · Document repository
governing documentDocuments that govern the control
- The defined system components required to operate as thin nodes · Document repository
- Baseline showing what functions and storage were removed or disabled · Policy repository / GRC workspace
- Change control preventing functionality being added back to thin nodes · 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
- Thin client deployed while local caching, print spooling and profile storage retain data on the device
- Minimal build defined at rollout with agents and tools added afterwards, restoring the surface
- No verification of local storage, so the minimal claim is untested
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-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] · SC-26 Decoys. Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks