1.5.1 Security controls are implemented on any computing devices, including company- and employee-owned devices, that connect to both untrusted networks (including the Internet) and the CDE as follows:
- Specific configuration settings are defined to prevent threats being introduced into the entity's network.
- Security controls are actively running.
- Security controls are not alterable by users of the computing devices unless specifically documented and authorized by management on a case-by-case basis for a limited period.
Defined Approach Requirements
1.5.1 Security controls are implemented on any computing devices, including company- and employee-owned devices, that connect to both untrusted networks (including the Internet) and the CDE as follows:
- Specific configuration settings are defined to prevent threats being introduced into the entity's network.
- Security controls are actively running.
- Security controls are not alterable by users of the computing devices unless specifically documented and authorized by management on a case-by-case basis for a limited period.
Customized Approach Objective
Devices that connect to untrusted environments and also connect to the CDE cannot introduce threats to the entity's CDE.
Defined Approach Testing Procedures
1.5.1.a Examine policies and configuration standards and interview personnel to verify security controls for computing devices that connect to both untrusted networks, and the CDE, are implemented in accordance with all elements specified in this requirement.
1.5.1.b Examine configuration settings on computing devices that connect to both untrusted networks and the CDE to verify settings are implemented in accordance with all elements specified in this requirement.
Purpose
Computing devices that are allowed to connect to the Internet from outside the corporate environment-for example, desktops, laptops, tablets, smartphones, and other mobile computing devices used by employees-are more vulnerable to Internet-based threats.
Use of security controls such as host-based controls (for example, personal firewall software or end-point protection solutions), network-based security controls (for example, firewalls, network-based heuristics inspection, and malware simulation), or hardware, helps to protect devices from Internet-based attacks, which could use the device to gain access to the organization's systems and data when the device reconnects to the network.
Applicability Notes
These security controls may be temporarily disabled only if there is legitimate technical need, as authorized by management on a case-by-case basis. If these security controls need to be disabled for a specific purpose, it must be formally authorized. Additional security measures may also need to be implemented for the period during which these security controls are not active.
This requirement applies to employee-owned and company-owned computing devices. Systems that cannot be managed by corporate policy introduce weaknesses and provide opportunities that malicious individuals may exploit.
Good Practice
The specific configuration settings are determined by the entity and should be consistent with its network security policies and procedures.
Where there is a legitimate need to temporarily disable security controls on a company-owned or employee-owned device that connects to both an untrusted network and the CDE -for example, to support a specific maintenance activity or investigation of a technical problem - the reason for taking such action is understood and approved by an appropriate management representative. Any disabling or altering of these security controls, including on administrators' own devices, is performed by authorized personnel. It is recognized that administrators have privileges that may allow them to disable security controls on their own computers, but there should be alerting mechanisms in place when such controls are disabled and follow up that occurs to ensure processes were followed.
Practices include forbidding split-tunneling of VPNs for employee-owned or corporate-owned mobile devices and requiring that such devices boot up into a VPN.
purpose
Prevent threats from dual-homed devices bridging untrusted networks and the CDE.
whats required for compliance
- Security controls (e.g., endpoint protection, personal firewalls) enforced on all such devices.
- Controls cannot be disabled by users except with management approval.
compliance strategies
- Endpoint detection & response (EDR)
- Mobile device management (MDM)
- Written exceptions process for temporary disabling
typical policies procedures
- Mobile Device Security Policy
- Endpoint Protection Standard
common pitfalls failures
- Personal devices without MDM
- Disabled EDR for 'convenience'
type
Technical Control
difficulty
High
key risks
- Compromised endpoints infecting CDE
product vendor recommendations
- Use EDR solutions (CrowdStrike, SentinelOne)
Eligible SAQ
- SAQ-A-EP
- SAQ-C-VT
- SAQ-D MERCHANT
- SAQ-D SERVICE PROVIDER
Your perspective on this PCI DSS requirement matters! Share your implementation experiences, challenges, or questions below. Your insights help other organizations improve their compliance journey and build a stronger security community.Comment Policy