Skip to main content

PES-06: Physical Access Authorizations

PES 7 — High Protect

Physical access control mechanisms exist to maintain a current list of personnel with authorized access to organizational facilities (except for those areas within the facility officially designated as publicly accessible).

Renumbered: Formerly PES-02 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, PES-06 was Visitor Control. That control is now PES-14.

Control Question: Does the organization maintain a current list of personnel with authorized access to organizational facilities (except for those areas within the facility officially designated as publicly accessible)?

General (41)
Framework Mapping Values
AICPA Privacy Management Framework (PMF) S7.2-POF1 S7.2-POF3
AICPA TSC 2017:2022 (used for SOC 2) (source) CC6.4 CC6.4-POF1 CC6.4-POF2
COBIT 2019 DSS05.05
GovRAMP PE-02
GovRAMP Low PE-02
GovRAMP Low+ PE-02
GovRAMP Moderate PE-02
GovRAMP High PE-02
ISO 27002 2022 5.15 5.18 7.1
ISO 27017 2015 9.1.1 11.1.1
ISO 27018 2025 5.15 5.18 7.1
MPA Content Security Program 5.3.1 PS-1.1 PS-1.2
NAIC Insurance Data Security Model Law (MDL-668) 4.D(2)(c)
NIST 800-53 R4 PE-2
NIST 800-53 R5.2 PE-02
NIST 800-53B R5 (low) (source) PE-02
NIST 800-53B R5 (moderate) (source) PE-02
NIST 800-53B R5 (high) (source) PE-02
NIST SP 800-66 R2 164.310(a)
NIST 800-82 R3 PE-02
NIST 800-82 R3 LOW OT Overlay PE-02
NIST 800-82 R3 MODERATE OT Overlay PE-02
NIST 800-82 R3 HIGH OT Overlay PE-02
NIST 800-161 R1 PE-2
NIST 800-161 R1 C-SCRM Baseline PE-2
NIST 800-161 R1 Flow Down PE-2
NIST 800-161 R1 Level 2 PE-2
NIST 800-161 R1 Level 3 PE-2
NIST 800-171 R2 (source) 3.10.1
NIST 800-171 R3 (source) 03.04.05 03.08.01 03.08.02 03.10.01.a 03.10.01.b 03.10.01.c 03.10.01.d 03.10.07.a 03.10.07.a.01
NIST 800-171A (source) 3.10.1[a] 3.10.1[b] 3.10.1[c] 3.10.1[d]
NIST 800-171A R3 (source) A.03.04.05[02] A.03.08.01[01] A.03.08.01[02] A.03.08.02 A.03.10.01.ODP[01] A.03.10.01.a[01] A.03.10.01.a[02] A.03.10.01.a[03] A.03.10.01.b A.03.10.01.c A.03.10.01.d A.03.10.07.a.01
NIST CSF 2.0 (source) PR.AA PR.AA-06
PCI DSS 4.0.1 (source) 8.3.11 9.1 9.2 9.2.1 9.3 9.3.1
PCI DSS 4.0.1 SAQ A-EP (source) 8.3.11 9.2.1
PCI DSS 4.0.1 SAQ C (source) 9.2.1
PCI DSS 4.0.1 SAQ C-VT (source) 9.2.1
PCI DSS 4.0.1 SAQ D Merchant (source) 8.3.11 9.2.1 9.3.1
PCI DSS 4.0.1 SAQ D Service Provider (source) 8.3.11 9.2.1 9.3.1
SCF DPMP 2026 7.3
SWIFT CSF 2025 3.1
US (21)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 PE-2 PE-2.a PE-2.b PE-2.c PE-2-IS.1 PE-2-IS.2 PE-3-IS.3
USA Federal C2M2 2.1 ACCESS-3b ACCESS-3d ACCESS-3f ACCESS-3g ACCESS-3i
USA Federal CMMC 2.0 Level 1 PE.L1-B.1.VIII
USA Federal CMMC 2.0 Level 1 AOs PE.L1-B.1.VIII[a] PE.L1-B.1.VIII[b] PE.L1-B.1.VIII[c] PE.L1-B.1.VIII[d]
USA Federal CMMC 2.0 Level 2 PEL2.-3.10.1
USA Federal FAR 52.204-21 52.204-21(b)(1)(viii)
USA Federal CJIS Security Policy 6.0 PE-2
USA Federal FFIEC ITEH 2016 II.C.7.b
USA Federal FedRAMP R5 (low) PE-02
USA Federal FedRAMP R5 (moderate) PE-02
USA Federal FedRAMP R5 (high) PE-02
USA Federal FedRAMP R5 (LI-SaaS) PE-02
USA Federal IRS 1075 2021 2.B.3.2 2.B.3.2-1 2.B.3.2-2 2.B.3.2-3 2.B.3.2-4 2.B.3.2-5 PE-2
USA Federal 33 CFR Part 101 Subpart F 101.650(i)(1)
USA Federal HIPAA Security Rule NIST SP 800-66 R2 § 164.310(a)(2)(i) § 164.310(a)(2)(iii)
USA Federal HIPAA Administrative Simplification 2013 § 164.310(a)(2)(i) § 164.310(a)(2)(iii)
USA Federal NERC CIP 2024 CIP-004-7 4.1.2 CIP-004-7 4.2 CIP-004-7 6.1.2
USA California CCPA 2025 7123(c)(3)(D)
USA Texas DIR SCSC 2.2 2025 PE-02
USA Texas TX-RAMP Level 1 PE-02
USA Texas TX-RAMP Level 2 PE-02
EMEA (12)
Framework Mapping Values
EMEA Germany C5 2026 PS-04.01B PS-04.01B.1 PS-04.01B.2
EMEA Spain CCN-STIC 825 op.acc.2 op.acc.4 op.acc.5 mp.if.1
EMEA EU DORA RTS 2024 Article 18.2(a) Article 21.1(g)(i) Article 21.1(g)(iv)
EMEA EU EBA GL/2019/04 3.4.3.34
EMEA EU NIS2 Annex 2024 13.3.1
EMEA UK DEFSTAN 05-138 2024 1500
EMEA UK DEFSTAN 05-138 - L1 2024 1500
EMEA UK DEFSTAN 05-138 - L2 2024 1500
EMEA UK DEFSTAN 05-138 - L3 2024 1500
EMEA LUX CCSF 20/750 2020 3.4.3-34
EMEA Saudi Arabia OTCC-1 2022 2-13-1-1
EMEA Saudi Arabia SACS-002 2022 VII.B.TPC-86
APAC (5)
Framework Mapping Values
APAC Japan ISMAP 11.1.2.3 11.1.2.12
APAC New Zealand HISF MLHSP 2023 HHSP04 HML04
APAC New Zealand HISF Suppliers 2023 HSUP04
APAC New Zealand NZISM 3.9 8.1.11.C.01 8.1.11.C.02
APAC Singapore MAS TRM 2021 8.5.6(a)
Americas (2)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.04.05 03.08.01 03.08.02 03.10.01.A 03.10.01.B 03.10.01.C 03.10.01.D 03.10.07.A 03.10.07.A.01
Americas Canada OSFI Self-Assessment Guidance 3.2.10

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

Physical & Environmental Security (PES) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with PES domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Physical security-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Physical security controls are primarily administrative in nature (e.g., policies & standards), focusing on protecting High Value Assets (HVAs). ▪ IT and/or cybersecurity personnel implement appropriate physical security practices to protect the confidentiality, integrity, availability and safety of the organization's technology assets and data.

Level 2 — Planned & Tracked

Physical & Environmental Security (PES) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with PES domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with PES domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with PES domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Physical security / facilities management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Physical security / facilities management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Physical security controls and technologies primarily focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed. ▪ The Human Resources (HR) department maintains a current list of personnel with authorized access to organizational facilities and facilitates the implementation of physical access management controls.

Level 3 — Well Defined

Physical & Environmental Security (PES) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with PES domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with PES domain capabilities are well-documented and kept current by process owners. ▪ A facilities management team, or similar function, is appropriately staffed and supported to implement and maintain NET domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of physical and environmental security operations (e.g., facility management solution, visitor log management automation and proximity badge access). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with PES domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational physical security capability exists to maintain a current list of personnel with authorized access to organizational facilities (except for those areas within the facility officially designated as publicly accessible).

Level 4 — Quantitatively Controlled

Physical & Environmental Security (PES) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. PES-06_A01 authorized individuals allowed physical access are identified.
  2. PES-06_A02 physical access to operating environments is limited to authorized individuals.
  3. PES-06_A03 physical access to organizational systems is limited to authorized individuals.
  4. PES-06_A04 physical access to equipment is limited to authorized individuals.
  5. PES-06_A05 the frequency at which to review the access list detailing authorized facility access by individuals is defined.
  6. PES-06_A06 a list of individuals with authorized access to the facility where the system resides is approved.
  7. PES-06_A07 a list of individuals with authorized access to the facility where the system resides is maintained.
  8. PES-06_A08 authorization credentials are issued for facility access.
  9. PES-06_A09 the facility access list is reviewed per an organization-defined frequency.
  10. PES-06_A10 individuals from the facility access list are removed when access is no longer required.
  11. PES-06_A11 physical access restrictions associated with changes to the system are approved.
  12. PES-06_A12 a list of individuals with authorized access to the facility where the system resides is developed.
  13. PES-06_A13 physical access authorizations are enforced at entry and exit points to the facility where the system resides by verifying individual physical access authorizations before granting access.
  14. PES-06_A14 the facility access list is reviewed <A.03.10.01.ODP[01]: frequency>.

Evidence Requirements

E-HRS-28 Authorized Personnel Access List

Documented evidence of an authorized personnel access list.

Human Resources
E-PES-03 Defined Physical Security Roles

Documented evidence of defined physical access control-specific roles that limit physical access to rooms and/or facilities.

Physical Security
E-PES-10 Physical Access Authorizations

Documented evidence of physical access authorization activities (e.g., list reviews, termination changes, etc.).

Physical Security

Technology Recommendations

Micro/Small

  • Lock server room/data closet, limit key holders

Small

  • Physical access controls to IT equipment locations
  • Visitor escort policy

Medium

  • Formal physical access control program
  • Card access for sensitive areas
  • Visitor management

Large

  • Enterprise physical access management
  • Multi-factor physical access for sensitive zones
  • Mantrap / tailgating controls

Enterprise

  • Enterprise physical access platform (e.g., Lenel S2, Genetec)
  • Multi-factor physical auth
  • Mantrap
  • Anti-tailgating controls

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.