Security requirement
- a.Develop, approve, and maintain a list of individuals with authorized access to the facility where the system resides.
- b.Issue authorization credentials for facility access.
- c.Review the facility access list [Organization-defined: frequency].
- d.Remove individuals from the facility access list when access is no longer required.
Discussion
A facility can include one or more physical locations containing systems or system components that process, store, or transmit CUI. Physical access authorizations apply to employees and visitors. Individuals with permanent physical access authorization credentials are not considered visitors. Authorization credentials include identification badges, identification cards, and smart cards. Organizations determine the strength of the authorization credentials consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines. Physical access authorizations may not be necessary to access certain areas within facilities that are designated as publicly accessible.
Tailoring decisions required
Resolve these values through the governing organization’s approved tailoring and risk-management process before declaring the requirement implemented.
Implementation perspective
Treat Physical Access Authorizations as a CUI protection outcome that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to physical access, facility protection, visitor accountability, and protection of system components that handle CUI.
- Confirm the requirement is in scope for the CUI system components, services, users, and external connections being assessed.
- Resolve every organization-defined parameter through an approved governance and tailoring process.
- Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
- Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
- Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.
Questions to ask
- Which CUI assets, data flows, users, and services are protected by this requirement?
- Which portions are implemented locally, inherited, shared, or not applicable, and what evidence supports that determination?
- Do the system security plan, deployed configuration, operating process, and assessment evidence tell the same story?
- What change, incident, or threshold should trigger reassessment?
Evidence and validation
- badge and visitor logs
- physical access reviews
- facility diagrams and sensor records
- environmental and power test results
Common failure patterns
- logical controls undermined by physical access
- tailgating or visitor exceptions normalized
- critical infrastructure omitted from access reviews
- environmental alarms disconnected from response
Assessment objectives and methods
Assessment objectives (6)
- a.
a list of individuals with authorized access to the facility where the system resides is developed.
- a.
a list of individuals with authorized access to the facility where the system resides is approved.
- a.
a list of individuals with authorized access to the facility where the system resides is maintained.
- c.
the facility access list is reviewed [Organization-defined: frequency].
- d.
individuals from the facility access list are removed when access is no longer required.
- b.
authorization credentials for facility access are issued.
Examine
- physical protection policy and procedures
- procedures for physical access authorizations
- authorized personnel access list
- physical access list reviews
- physical access termination records
- authorization credentials
- system security plan
- other relevant documents or records
Interview
- personnel with physical access authorization responsibilities
- personnel with physical access to the facility where the system resides
- personnel with information security responsibilities
Test
- processes for physical access authorizations
- mechanisms for supporting or implementing physical access authorizations
Source NIST SP 800-53 controls
These controls are referenced by the official SP 800-171 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.
Authoritative sources
- NIST SP 800-171 Revision 3 official publication ↗
- NIST SP 800-171A Revision 3 official publication ↗
- NIST OSCAL Content release used for this import ↗
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. The official publications, the responsible federal agency, and the governing contract or agreement determine applicability, tailoring, assessment depth, and required implementation.