NIST SP 800-53 Rev. 5 PE-3(6) — Facility Penetration Testing

What this control requires

Conducting penetration testing at an organization-defined frequency on the facility housing the system to identify and address physical security vulnerabilities, ensuring robust protection against unauthorized access. This control supports the Physical Security System capability within the Physical and Environmental Protection family.

In plain English

Conducting penetration testing at an organization-defined frequency on the facility housing the system to identify and address physical security vulnerabilities, ensuring robust protection against unauthorized access. 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(6)) and look for objective evidence on the latest two assessment cycles.

How to implement

Vulnerability Management

Scanners. Pair an unauthenticated scanner (Nessus / Qualys / Tenable.io) for external surface with an authenticated agent for OS/library CVEs on every host.

SLA. Document remediation SLAs by CVSS / EPSS: critical 7 days, high 30 days, medium 90 days; report monthly trend to leadership.

Containers. Scan images in CI (Trivy / Grype / Snyk Container) AND at runtime; block deploys on critical findings without exception.

Code Review Testing

Pipeline. Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

Physical Security

Inheritance. For cloud-only operations, inherit physical controls from the provider's SOC 2 / ISO 27001 report and document the inheritance in the SoA.

Operational checklist

• Access. 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.
• Review. Document the trigger, the owner and the cadence.
• Protection. Document the trigger, the owner and the cadence.
• Scope: management, organization, system, protection, review, capability, vulnerability, security.

Evidence to collect

• Vapt Scan. vapt_scan evidence

Pen-test and vulnerability scan reports substantiate attack-surface coverage. Focus: Facility Penetration Testing.

Common pitfalls

• Scans that hit only the perimeter; missing authenticated scans of OS, runtime libs and base images so most CVEs are invisible.

Related controls in NIST SP 800-53 Rev. 5

• Control CA-8(3) — Facility Penetration Testing
• Control PE-13(4) — Inspections
• Control RA-5(9) — Penetration Testing And Analyses
• Control PE-2(2) — Two Forms Of Identification
• Control CA-8(1) — Independent Penetration Testing Agent Or Team
• Control SA-11(5) — Penetration Testing

References

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

Topics: physical securityvulnerability managementcode review testing