| name | PE-3_physical-access-control |
| description | Enforce physical access authorizations at [organization-defined] by: Verifying individual access authorizations before granting access to the facility |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","pe-3","pe"] |
| tech_stack | ["any"] |
| cwe_ids | [] |
| chains_with | ["AT-3","AU-2","AU-6","AU-9","AU-13","CP-10","IA-3","IA-8","MA-5","MP-2"] |
| prerequisites | [] |
| severity_boost | {"AT-3":"Chain with AT-3 for comprehensive security coverage","AU-2":"Chain with AU-2 for comprehensive security coverage","AU-6":"Chain with AU-6 for comprehensive security coverage"} |
PE-3 Physical Access Control
High-Level Description
Family: Physical and Environmental Protection (PE)
Framework: NIST SP 800-53 Rev 5
Physical access control applies to employees and visitors. Individuals with permanent physical access authorizations are not considered visitors. Physical access controls for publicly accessible areas may include physical access control logs/records, guards, or physical access devices and barriers to prevent movement from publicly accessible areas to non-public areas. Organizations determine the types of guards needed, including professional security staff, system users, or administrative staff. Physical access devices include keys, locks, combinations, biometric readers, and card readers. Physical access control systems comply with applicable laws, executive orders, directives, policies, regulations, standards, and guidelines. Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural, automated, or some combination thereof. Physical access points can include facility access points, interior access points to systems that require supplemental access controls, or both. Components of systems may be in areas designated as publicly accessible with organizations controlling access to the components.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for PE-3 implementation details. Verify the organization has documented how this control is satisfied.
Step 2: Validate Implementation
# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly
# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null
Step 3: Test Operating Effectiveness
Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.
Tools
| Tool | Purpose | Usage |
|---|
| Manual Review | Documentation and interview-based | N/A |
Remediation Guide