- Name the designated locations and reconcile deployment against the asset inventory; the unprotected server nobody remembers is the classic gap.
- Modern endpoint detection and response tooling carries this requirement's intent further than signature antivirus; either way, central visibility of agent health matters as much as installation.
3.14.2OFFICIAL STATEMENT BELOWBASIC REQUIREMENTPENDING NIST SME REVIEW
3.14.2 — Malicious code protection
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)
Provide protection from malicious code at designated locations within organizational systems.
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
Malicious code protection at designated locations — endpoints, servers, email and web gateways — chosen deliberately rather than wherever the installer happened to run. The requirement asks where protection lives, and expects the answer to be a decision.
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
- Deployment coverage reports reconciled against the asset inventory
- The documented designation of protection locations
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 |