Independent DIB implementation resource — not affiliated with or endorsed by the U.S. Department of WarView the official DoW campaign ↗
3.10.2OFFICIAL STATEMENT BELOWBASIC REQUIREMENTPENDING NIST SME REVIEW

3.10.2Facility protection and monitoring

3.10 Physical Protection · 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)

Protect and monitor the physical facility and support infrastructure for organizational systems.

NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal SystemsNIST SP 800-171A — Assessing Security Requirements for CUI
Independent interpretation

What this requirement is after

The facility itself and what keeps it running — power, cooling, cabling, telecom — are protected and watched. Monitoring means something or someone notices intrusion or tampering: alarms, cameras, guards, or their practical small-facility equivalents.

Across revisions

Carried into Rev. 3 as 03.10.02 Monitoring Physical Access, with physical-access incident review made part of the requirement's scope.

Mapped practices

Brilliant at the Basics practices that support this requirement

Doing the work

Implementation considerations and evidence

Implementation considerationsIndependent guidance — tailor to your environment
  • Include support infrastructure explicitly: telecom rooms, power and cooling for server spaces, exposed cable runs between areas.
  • Choose monitoring proportionate to the facility — an alarmed server-room door can be worth more than cameras everywhere.
  • Review the monitoring output on some cadence; an unwatched camera is decoration, and assessors ask who looks at it.
What operating evidence looks likeRecords worth retaining, not a submission checklist
  • Coverage records for alarms and cameras against the areas that matter
  • Maintenance and test records for the monitoring itself
  • Sampled review of monitoring events and the retention applied to footage or alarm logs
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 sourcesNIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems · NIST SP 800-171A — Assessing Security Requirements for CUI
Review statusPending NIST SME review
Content version1.0
Updated