PE.L1-b.1.ix
Manage Visitors & Physical Access [FCI Data]
Requirement
Assessment objectives
An assessor checks each lettered objective separately. The letters in brackets elsewhere on this page, such as [a] or [b,c], refer to these.
Determine if:
- avisitors are escorted;
- bvisitor activity is monitored;
- caudit logs of physical access are maintained;
- dphysical access devices are identified;
- ephysical access devices are controlled; and
- fphysical access devices are managed.
From the CMMC Level 1 Assessment Guide v2.13 · publisher approved 2026-10-31.
How to implement
Escort visitors and keep an eye on what they do, keep a log of who enters your facility, and know exactly which keys, badges and codes exist and who holds them. For a small business that can be as simple as a sign-in book, visitor badges, an employee escort, a key list checked against serial numbers, and changing codes or locks when someone leaves without returning a key. Keep the logs for the period you define, for example one year.
- 1PolicyWrite a short visitor and physical access procedure: who counts as a visitor (anyone not on the authorized list, including friends, family and vendors), escort required at all times, visitor badges, sign-in and sign-out, log retention period, and how keys, badges and codes are issued, tracked and revoked.[a][b][c][d][e][f]
- 2
- 3ProcessKeep physical access logs: a visitor sign-in book or visitor-management system (name, company, host, time in and out), plus employee entry logs from badge readers if you have them. Store paper logs in a locked cabinet and keep them for your defined retention period.[c]
- 4ProcessInventory physical access devices: every key (with serial or stamp number), badge, fob and alarm code, who it is assigned to and what it opens.[d]
- 5TechnicalControl the devices: store spare keys and unassigned badges in a locked key box; restrict who can program the badge system or change alarm codes; use restricted keyways so keys cannot be copied freely.[e]
- 6ProcessManage the devices over time: collect keys and badges at departure and check them against the inventory, disable badges the same day, change alarm codes and rekey locks when a key is lost or not returned, and review the inventory at least annually.[f]
Evidence to collect
Artifacts that show the practice is implemented and operating. Tags show which assessment objectives each one supports.
Short dated document covering escorts, badges, logs and key and badge management.
Sign-in book or visitor-management export showing visitor, host or escort, and times.
Badge reader or entry logs[c]
log · retained for your defined period
Export from the access-control system, if you have one.
Spreadsheet of keys, badges, fobs and codes with serials, holders and areas opened.
Key and badge return and revocation records[f]
record · every departure in the assessment period
Offboarding checklist entries or access-system audit log showing returns, disablement, rekeying or code changes.
How assessors check
- Examine
- Visitor and physical access procedures, visitor logs, access logs, key and badge inventory, offboarding records.
- Interview
- Reception or office staff who sign visitors in; employees who escort visitors; the person who manages keys and badges.
- Test
- Arrive as a visitor and observe the sign-in, badge and escort process; pick a key from the inventory and confirm its holder; pick a former employee and show the badge or key was returned and access revoked.
Tools and products
Named options a contractor can adopt, with an honest cost tier. The industry standard is listed even when it is expensive, alongside what is free and acceptable for a very small shop.
Essentially free and exactly what the guide's example describes; keep completed pages in a locked cabinet for the retention period.
Common iPad-based sign-in with host notifications, printed badges and searchable logs; per-location subscription.
Affordable electronic access control that records entries and lets you revoke a badge instantly.
Integrated cameras, doors and visitor management; the polished industry option, priced per device with licenses.
A lockable key box and keys that cannot be copied without authorization make the key inventory meaningful.
Editorial mentions, not endorsements. Pricing and tiers change; confirm with the vendor and check FedRAMP or GCC High availability where CUI is involved.
Common pitfalls
- Friends and family wandering the office unescorted because 'we know them'.
- Visitor badges that look the same as employee badges.
- Paper visitor logs thrown away every month, shorter than the retention period you defined.
- Former employees still holding keys, or a shared alarm code that has never changed.
Platform notes
Microsoft 365 (GCC / GCC High)
Not applicable for the physical controls; Microsoft is responsible for its data-center physical security.
Google Workspace
Not applicable for the physical controls; Google is responsible for its data-center physical security.
On-premises or MSP-managed
MSP technicians who visit on-site are visitors unless on your authorized list; sign them in. If you share a building, ask the landlord for building access logs if they cover your entrance, but keep your own suite-level log.
Related practices: PE.L1-b.1.viii, PE.L2-3.10.3, PE.L2-3.10.4, PE.L2-3.10.5
Editorial implementation guidance published November 2, 2026. It is not part of the official requirement and does not replace the assessment guide.
Crosswalk
Full crosswalkThe NIST requirements this practice is built on, what NIST made of each in the newer edition, and the SP 800-53 controls behind them, each from an official NIST or DoD table. Open any one to read it and see every CMMC practice it supports.
NIST SP 800-171 Rev 2
3.10.3SP 800-171 Rev 3
03.10.0703.10.03 withdrawn; incorporated intoSP 800-53 Rev 4
PE-3SP 800-53 Rev 5
PE-3DSPE-5SHow these were reachedHide how these were reached
- PE-3 · Physical Access Control
- D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 PE-3 → 800-53 Rev 5 PE-3
- S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.10.07 → 800-53 Rev 5 PE-3NIST: 03.10.07 also: 3.10.4, 3.10.5 incorporated into
- PE-5 · Access Control for Output Devices
- S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.10.07 → 800-53 Rev 5 PE-5NIST: 03.10.07 also: 3.10.4, 3.10.5 incorporated into
NIST SP 800-171 Rev 2
3.10.4SP 800-171 Rev 3
03.10.0703.10.04 withdrawn; incorporated intoSP 800-53 Rev 4
PE-3SP 800-53 Rev 5
PE-3DSPE-5SHow these were reachedHide how these were reached
- PE-3 · Physical Access Control
- D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 PE-3 → 800-53 Rev 5 PE-3
- S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.10.07 → 800-53 Rev 5 PE-3NIST: 03.10.07 also: 3.10.3, 3.10.5 incorporated into
- PE-5 · Access Control for Output Devices
- S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.10.07 → 800-53 Rev 5 PE-5NIST: 03.10.07 also: 3.10.3, 3.10.5 incorporated into
NIST SP 800-171 Rev 2
3.10.5SP 800-171 Rev 3
03.10.0703.10.05 withdrawn; incorporated intoSP 800-53 Rev 4
PE-3SP 800-53 Rev 5
PE-3DSPE-5SHow these were reachedHide how these were reached
- PE-3 · Physical Access Control
- D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 PE-3 → 800-53 Rev 5 PE-3
- S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.10.07 → 800-53 Rev 5 PE-3NIST: 03.10.07 also: 3.10.3, 3.10.4 incorporated into
- PE-5 · Access Control for Output Devices
- S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.10.07 → 800-53 Rev 5 PE-5NIST: 03.10.07 also: 3.10.3, 3.10.4 incorporated into
Rev 5 paths: D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison; S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL); C SP 800-172 (Feb 2021) Appendix C. NIST also names this Rev 3 requirement as the successor of other withdrawn requirements: open “How these were reached” under the Rev 5 controls for which, in NIST's words.
Where each link comes from (15 links from 5 official documents)
CMMC Assessment Guide Level 1 v2.13 DoD CIO
- PE.L1-b.1.ix → 3.10.3“Key reference”p.37 PE.L1-b.1.ix KEY REFERENCES
- PE.L1-b.1.ix → 3.10.4“Key reference”p.37 PE.L1-b.1.ix KEY REFERENCES
- PE.L1-b.1.ix → 3.10.5“Key reference”p.37 PE.L1-b.1.ix KEY REFERENCES
NIST SP 800-171 Rev 3 (OSCAL) NIST
- 03.10.03 → 03.10.07“Incorporated into”control 03.10.03 link rel=incorporated_into
- 03.10.07 → PE-3“Source control”control 03.10.07 link rel=reference (PE-03)
- 03.10.07 → PE-5“Source control”control 03.10.07 link rel=reference (PE-05)
- 03.10.04 → 03.10.07“Incorporated into”control 03.10.04 link rel=incorporated_into
- 03.10.05 → 03.10.07“Incorporated into”control 03.10.05 link rel=incorporated_into
Further discussion
Practice guide notes
Implementation guidance
Editorial examples to help you plan. Adapt them to your environment; the official requirement and objectives remain authoritative.
In plain language
Escort visitors, record physical access, and manage the keys, badges, and other devices that grant access.
Implementation example
Example from the source assessment guide (not a mandatory implementation): Coming back from a meeting, you see the friend of a coworker walking down the hallway near your office where FCI is stored. You know this person well and trust them, but are not sure why they are in the building. You stop to talk, and the person explains that they are meeting a coworker for lunch, but cannot remember where the lunchroom is. You walk the person back to the reception area to get a visitor badge and wait until someone can escort them to the lunchroom [a]. You report this incident, and the company decides to install a badge reader at the main door so visitors cannot enter without an escort [a]. Example 2 You and your coworkers like to have friends and family join you for lunch at the office on Fridays. Your small company has just signed a contract with the DoD in which your company will receive FCI and you now need to document who enters and leaves your facility. You work with the reception staff to ensure that all non-employees sign in at the reception area and sign out when they leave [c]. You retain those paper sign-in sheets in a locked filing cabinet for one year. Employees receive badges or key cards that enable tracking and logging access to company facilities. Example 3 You are a facility manager. A team member retired today and returns their company keys to you. The project on which they were working requires access to areas that contain equipment with FCI . You receive the keys, check your electronic records against the serial numbers on the keys to ensure all have been returned, and mark each key returned [f].
Evidence examples
Examples suggested by the source guide (not an exhaustive or mandatory checklist): Physical and environmental protection policy; procedures addressing physical access control; system security plan; physical access control logs or records; inventory records of physical access control devices; system entry and exit points; records of key and lock combination changes; storage locations for physical access control devices; physical access control devices; list of security safeguards controlling access to designated publicly accessible areas within facility; other relevant documents or records
Common mistakes
Keeping a visitor book without controlling visitor activity or recovering keys and badges.
Track this in a workspace
The compliance workspace tracks each objective, its evidence and the tasks to close gaps. It is open to invited contractors while in pilot: request access below.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Source: DoD CIO · https://dodcio.defense.gov/CMMC/