SC-26 Decoys. Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks
Decoys. Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks.
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
- Detection configuration showing interaction with a decoy raises an alert · SIEM / log platform
periodic reviewEvidence produced at each review
- Records of interactions detected and how each was analysed · Document repository
- Evidence legitimate users and scanners cannot trip decoys routinely, which would destroy their signal value · Document repository
governing documentDocuments that govern the control
- Identification of the decoy components deployed and their placement within the system · Document repository
- Design documentation showing decoys are isolated so an attack on them cannot reach production · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform 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
- Decoys deployed with alerts routed nowhere, so interaction is recorded but never seen
- Decoy shares credentials or network paths with production, turning it into an entry point
- Vulnerability scanners trip decoys constantly, so alerts are muted and real interaction is missed
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-25 Thin Nodes. Employ minimal functionality and information storage on the following system components: [organization-defined] · SC-27 Platform-independent Applications. Include within organizational systems the following platform independent applications: [organization-defined]