Skip to main content

PES-08: Physical Access Control

PES 10 — Critical Protect

Physical access control mechanisms exist to enforce physical access authorizations for all physical access points (including designated entry/exit points) to facilities (excluding those areas within the facility officially designated as publicly accessible).

Renumbered: Formerly PES-03 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, PES-08 was Fire Protection. That control is now PES-26.

Control Question: Does the organization enforce physical access authorizations for all physical access points (including designated entry/exit points) to facilities (excluding those areas within the facility officially designated as publicly accessible)?

General (43)
Framework Mapping Values
AICPA Privacy Management Framework (PMF) S7.2 S7.2-POF4 S7.2-POF5
AICPA TSC 2017:2022 (used for SOC 2) (source) CC6.4 CC6.4-POF1 CC6.4-POF2
COBIT 2019 DSS05.05
CSA CCM 4.1.0 DCS-08
CSA IoT SCF 2 PHY-01
GovRAMP PE-03
GovRAMP Low PE-03
GovRAMP Low+ PE-03
GovRAMP Moderate PE-03
GovRAMP High PE-03
ISO 27002 2022 5.15 5.18 7.1 7.4
ISO 27017 2015 9.1.1 11.1.1
ISO 27018 2025 5.15 5.18 7.1 7.4
MPA Content Security Program 5.3.1 OP-1.0 PS-1.0 PS-1.2
NIST 800-53 R4 PE-3 PE-3(2) PE-3(3)
NIST 800-53 R5.2 PE-03 PE-03(02) PE-03(03)
NIST 800-53B R5 (low) (source) PE-03
NIST 800-53B R5 (moderate) (source) PE-03
NIST 800-53B R5 (high) (source) PE-03
NIST SP 800-66 R2 164.310(a) 164.310(c)
NIST 800-82 R3 PE-03 PE-03(02) PE-03(03)
NIST 800-82 R3 LOW OT Overlay PE-03
NIST 800-82 R3 MODERATE OT Overlay PE-03
NIST 800-82 R3 HIGH OT Overlay PE-03
NIST 800-161 R1 PE-3 PE-3(2)
NIST 800-161 R1 C-SCRM Baseline PE-3
NIST 800-161 R1 Level 2 PE-3 PE-3(2)
NIST 800-161 R1 Level 3 PE-3 PE-3(2)
NIST 800-171 R2 (source) 3.10.3 3.10.5
NIST 800-171 R3 (source) 03.04.05 03.10.02.a 03.10.07.a 03.10.07.a.01 03.10.07.a.02 03.10.07.d
NIST 800-171A (source) 3.10.5[a] 3.10.5[b] 3.10.5[c]
NIST 800-171A R3 (source) A.03.04.05[03] A.03.10.02.a[01] A.03.10.07.a.01 A.03.10.07.a.02 A.03.10.07.d
NIST CSF 2.0 (source) PR.AA PR.AA-06 DE.CM-02
NIST Privacy Framework 1.0 PR.AC-P2
PCI DSS 4.0.1 (source) 9.1 9.1.2 9.2 9.2.1
PCI DSS 4.0.1 SAQ A-EP (source) 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) 9.1.2 9.2.1
PCI DSS 4.0.1 SAQ D Service Provider (source) 9.1.2 9.2.1
SCF DPMP 2026 7.3
SWIFT CSF 2025 3.1
TISAX ISA 6.0.3 8.1.3
US (25)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 PE-3 PE-3.a PE-3.b PE-3.c PE-3.d PE-3.e PE-3.f PE-3.g PE-3.h PE-3.i PE-3-IS.1 PE-3-IS.4
USA Federal C2M2 2.1 ACCESS-3a ACCESS-3d ACCESS-3e ACCESS-3f ACCESS-3g ACCESS-3j
USA Federal CMMC 2.0 Level 1 PE.L1-B.1.IX
USA Federal CMMC 2.0 Level 1 AOs PE.L1-B.1.IX[a] PE.L1-B.1.IX[d] PE.L1-B.1.IX[e] PE.L1-B.1.IX[f]
USA Federal CMMC 2.0 Level 2 PEL2.-3.10.3 PEL2.-3.10.5
USA Federal CMMC 2.0 Level 3 AC.L3-3.1.2E
USA Federal FAR 52.204-21 52.204-21(b)(1)(ix)
USA Federal CJIS Security Policy 6.0 PE-3
USA Federal FFIEC ITEH 2016 II.C.8
USA Federal FedRAMP R5 (low) PE-03
USA Federal FedRAMP R5 (moderate) PE-03
USA Federal FedRAMP R5 (high) PE-03
USA Federal FedRAMP R5 (LI-SaaS) PE-03
USA Federal IRS 1075 2021 2.B.3.4 PE-3 PE-3(CE-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)(ii) § 164.310(a)(2)(iii) § 164.310(c)
USA Federal HIPAA Administrative Simplification 2013 § 164.310(a)(2)(ii) § 164.310(a)(2)(iii) § 164.310(c)
USA Federal NERC CIP 2024 CIP-006-6 1.1 CIP-006-6 1.3 CIP-006-6 1.5 CIP-006-6 1.10
USA Federal NISPOM 2020 §117.15(e)(4)
USA California CCPA 2025 7123(c)(3)(D)
USA Massachusetts 201 CMR 17.00 2008 17.03(2)(g)
USA Texas DIR SCSC 2.2 2025 PE-03
USA Texas TX-RAMP Level 1 PE-03
USA Texas TX-RAMP Level 2 PE-03
USA Vermont Act 171 2018 2447(b)(7)
EMEA (13)
Framework Mapping Values
EMEA Germany C5 2026 PS-01.03B.2 PS-03.02B PS-03.01AC PS-04.01B PS-04.01B.3 PS-04.01B.6 PS-04.03B PS-08.01B.1
EMEA Spain CCN-STIC 825 op.acc.2 op.acc.4 op.acc.5 mp.if.1
EMEA EU DORA RTS 2024 Article 21.1(g) Article 32.2 Article 33.1
EMEA EU NIS2 Annex 2024 13.1.2(c) 13.3.1 13.3.2(b)
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-3
EMEA Saudi Arabia SACS-002 2022 VII.B.TPC-82
EMEA Saudi Arabia SAMA CSF 1.0 2017 3.3.2.3.a
EMEA UAE NIAF 2023 3.2.2
APAC (8)
Framework Mapping Values
APAC Australia CCM 2026 PRO-15
APAC Australia ISM June 2026 ISM-1296
APAC India SEBI CSCRF 2024 PR.AA.S10
APAC Japan ISMAP 11.1.1 11.1.1.1 11.1.1.2 11.1.1.3 11.1.1.4 11.1.1.5 11.1.1.6 11.1.1.7 11.1.2 11.1.2.1 11.1.2.2 11.1.2.5 11.1.2.10
APAC Malaysia RMiT 2025 A5-C5(a)
APAC New Zealand HISF MLHSP 2023 HHSP48 HML48
APAC New Zealand HISF Suppliers 2023 HSUP40
APAC Singapore MAS TRM 2021 8.5.6(e)
Americas (3)
Framework Mapping Values
Americas Argentina Reg 132 2018 B.2.4-1 B.2.4-2
Americas Canada ITSP-10-171 2025 03.04.05 03.10.02.A 03.10.07.A 03.10.07.A.01 03.10.07.A.02 03.10.07.D
Americas Canada OSFI B-13 2022 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

SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

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. ▪ Physical security controls and technologies ensure that only authorized personnel are allowed access to secure areas. ▪ A facilities maintenance team, or similar function, manages the operation of automated physical and environmental protection controls. ▪ Physical security controls and technologies are configured to enforce physical access authorizations for all physical access points (including designated entry/exit points) to facilities (excluding those areas within the facility officially designated as publicly accessible).

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 enforce physical access authorizations for all physical access points (including designated entry/exit points) to facilities (excluding 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-08_A01 physical access controls to control access to areas within the facility designated as publicly accessible are defined.
  2. PES-08_A02 physical access authorizations are enforced at entry and exit points to the facility where the system resides by controlling ingress and egress with physical access control systems, devices, or guards.
  3. PES-08_A03 entry and exit points to the facility in which the system resides are defined.
  4. PES-08_A04 entry or exit points for which physical access logs are maintained are defined.
  5. PES-08_A05 physical access devices are identified.
  6. PES-08_A06 physical access devices are controlled.
  7. PES-08_A07 physical access devices are managed.
  8. PES-08_A08 circumstances requiring visitor escorts and control of visitor activity are defined.
  9. PES-08_A09 physical access devices to be inventoried are defined.
  10. PES-08_A10 frequency at which to inventory physical access devices is defined.
  11. PES-08_A11 frequency at which to change combinations is defined.
  12. PES-08_A12 frequency at which to change keys is defined.
  13. PES-08_A13 physical access authorizations are enforced at entry and exit points by controlling ingress and egress to the facility.
  14. PES-08_A14 physical access event logs are maintained for entry or exit points.
  15. PES-08_A15 access to areas within the facility designated as publicly accessible are maintained by implementing physical access controls.
  16. PES-08_A16 visitors are escorted.
  17. PES-08_A17 visitor activity is controlled circumstances.
  18. PES-08_A18 physical access devices are inventoried frequently.
  19. PES-08_A19 combinations are changed frequently, when combinations are compromised or when individuals possessing the combinations are transferred or terminated.
  20. PES-08_A20 keys are changed frequency, when keys are lost or when individuals possessing the keys are transferred or terminated.
  21. PES-08_A21 the frequency at which to perform security checks at the physical perimeter of the facility or system for exfiltration of information or removal of system components is defined.
  22. PES-08_A22 security checks are performed C at the physical perimeter of the facility or system for exfiltration of information or removal of system components.
  23. PES-08_A23 physical access points to the facility where the system resides are defined.
  24. PES-08_A24 guards are employed to control physical access points to the facility where the system resides 24 hours per day, 7 days per week.
  25. PES-08_A25 physical access restrictions associated with changes to the system are enforced.
  26. PES-08_A26 keys, combinations, and other physical access devices are secured.

Evidence Requirements

E-PES-05 Physical Security Operations

Documented evidence of the organization's physical security capabilities as it pertains to operating and monitoring Physical Access Control (PAC) mechanisms.

Physical Security
E-PES-07 Physical Access Control Devices

Documented evidence of Physical Access Control (PAC) mechanisms.

Physical Security
E-PES-09 Key & Combination Changes

Documented evidence of key and lock combination changes.

Physical Security

Technology Recommendations

Micro/Small

  • Physical security policy
  • Door locks and key management

Small

  • Physical security policy
  • Access log
  • Visitor procedures

Medium

  • Staffed lobby (receptionist)
  • Physical security guards
  • Verify individual access authorizations before granting access to the facility.
  • Control entry to the facility containing the system using physical access devices and/or guards.
  • Control access to areas officially designated as publicly accessible in accordance with the organization's assessment of risk.
  • Secure keys, combinations and other physical access devices.

Large

  • Staffed lobby (receptionist)
  • Physical security guards
  • Verify individual access authorizations before granting access to the facility.
  • Control entry to the facility containing the system using physical access devices and/or guards.
  • Control access to areas officially designated as publicly accessible in accordance with the organization's assessment of risk.
  • Secure keys, combinations and other physical access devices.

Enterprise

  • Staffed lobby (receptionist)
  • Physical security guards
  • Verify individual access authorizations before granting access to the facility.
  • Control entry to the facility containing the system using physical access devices and/or guards.
  • Control access to areas officially designated as publicly accessible in accordance with the organization's assessment of risk.
  • Secure keys, combinations and other physical access devices.

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.