3.10.2Protect and monitor the facility in Rev. 3

Reworded: 03.10.02 Monitoring Physical Access. Gains organization-defined parameters.

Status as of 2026-09-08

Rev. 2 is what a contract requires today. DFARS 252.204-7012 and the CMMC rule at 32 CFR 170 point at NIST SP 800-171 Rev. 2, and a standing DoD class deviation keeps it there. NIST has published Rev. 3, but publishing a revision does not change an obligation. A move to Rev. 3 would arrive through the Department's reform process and formal rulemaking, a change to that deviation or an amendment to the rule, not through publication. The Department has published its organization-defined parameter values for Rev. 3 in preparation; that is groundwork, not adoption.

Side by side

Rev. 2 · in force 3.10.2 Monitor Facility

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

Assessment objectives · 800-171A

[a] the physical facility where organizational systems reside is protected
[b] the support infrastructure for organizational systems is protected
[c] the physical facility where organizational systems reside is monitored
[d] the support infrastructure for organizational systems is monitored

Rev. 3 · not adopted 03.10.02 Monitoring Physical Access

a. Monitor physical access to the facility where the system resides to detect and respond to physical security incidents.

b. Review physical access logs [Assignment: organization-defined frequency] and upon occurrence of [Assignment: organization-defined events or potential indications of events].

Determination statements · 800-171A Rev. 3

03.10.02.a[01] physical access to the facility where the system resides is monitored to detect physical security incidents.
03.10.02.a[02] physical security incidents are responded to.
03.10.02.b[01] physical access logs are reviewed <A.03.10.02.ODP[01]: frequency>.
03.10.02.b[02] physical access logs are reviewed upon occurrence of <A.03.10.02.ODP[02]: events or potential indicators of events>.

Organization-defined parameters

A.03.10.02.ODP[01] the frequency at which to review physical access logs is defined.
A.03.10.02.ODP[02] events or potential indications of events requiring physical access logs to be reviewed are defined.

Draws on Rev. 2 3.10.2.

Left: NIST SP 800-171 Rev. 2 and 800-171A, verbatim. Right: NIST SP 800-171 Rev. 3 and 800-171A Rev. 3, verbatim, with organization-defined blanks highlighted.

Word by word

The Rev. 2 requirement compared with its Rev. 3 successor. A mechanical comparison of the two verbatim texts, not an interpretation.

~~removed in Rev. 3~~ added in Rev. 3

Rev. 2 3.10.2 → Rev. 3 03.10.02 Monitoring Physical Access

~~Protect and~~ Monitor ~~the~~ physical access to the facility where the system resides to detect and ~~support infrastructure for organizational systems.~~ respond to physical security incidents. Review physical access logs [Assignment: organization-defined frequency] and upon occurrence of [Assignment: organization-defined events or potential indications of events].

4 words kept, 8 removed, 33 added. Rev. 3 statement labels omitted for the comparison.

What NIST says changed

New security requirement title
Aligned with SP 800-53, Rev 5 to provide more comprehensive detail on and foundational tasks for monitoring physical access
Added new ODP: frequency to review physical access logs
Added new ODP: events or potential indications of events to review physical access logs

NIST, SP 800-171 Rev. 2 to Rev. 3 change analysis, class “Significant change”. At adoption, Bedrock files this under “Rework”.

NIST's Rev. 3 discussion for 03.10.02

A facility can include one or more physical locations containing systems or system components that process, store, or transmit CUI. Physical access monitoring includes publicly accessible areas within organizational facilities. Examples of physical access monitoring include guards, video surveillance equipment (i.e., cameras), and sensor devices. Reviewing physical access logs can help to identify suspicious activities, anomalous events, or potential threats. The reviews can be supported by audit logging controls if the access logs are part of an automated system. Incident response capabilities include investigations of physical security incidents and responses to those incidents. Incidents include security violations or suspicious physical access activities, such as access outside of normal work hours, repeated access to areas not normally accessed, access for unusual lengths of time, and out-of-sequence access.

What this means for you now

Nothing changes in what you are assessed against until a class deviation or a published rule adopts Rev. 3. Keep meeting 3.10.2 as written in Rev. 2, and if you already choose a value for the parameters above in practice, write it down where your system security plan can find it.

Bedrock CMMC shows this same comparison against your own package, with your current status on the Rev. 2 side, so the day adoption lands the migration is a review, not a rewrite.

Back to the Rev. 2 vs Rev. 3 overview

Where this page's facts come from

Rev. 2 text and objectives: bedrock-cmmc-api@89b8e8e:migrations/004_reference_requirements.sql#Requirement.basicRequirement@rev2; bedrock-cmmc-api@89b8e8e:migrations/005_reference_objectives.sql#AssessmentObjective.description@rev2
Mapping and change class: bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/r2_r3_transition_map.json#r2_to_r3
Rev. 3 03.10.02: bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/rev3.json#requirements[]