CMMC physical security requirements are the six controls in the Physical Protection family of NIST SP 800-171 Rev 2, numbered 3.10.1 to 3.10.6. In plain terms: decide who is allowed in, keep everyone else away from the spaces where your systems and Controlled Unclassified Information (CUI) sit, escort and log visitors, keep track of keys and badges, and set rules for work done away from the office.
None of it needs a guard desk or a big budget. A five-person shop can meet all six with locks, a sign-in sheet, a key list and a few written paragraphs. The catch is that this family is the least forgiving in the scoring rules. Five of the six can never be deferred to a plan of action and milestones (POA&M), so "we are working on it" is not an available answer. This is explanatory content, not legal advice, so check your own contract for anything stricter.
The six CMMC physical security requirements
The requirement text comes from NIST SP 800-171 Rev 2, the objectives from NIST SP 800-171A, and the points from the DoD Assessment Methodology, version 1.2.1.
| Requirement | Plain English | Objectives | SPRS points | Also in Level 1? |
|---|---|---|---|---|
| 3.10.1 | Limit physical access to systems, equipment and their operating environments to authorized people | 4 | 5 | Yes |
| 3.10.2 | Protect and monitor the facility and its support infrastructure | 4 | 5 | No |
| 3.10.3 | Escort visitors and monitor what they do | 2 | 1 | Yes |
| 3.10.4 | Maintain audit logs of physical access | 1 | 1 | Yes |
| 3.10.5 | Control and manage physical access devices | 3 | 1 | Yes |
| 3.10.6 | Enforce safeguarding measures for CUI at alternate work sites | 2 | 1 | No |
That is 16 assessment objectives and 14 points. The three self-assessed paths use the family like this:
- CMMC Level 1 (Self). FAR 52.204-21 paragraphs (b)(1)(viii) and (ix) contain four of the six, applied to Federal Contract Information: limit physical access, escort visitors, keep access logs, and manage access devices. They are on the free Level 1 checklist.
- CMMC Level 2 (Self). All six apply wherever CUI is processed, stored or transmitted.
- SPRS score. The same six, scored at 14 points. The two worth 5 points each are covered in our post on the 5-point controls.
Why physical security cannot wait on a POA&M
32 CFR 170.21 sets the rules for what may be deferred, and it is hard on this family.
- At Level 1, a POA&M is not permitted at any time. All four physical safeguards must be met.
- At Level 2, nothing worth more than 1 point can go on a POA&M (with one encryption exception that does not apply here). That rules out 3.10.1 and 3.10.2.
- The rule then names six requirements that can never be on a POA&M regardless of points. Three of them are 3.10.3 Escort Visitors, 3.10.4 Physical Access Logs and 3.10.5 Manage Physical Access.
That leaves 3.10.6 as the only physical protection requirement you may defer for a Conditional Level 2 (Self) status. Everything else has to be in place and working on the day you score yourself. Our POA&M guide covers the 80 percent floor and the 180-day closeout that apply to anything you do defer.
What each requirement looks like in a small office
3.10.1: the doors and the authorized list
The first objective is not about locks. It asks whether the authorized individuals allowed physical access are identified. So start with a list: every person who may be in the space unescorted. Include the people who are easy to forget, such as the cleaning crew, the landlord's maintenance staff and your IT provider's technician.
NIST's discussion says the requirement applies only to areas that have not been designated as publicly accessible. A front lobby can stay open. The office, shop floor or room where the computers and paper live cannot. NIST's examples of equipment include printers, copiers, scanners, monitors, external drives and networking gear, so a shared printer in an open hallway that prints controlled drawings is in play.
3.10.2: the server closet and the wiring
This one has two verbs, protect and monitor, and two targets, the facility and its support infrastructure. NIST's examples of protecting support infrastructure are practical: locked wiring closets, disconnected or locked spare network jacks, and cabling in conduit or trays. If your "server room" is a shelf in the supply closet, the closet needs a lock and a short list of who holds the key.
For monitoring, NIST names guards, sensor devices and video cameras as examples. It does not mandate any one of them. In a small office, an alarm system with a separate code for each person is a reasonable way to know who came in after hours. Whatever you use, write down what does the monitoring and who looks at it.
3.10.3: visitors
NIST defines visitors by exclusion: people with permanent physical access authorization credentials are not visitors. Everyone else is. That covers customers, delivery drivers who come past the lobby, the copier repair technician, inspectors and family members. Two things must be true: they are escorted, and their activity is monitored. A simple rule works: no visitor is left alone in a space where systems or CUI are present, and screens and paper are covered or cleared before they walk through.
3.10.4: the access log
NIST gives you flexibility here. Its discussion says audit logs can be procedural, such as a written log of individuals accessing the facility, automated, or a mix. A paper sign-in sheet is acceptable if it is actually used. Useful columns:
- Date, name and company
- Who they came to see and who escorted them
- Time in and time out
If you have a badge reader or an alarm panel that records entries, its export counts toward the same requirement. NIST SP 800-171 Rev 2 does not set a retention period for these logs. Pick one, write it in your policy, and keep to it.
3.10.5: keys, codes and badges
NIST's list of physical access devices is short: keys, locks, combinations and card readers. The three objectives ask whether they are identified, controlled and managed. In practice that means a key and badge inventory showing who holds what, collection on an employee's last day, and a change of combinations and alarm codes when someone who knew them leaves. A master key held by a landlord or cleaning company belongs on the inventory too.
3.10.6: work away from the office
The last requirement asks you to define safeguards for alternate work sites and then enforce them. NIST says alternate work sites may include employees' homes. Our post on remote work and CUI covers what to write and how to get it signed.
Shrink the space before you harden it
Physical controls follow your assessment scope. If CUI lives in one locked room and on the systems inside it, that room is where the authorized list, the escort rule and the log matter most. If CUI is on every desk, every desk is in play. Deciding where controlled information is allowed to be is often cheaper than securing a whole building, and it is the idea behind a CUI enclave. Shared buildings raise the same question from the other side: find out who else holds a key to your suite before you write that access is limited.
Evidence to keep
NIST SP 800-171A lists what may be examined for this family. For a small office, the working set is:
- A physical protection policy, even one page, and the matching paragraphs in your system security plan (SSP)
- The authorized personnel access list, with a date showing when it was last reviewed
- Visitor logs for the retention period you chose
- The key, badge and code inventory
- Records of key returns, lock changes and combination changes when people leave
- Alarm, badge or camera records if you rely on them for monitoring
An assessor may also interview the person responsible and walk the space. Our post on 800-171A assessment objectives explains how each objective is judged.
What to do this week
- Walk the office and mark which areas are public and which are not. Write it down in two sentences.
- List everyone allowed in the non-public areas unescorted, including outside parties with keys.
- Put a sign-in sheet at the entrance and tell staff that visitors are escorted, starting today.
- Build the key, badge and code inventory. Change any code that a former employee knew.
- Lock the closet or cabinet that holds the server, firewall and network switch.
- Decide how the office is monitored after hours and who reviews it.
- Write the one-page policy and the SSP paragraphs, then file the first week of logs as evidence.
CMMC Map, CMMC compliance software for small defense contractors, walks you through all six physical protection requirements in the free assessment and flags the ones that cannot be deferred. You can test the effect on your number with the free SPRS calculator.
See where your office stands on 3.10
The free CMMC Map assessment walks through the six physical protection requirements and the other 104, and shows which gaps block Level 1 (Self) and Level 2 (Self).
Start free in CMMC Map