Skip to main content

PES-02: Physical & Environmental Protections

PES 9 — Critical Govern

Mechanisms exist to facilitate the operation of physical and environmental protection controls.

Renumbered: Formerly PES-01 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, PES-02 was Physical Access Authorizations. That control is now PES-06.

Control Question: Does the organization facilitate the operation of physical and environmental protection controls?

General (48)
Framework Mapping Values
AICPA Privacy Management Framework (PMF) S7.1-POF2 S7.1-POF6
AICPA TSC 2017:2022 (used for SOC 2) (source) A1.2 A1.2-POF1 A1.2-POF2 A1.2-POF3 A1.2-POF4 A1.2-POF5 A1.2-POF6 A1.2-POF7 A1.2-POF9 CC6.4 CC6.4-POF1 CC6.4-POF2
COBIT 2019 DSS01.04 DSS01.05 DSS05.05
CSA CCM 4.1.0 DCS-01
CSA IoT SCF 2 PHY-01
GovRAMP PE-01
GovRAMP Low PE-01
GovRAMP Low+ PE-01
GovRAMP Moderate PE-01
GovRAMP High PE-01
IEC 62443-2-1 2024 ORG 3.1
ISO 27002 2022 5.14 5.15 5.18 7.1 7.5
ISO 27017 2015 9.1.1 11.1.4 13.2.1
ISO 27018 2025 5.14 5.15 5.18 7.1 7.5
MPA Content Security Program 5.3.1 OP-2.1 PS-1.5
NAIC Insurance Data Security Model Law (MDL-668) 4.D(2)(b) 4.D(2)(c) 4.D(2)(j)
NIST 800-53 R4 PE-1
NIST 800-53 R5.2 PE-01 PE-23
NIST 800-53B R5 (low) (source) PE-01
NIST 800-53B R5 (moderate) (source) PE-01
NIST SP 800-66 R2 164.310(a)
NIST 800-82 R3 PE-01 PE-23
NIST 800-82 R3 LOW OT Overlay PE-01
NIST 800-82 R3 MODERATE OT Overlay PE-01
NIST 800-82 R3 HIGH OT Overlay PE-01
NIST 800-161 R1 PE-1 PE-23
NIST 800-161 R1 C-SCRM Baseline PE-1
NIST 800-161 R1 Flow Down PE-23
NIST 800-161 R1 Level 1 PE-1
NIST 800-161 R1 Level 2 PE-1 PE-23
NIST 800-161 R1 Level 3 PE-1 PE-23
NIST 800-171 R2 (source) 3.10.2 NFO - PE-1
NIST 800-171 R3 (source) 03.08.01 03.08.02 03.10.01.a 03.10.07.a 03.10.07.a.01
NIST 800-171A (source) 3.10.2[a] 3.10.2[b] 3.10.2[c] 3.10.2[d]
NIST 800-171A R3 (source) A.03.08.01[01] A.03.08.01[02] A.03.08.02 A.03.10.01.a[01] A.03.10.01.a[02] A.03.10.01.a[03] A.03.10.07.a.01
NIST CSF 2.0 (source) ID.AM PR.AA PR.AA-06 PR.IR-02 DE.CM-02
NIST Privacy Framework 1.0 PR.PO-P4 PR.AC-P2
PCI DSS 4.0.1 (source) 9.1 9.1.1 9.2
PCI DSS 4.0.1 SAQ B-IP (source) 9.1.1
PCI DSS 4.0.1 SAQ C (source) 9.1.1
PCI DSS 4.0.1 SAQ C-VT (source) 9.1.1
PCI DSS 4.0.1 SAQ D Merchant (source) 9.1.1
PCI DSS 4.0.1 SAQ D Service Provider (source) 9.1.1
PCI DSS 4.0.1 SAQ P2PE (source) 9.1.1
SCF DPMP 2026 7.3
SPARTA 4.0 CM0053
SWIFT CSF 2025 3.1
TISAX ISA 6.0.3 8.1.2
US (23)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 PE-1
USA Federal C2M2 2.1 ACCESS-3a ACCESS-3d ARCHITECTURE-3a ARCHITECTURE-3j
USA Federal CERT RMM 1.2 EC:SG4 EC:SG4.SP2 EC:GG1.GP1 EC:GG2 EC:GG2.GP2
USA Federal CMMC 2.0 Level 2 PEL2.-3.10.2
USA Federal CJIS Security Policy 6.0 PE-1
USA Federal FFIEC ITEH 2016 II.C.8
USA Federal FedRAMP R5 (low) PE-01
USA Federal FedRAMP R5 (moderate) PE-01
USA Federal FedRAMP R5 (high) PE-01
USA Federal FedRAMP R5 (LI-SaaS) PE-01
USA Federal IRS 1075 2021 2.B.2 PE-1 PE-1(IRS-Defined)-1 PE-1(IRS-Defined)-2 PE-1(IRS-Defined)-3
USA Federal HIPAA Security Rule NIST SP 800-66 R2 § 164.310(a)(1) § 164.310(a)(2)(ii) § 164.310(a)(2)(iv)
USA Federal HIPAA Administrative Simplification 2013 § 164.310(a)(1) § 164.310(a)(2)(ii) § 164.310(a)(2)(iv)
USA Federal NERC CIP 2024 CIP-003-8 1.1.3 CIP-003-8 1.2.2
USA Federal NRC 10 CFR 73.54 2015 73.54(b)(3)
USA Federal TSA SDP 2021-02F III.C
USA Federal TSA / DHS 1580/82-2022-01 III.C
USA California CCPA 2025 7123(c)(3)(D)
USA New York DFS 23 NYCRR500 2023 Amd 2 500.3(j)
USA New York SHIELD Act 2019 899-bb.2(b)(ii)(C)
USA Texas DIR SCSC 2.2 2025 PE-01
USA Texas TX-RAMP Level 1 PE-01
USA Texas TX-RAMP Level 2 PE-01
EMEA (15)
Framework Mapping Values
EMEA Germany C5 2026 PS-05.01B PS-05.02B
EMEA Spain CCN-STIC 825 op.acc.2 op.acc.4 op.acc.5 mp.if.1 mp.if.3 mp.if.5 mp.if.6 mp.s.1
EMEA Spain Royal Decree 311 2022 Article 12(6)(f)
EMEA EU DORA RTS 2024 Article 18.1 Article 18.2 Article 18.2(b) Article 32.1 Article 32.2 Article 32.3
EMEA EU EBA GL/2019/04 3.4.3.33
EMEA EU NIS2 Annex 2024 13.1.1 13.1.3 13.2.1 13.2.2(a) 13.2.3 13.3.2(a) 13.3.3
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.1-30.c 3.4.3-33 3.4.3-35
EMEA Saudi Arabia ECC-1 2018 2-3-1 2-3-2 2-14-1 2-14-2 2-14-3-1 2-14-3-2 2-14-3-3 2-14-3-5 2-14-4
EMEA Saudi Arabia OTCC-1 2022 2-3-1 2-3-2 2-13-1 2-13-2
EMEA Saudi Arabia SAMA CSF 1.0 2017 3.3.2 3.3.2.1 3.3.2.3
EMEA UAE NIAF 2023 3.2.2
APAC (8)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-0810
APAC India SEBI CSCRF 2024 PR.AA.S10 PR.IP.S9
APAC Japan ISMAP 5.1.1.11 11.0 11.1 11.1.4 11.1.4.1 11.2.1.3
APAC Malaysia RMiT 2025 12.1(c) A7-D1(b) A8-2(d)
APAC New Zealand HISF MLHSP 2023 HHSP47 HML47
APAC New Zealand HISF Suppliers 2023 HSUP11 HSUP39
APAC New Zealand NZISM 3.9 5.7.4.C.01 8.1.10.C.01 20.2.16.C.01
APAC Singapore MAS TRM 2021 8.5.5 8.5.6
Americas (4)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.08.01 03.08.02 03.10.01.A 03.10.07.A 03.10.07.A.01
Americas Canada OSFI B-13 2022 3.2.10
Americas Canada OSFI Self-Assessment Guidance 3.2.10
Americas Canada PIPEDA 2000 P7-4.7.3(a)

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. ▪ 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.

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 capability exists to facilitate the operation of physical and environmental protection controls.

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-02_A01 the physical facility where organizational systems reside is protected.
  2. PES-02_A02 the location or site of the facility where the system resides is planned considering physical and environmental hazards.
  3. PES-02_A03 for existing facilities, physical and environmental hazards are considered in the organizational risk management strategy.
  4. PES-02_A04 the support infrastructure for organizational systems is protected.
  5. PES-02_A05 the physical facility where organizational systems reside is monitored.
  6. PES-02_A06 the support infrastructure for organizational systems is monitored.
  7. PES-02_A07 physical security operations are conducted according to documented policies, standards, procedures and/or other organizational directives.
  8. PES-02_A08 adequate resources (e.g., people, processes, technologies, data and/or facilities) are provided to support physical security operations.
  9. PES-02_A09 responsibility and authority for the performance of physical security-related activities are assigned to designated personnel.
  10. PES-02_A10 personnel performing physical security-related activities have the skills and knowledge needed to perform their assigned duties.

Evidence Requirements

E-PES-04 Physical Security Plan

Documented evidence of a physical security plan.

Physical Security

Technology Recommendations

Micro/Small

  • Physical security policy
  • Door locks and key management

Small

  • Physical security policy
  • Access log
  • Visitor sign-in procedure

Medium

  • Formal physical security program
  • Card-based access control
  • CCTV

Large

  • Enterprise physical security program
  • Multi-zone card access
  • CCTV monitoring
  • Security guard coverage

Enterprise

  • Enterprise physical security platform (e.g., Lenel, Genetec)
  • Integrated access control/CCTV
  • 24/7 security operations
  • Environmental monitoring

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.