What evidence do auditors commonly ask for on 1.5.1 Security controls on dual-connected devices?

Policy and configuration standard for laptops and mobile devices that connect to both the internet and the CDE; Endpoint management console reports showing personal firewall or endpoint protection running and locked against user changes; Management authorisation records for any temporary disabling, with time limits; VPN configuration showing split tunnelling disabled for devices accessing the CDE; Alerting records for security controls disabled on administrator devices.

What is the most common gap auditors find on 1.5.1?

Employee-owned devices access the CDE without enforced endpoint controls

PCI DSS v4.0.1 · Req 1: Network Security Controls

`1.5.1` Security controls on dual-connected devices

Any computing device, whether owned by the company or by an employee, that connects both to untrusted networks (the internet included) and to the CDE must have security controls where: (a) specific configuration settings are defined to stop threats entering the entity's network; (b) the security controls are actively running; and (c) users of the device cannot change the controls unless management has documented and authorised it case by case for a limited time. Applicability: controls may be disabled temporarily only for a legitimate technical need with case-by-case management authorisation, formally approved, and extra measures may be needed while they are off; this covers both employee-owned and company-owned devices. Customized approach objective: devices that touch untrusted environments and the CDE cannot bring threats into the CDE.

Source: PCI DSS v4.0.1, 1.5.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

artefacts

held by a system

at each review

easy

to go live

Endpoint management (MDM / EDR)

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Endpoint management console reports showing personal firewall or endpoint protection running and locked against user changes · Endpoint management (MDM / EDR)
VPN configuration showing split tunnelling disabled for devices accessing the CDE · Endpoint management (MDM / EDR)
Alerting records for security controls disabled on administrator devices · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

Management authorisation records for any temporary disabling, with time limits · Endpoint management (MDM / EDR)

governing documentDocuments that govern the control

Policy and configuration standard for laptops and mobile devices that connect to both the internet and the CDE · Policy repository / GRC workspace

First move

Automate the pull from your Endpoint management (MDM / EDR). Device compliance report from the MDM (encryption, EDR agent, OS version) on a daily pull.

Common gaps auditors find

Employee-owned devices access the CDE without enforced endpoint controls
Local administrators can disable endpoint protection without authorisation or alerting
Temporary exceptions granted with no expiry and never revoked

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

1.4.5 Internal IP and routing disclosure limited · 2.1.1 Requirement 2 policies and procedures governed