- Verify real-time protection is on and unexcluded where it matters — sweeping exclusion lists added for performance are the common self-inflicted gap.
- Schedule periodic scans and retain their results; an engine that never reports is indistinguishable from one that never ran.
3.14.5OFFICIAL STATEMENT BELOWDERIVED REQUIREMENTPENDING NIST SME REVIEW
3.14.5 — Periodic and real-time scanning
3.14 System and Information Integrity · NIST SP 800-171 Rev. 2 · The heading label is this site's navigational shorthand; the official language is the statement below.
Official requirement statement (verbatim)
Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.
NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems ↗NIST SP 800-171A — Assessing Security Requirements for CUI ↗Independent interpretation
What this requirement is after
Periodic scans of systems, plus real-time scanning of files arriving from outside as they are downloaded, opened, or executed. The pairing matters: real-time catches the inbound path, and periodic sweeps catch what got in anyway.
Across revisions
Withdrawn as a standalone in Rev. 3 (03.14.05); scanning behavior folds into the consolidated Malicious Code Protection requirement, 03.14.02.
Mapped practices
Brilliant at the Basics practices that support this requirement
No practice maps to this requirement — deliberately.
The campaign’s twenty practices are a priority list, not a control catalog, and none of them works this requirement’s substance directly. It still applies to you if it is in your contract’s scope: address it through your own implementation and the related artifacts below, and treat the absence of a mapping here as honesty, not permission to skip it.
Doing the work
Implementation considerations and evidence
- Scan policy exports: real-time settings, exclusions, schedules
- Periodic scan result reports for a sampled period
Artifacts
Templates and worksheets with a mapped relationship
No artifact in the library names this requirement yet. The library index groups everything by category and practice.
The other revision
Where this lands in Rev. 3
Provenance
Sources and review status
| Primary sources | NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems · NIST SP 800-171A — Assessing Security Requirements for CUI |
|---|---|
| Review status | Pending NIST SME review |
| Content version | 1.0 |
| Updated |