NIST SP 800-53 Rev. 5 · SC-26

Decoys

US National Institute of Standards and Technology (NIST) · cited in 2 of our lessons

Explanation

What it asks for. Systems must include components specifically designed to be targets of malicious attacks, in order to detect, deflect and analyse those attacks.

In practice. This means honeypots, honey tokens, decoy credentials or deception platforms placed where attackers are likely to look. Because legitimate users have no reason to touch them, any interaction is a high-confidence signal. Evidence includes a description of deployed decoys, their placement and alert handling records. Decoys should be realistic enough to attract attention and placed in high-value network segments.

Common gaps. Decoys are sometimes deployed and then not monitored, so alerts go nowhere. Poorly isolated honeypots can create new risk if attackers use them as a foothold. Decoys that look obviously fake are easily avoided by skilled attackers.

The official text
Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks. Discussion: Decoys (i.e., honeypots, honeynets, or deception nets) are established to attract adversaries and deflect attacks away from the operational systems that support organizational mission and business functions. Use of decoys requires some supporting isolation measures to ensure that any deflected malicious code does not infect organizational systems. Depending on the specific usage of the decoy, consultation with the Office of the General Counsel before deployment may be needed.

From NIST SP 800-53 Rev. 5, a work of the US government in the public domain.

Lessons that cite it

Real incidents where this item mattered.