Skip to main content

PES-14: Visitor Control

PES 9 — Critical Protect

Physical access control mechanisms exist to identify, authorize and monitor visitors before allowing access to the facility (other than areas designated as publicly accessible).

Renumbered: Formerly PES-06 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, PES-14 was Asset Monitoring and Tracking. That control is now PES-19.

Control Question: Does the organization identify, authorize and monitor visitors before allowing access to the facility (other than areas designated as publicly accessible)?

General (17)
Framework Mapping Values
ISO 27002 2022 7.2
ISO 27017 2015 11.1.2
ISO 27018 2025 7.2
MPA Content Security Program 5.3.1 OP-1.0 PS-1.1
NIST SP 800-66 R2 164.310(a)
NIST 800-171 R2 (source) 3.10.3
NIST 800-171 R3 (source) 03.10.01.a 03.10.07.c
NIST 800-171A (source) 3.10.3[a] 3.10.3[b]
NIST 800-171A R3 (source) A.03.10.01.a[02] A.03.10.07.c[01] A.03.10.07.c[02]
NIST 800-172 R3 03.10.01E
NIST 800-172A R3 A.03.10.01E.ODP[01]
PCI DSS 4.0.1 (source) 9.3.2 9.3.3 9.3.4
PCI DSS 4.0.1 SAQ D Merchant (source) 9.3.2 9.3.3 9.3.4
PCI DSS 4.0.1 SAQ D Service Provider (source) 9.3.2 9.3.3 9.3.4
SCF DPMP 2026 7.3
SWIFT CSF 2025 3.1
TISAX ISA 6.0.3 8.1.7
US (10)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 PE-3-IS.5
USA Federal CMMC 2.0 Level 1 PE.L1-B.1.IX
USA Federal CMMC 2.0 Level 2 PEL2.-3.10.3
USA Federal NNPI (unclass) 2010 8-3.a 8-3.a(1) 8-3.a(3)
USA Federal FAR 52.204-21 52.204-21(b)(1)(ix)
USA Federal IRS 1075 2021 2.B.3.1 2.B.3.1-1 2.B.3.1-2 2.B.3.1-3 2.B.3.1-4 2.B.3.1-5 2.B.3.1-6 2.B.3.1-7
USA Federal HIPAA Security Rule NIST SP 800-66 R2 § 164.310(a)(2)(iii)
USA Federal HIPAA Administrative Simplification 2013 § 164.310(a)(2)(iii)
USA Federal NERC CIP 2024 CIP-006-6 1.2 CIP-006-6 1.3 CIP-006-6 R2 CIP-006-6 2.2
USA California CCPA 2025 7123(c)(3)(D)
EMEA (4)
Framework Mapping Values
EMEA Germany C5 2026 PS-04.01B.7
EMEA Spain CCN-STIC 825 mp.if.2 mp.if.7
EMEA Saudi Arabia OTCC-1 2022 2-13-1-6
EMEA Saudi Arabia SACS-002 2022 VII.B.TPC-47 VII.B.TPC-47-BP2 VII.B.TPC-47-BP3
APAC (4)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-0164
APAC Japan ISMAP 11.1.2.4
APAC New Zealand NZISM 3.9 9.4.4.C.01 9.4.5.C.01 9.4.5.C.02 9.4.6.C.01 9.4.6.C.02 9.4.7.C.01 9.4.8.C.01 9.4.9.C.01 9.4.10.C.01
APAC Singapore MAS TRM 2021 8.5.6(b)
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.10.01.A 03.10.07.C

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 distinguish between onsite personnel and visitors, especially in areas where sensitive/regulated data is accessible. ▪ Users are trained and encouraged to stop and question anyone attempting to install or remove IT assets from facilities.

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 identify, authorize and monitor visitors before allowing access to the facility (other than areas 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

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. ▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes. ▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions via Artificial Intelligence (AI) or Machine Learning (ML) technologies.

Assessment Objectives

  1. PES-14_A01 visitors are escorted.
  2. PES-14_A02 visitor activity is controlled.

Evidence Requirements

E-PES-02 Visitor Logbook

Documented evidence of a visitor management and logging visitor activities.

Physical Security

Technology Recommendations

Micro/Small

  • Visitor logbook
  • iLobby (https://goilobby.com)
  • The Receptionist (https://thereceptionist.com)
  • LobbyGuard (http://lobbyguard.com)

Small

  • Visitor logbook
  • iLobby (https://goilobby.com)
  • The Receptionist (https://thereceptionist.com)
  • LobbyGuard (http://lobbyguard.com)

Medium

  • Visitor logbook
  • iLobby (https://goilobby.com)
  • The Receptionist (https://thereceptionist.com)
  • LobbyGuard (http://lobbyguard.com)

Large

  • Staffed lobby (receptionist)
  • Visitor logbook

Enterprise

  • Staffed lobby (receptionist)
  • Visitor logbook

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.