Skip to main content

PES-16: Equipment Siting & Protection

PES 9 — Critical Protect

Physical security mechanisms exist to locate system components within the facility to minimize potential damage from physical and environmental hazards and to minimize the opportunity for unauthorized access.

Renumbered: Formerly PES-12 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, PES-16 was Component Marking. That control is now PES-18.

Control Question: Does the organization locate system components within the facility to minimize potential damage from physical and environmental hazards and to minimize the opportunity for unauthorized access?

General (29)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) A1.2
CSA CCM 4.1.0 DCS-16
CSA IoT SCF 2 PHY-01
GovRAMP PE-18
GovRAMP High PE-18
ISO 27002 2022 7.3 7.5 7.8 7.12
ISO 27017 2015 11.1.4 11.2.1 11.2.3
ISO 27018 2025 7.3 7.5 7.8 7.12
MPA Content Security Program 5.3.1 PS-1.0
NIST 800-53 R4 PE-18 PE-18(1) SC-7(14)
NIST 800-53 R5.2 PE-18 PE-23 SC-07(14)
NIST 800-53B R5 (high) (source) PE-18
NIST 800-82 R3 PE-18 PE-23 SC-07(14)
NIST 800-82 R3 HIGH OT Overlay PE-18
NIST 800-161 R1 PE-18 PE-23 SC-7(14)
NIST 800-161 R1 Flow Down PE-23
NIST 800-161 R1 Level 1 PE-18
NIST 800-161 R1 Level 2 PE-18 PE-23 SC-7(14)
NIST 800-161 R1 Level 3 PE-18 PE-23 SC-7(14)
NIST 800-171 R2 (source) 3.10.1
NIST 800-171 R3 (source) 03.10.07.e 03.10.08
NIST 800-171A R3 (source) A.03.10.07.e A.03.10.08
PCI DSS 4.0.1 (source) 9.2.2 9.2.3 9.2.4
PCI DSS 4.0.1 SAQ B-IP (source) 9.2.2
PCI DSS 4.0.1 SAQ C (source) 9.2.2
PCI DSS 4.0.1 SAQ D Merchant (source) 9.2.2 9.2.3 9.2.4
PCI DSS 4.0.1 SAQ D Service Provider (source) 9.2.2 9.2.3 9.2.4
SWIFT CSF 2025 3.1
TISAX ISA 6.0.3 8.1.4
US (9)
EMEA (4)
Framework Mapping Values
EMEA Germany C5 2026 PS-06.03AC
EMEA Spain CCN-STIC 825 mp.if.3 mp.if.5 mp.if.6
EMEA EU DORA RTS 2024 Article 18.2(c)
EMEA Saudi Arabia SAMA CSF 1.0 2017 3.3.2.3.e
APAC (4)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-1644
APAC Japan ISMAP 11.2 11.2.1 11.2.1.1 11.2.1.2 11.2.1.4 11.2.1.5 11.2.1.6 11.2.1.7 11.2.1.8 11.2.1.9 11.2.1.10 11.2.7.4.PB
APAC Malaysia RMiT 2025 10.26
APAC New Zealand NZISM 3.9 8.3.3.C.01 8.3.4.C.01 8.3.4.C.02 8.3.5.C.01
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.10.07.E 03.10.08

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. ▪ Physical security controls address system component location within the facility to minimize potential damage from physical and environmental hazards and to minimize the opportunity for unauthorized access. ▪ Physical security controls isolate information processing facilities from points such as delivery and loading areas and other points to avoid unauthorized access.

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 locate system components within the facility to minimize potential damage from physical and environmental hazards and to minimize the opportunity for unauthorized access.

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-16_A01 the location or site of the facility where the system resides is planned considering physical and environmental hazards.
  2. PES-16_A02 for existing facilities, physical and environmental hazards are considered in the organizational risk management strategy.
  3. PES-16_A03 physical and environmental hazards that could result in potential damage to system components within the facility are defined.
  4. PES-16_A04 system components are positioned within the facility to minimize potential damage from physical and environmental hazards and to minimize the opportunity for unauthorized access.
  5. PES-16_A05 managed interfaces to be protected against unauthorized physical connections are defined.
  6. PES-16_A06 managed interfaces are protected against unauthorized physical connections.

Evidence Requirements

E-PES-04 Physical Security Plan

Documented evidence of a physical security plan.

Physical Security

Technology Recommendations

Micro/Small

  • Server equipment kept off the floor, away from windows, water pipes and public areas

Small

  • Server room located away from environmental hazards and public access
  • Equipment racked and secured

Medium

  • Server room siting considers flood, fire, HVAC and public exposure
  • Environmental risk assessment for equipment locations

Large

  • Data center design standards for equipment siting (e.g., TIA-942)
  • Environmental hazard assessment
  • Hardened equipment rooms

Enterprise

  • Enterprise facility design program aligned with TIA-942 / Uptime Institute tiers
  • Formal site risk assessments
  • Physical security reviews during facility design

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.