NIST SP 800-53 Rev. 5 PE-3(7) — Physical Barriers

What this control requires

Implementing organization-defined physical barriers to restrict unauthorized access to facilities containing information systems. These barriers, such as walls, fences, or locked enclosures, protect against physical intrusions and environmental threats, ensuring only authorized personnel access sensitive areas. This control supports the Physical Security System capability within the Physical and Environmental Protection family.

In plain English

Implementing organization-defined physical barriers to restrict unauthorized access to facilities containing information systems. In practice, this means you can prove you access management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Physical and Environmental Protection, the assessor will trace your implementation back to the catalogue reference (Control PE-3(7)) and look for objective evidence on the latest two assessment cycles.

How to implement

1. Write a short policy stating intent, scope and named owner.
2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
4. Review on a documented cadence and capture the review in the risk register or compliance tracker.

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• Restrict. Document the trigger, the owner and the cadence.
• Information. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Physical. Document the trigger, the owner and the cadence.
• Scope: management, information, organization, system, only, personnel, controls, protection.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Physical Barriers.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• NIST SP 800-171 Rev. 3 3.15.2 — System Security Plan

Related controls in NIST SP 800-53 Rev. 5

• Control SC-7(14) — Protect Against Unauthorized Physical Connections
• Control PE-4 — Access Control For Transmission
• Control PS-4 — Personnel Termination
• Control SC-42(1) — Reporting To Authorized Individuals Or Roles
• Control PE-2(2) — Two Forms Of Identification
• Control PE-15(1) — Automation Support

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control PE-3(7)

Topics: identity accessidentity managementaccess reviewprivileged accessenvironmental controls