What evidence do auditors commonly ask for on A3.2.2.1 Post-change confirmation that PCI DSS controls are in place?

Post-implementation PCI DSS checklist attached to change records; Configuration compliance scan of newly deployed systems; Updated asset inventory and network diagrams after change; Evidence of new systems added to vulnerability scanning and log collection.

What is the most common gap auditors find on A3.2.2.1?

Change closed without any post-implementation control verification

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

`A3.2.2.1` Post-change confirmation that PCI DSS controls are in place

Once a change is complete, the entity must confirm that every relevant PCI DSS requirement is in place on all new or modified systems and networks and update documentation where applicable. Linked to the PCI DSS scoping section; Requirements 1-12. Guidance examples of checks: updated network diagrams, configuration to hardening standards with defaults changed and unneeded services off, required controls such as FIM, anti-malware, patching and audit logging, no stored sensitive authentication data, and inclusion in quarterly vulnerability scanning. 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.2.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

moderate

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

Configuration compliance scan of newly deployed systems · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

Post-implementation PCI DSS checklist attached to change records · Ticketing / ITSM
Evidence of new systems added to vulnerability scanning and log collection · Vulnerability scanner / patch tooling

governing documentDocuments that govern the control

Updated asset inventory and network diagrams after change · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Change closed without any post-implementation control verification
New servers missing from FIM, anti-malware or logging coverage
Diagrams and inventories not updated after the change

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.2 Scope impact of every system or network change · A3.2.3 Scope review after organizational structure changes