EvidenceSheet
PCI DSS v4.0.1 · Appendix A3: Designated Entities Supplemental Validation (DESV)

A3.2.4 Six-monthly penetration testing of segmentation controls

Where segmentation is in use, PCI DSS scope must be confirmed by: following the entity's methodology defined in Requirement 11.4.1; pen-testing the segmentation controls every six months at a minimum and after any change to segmentation controls or methods; testing covering all segmentation controls and methods in use; and testing showing the controls are operational and effective and keep every out-of-scope system separated from the CDE. PCI DSS reference: Requirement 11. Guidance: base PCI DSS normally expects segmentation pen-testing every twelve months, and testing as often as possible is encouraged. Applies only to designated entities. Customized approach objective: not eligible for the customized approach; only the defined approach can be used.

Source: PCI DSS v4.0.1, A3.2.4. 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.

5
artefacts
1
held by a system
2
at each review
hard
to go live
Vulnerability scanner / patch tooling
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

  • Change records for segmentation changes and matching retests · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

  • Two most recent semi-annual segmentation penetration test reports · Vulnerability scanner / patch tooling
  • Remediation and retest evidence for segmentation failures · Vulnerability scanner / patch tooling

governing documentDocuments that govern the control

  • Penetration testing methodology per Requirement 11.4.1 · Policy repository / GRC workspace
  • Inventory of segmentation controls and methods cross-referenced to test coverage · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Vulnerability scanner / patch tooling on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

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

A3.2.3 Scope review after organizational structure changes · A3.2.5 Data-discovery methodology for cleartext PAN