PES-17: Access Control for Output Devices
Physical security mechanisms exist to restrict access to printers and other system output devices to prevent unauthorized individuals from obtaining the output.
Renumbered: Formerly PES-12.2 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, PES-17 was Proximity Sensor. That control is now EMB-24.
Control Question: Does the organization restrict access to printers and other system output devices to prevent unauthorized individuals from obtaining the output?
General (21)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | PI1.4 |
| COBIT 2019 | DSS05.06 |
| GovRAMP | PE-05 |
| GovRAMP Low+ | PE-05 |
| GovRAMP Moderate | PE-05 |
| GovRAMP High | PE-05 |
| NIST 800-53 R4 | PE-5 |
| NIST 800-53 R5.2 | PE-05 |
| NIST 800-53B R5 (moderate) (source) | PE-05 |
| NIST 800-53B R5 (high) (source) | PE-05 |
| NIST 800-82 R3 | PE-05 |
| NIST 800-82 R3 MODERATE OT Overlay | PE-05 |
| NIST 800-82 R3 HIGH OT Overlay | PE-05 |
| NIST 800-171 R2 (source) | 3.10.1 |
| NIST 800-171 R3 (source) | 03.10.07.e |
| NIST 800-171A R3 (source) | A.03.10.07.e |
| PCI DSS 4.0.1 (source) | 9.2.2 9.2.3 |
| 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 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 9.2.2 9.2.3 |
US (9)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | PE-5 |
| USA Federal CMMC 2.0 Level 1 | PE.L1-B.1.VIII |
| 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-5 |
| USA Federal FedRAMP R5 (moderate) | PE-05 |
| USA Federal FedRAMP R5 (high) | PE-05 |
| USA Federal IRS 1075 2021 | PE-5 |
| USA Texas TX-RAMP Level 2 | PE-05 |
APAC (2)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-1036 |
| APAC New Zealand NZISM 3.9 | 11.8.9.C.01 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.10.07.E |
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 restrict access to printers and other system output devices to prevent unauthorized individuals from obtaining the output.
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
- PES-17_A01 output devices that require physical access control to output are defined.
- PES-17_A02 physical access to output devices is controlled to prevent unauthorized individuals from obtaining access to sensitive / regulated data.
- PES-17_A03 physical access to output devices is controlled to prevent unauthorized individuals from obtaining access to CUI.
Technology Recommendations
Micro/Small
- Physical security policy
- Door locks and key management
Small
- Physical security policy
- Access log
- Visitor procedures
Medium
- Printer management (print only when at the printer with proximity card or code)
Large
- Printer management (print only when at the printer with proximity card or code)
Enterprise
- Printer management (print only when at the printer with proximity card or code)