SC-26 Decoys
Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks.
Source: NIST SP 800-53 Rev 5, SC-26. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-53 Rev 5 in the compliance library.
Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- System audit records · Policy repository / GRC workspace
- Test of Mechanisms supporting and/or implementing decoys · Document repository
governing documentDocuments that govern the control
- System and communications protection policy · Policy repository / GRC workspace
- Procedures addressing the use of decoys · Policy repository / GRC workspace
- System design documentation · Document repository
- System configuration settings and associated documentation · Policy repository / GRC workspace
- System security plan · Policy repository / GRC workspace
First move
Common gaps auditors find
- No decoy components are included to detect, deflect and analyze attacks
- Decoy alerts are not monitored or analyzed
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 sheet