NIST SP 800-53 Rev. 5 · SI-8

Spam Protection

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

Explanation

What it asks for. Spam protection mechanisms must be employed at system entry and exit points to detect and act on unsolicited messages, and they must be updated when new releases are available.

In practice. Doing this well means a managed email security service or gateway with spam, phishing and malicious attachment filtering, sender authentication checks using SPF, DKIM and DMARC, and automatic updates of detection rules. Auditors look for configuration evidence, DMARC policies and filtering statistics. CIS Control 9 covers email protections. Users should have an easy way to report suspicious messages, which feeds back into tuning.

Common gaps. DMARC is frequently left at a monitoring-only policy indefinitely. Filtering exceptions for specific senders or domains are added and never reviewed. Outbound filtering is often missing, so a compromised mailbox can be used to spam partners.

The official text
a. Employ spam protection mechanisms at system entry and exit points to detect and act on unsolicited messages; and b. Update spam protection mechanisms when new releases are available in accordance with organizational configuration management policy and procedures. Discussion: System entry and exit points include firewalls, remote-access servers, electronic mail servers, web servers, proxy servers, workstations, notebook computers, and mobile devices. Spam can be transported by different means, including email, email attachments, and web accesses. Spam protection mechanisms include signature definitions.

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: the latest 12 of 30.