EvidenceSheet
PCI DSS v4.0.1 · Req 6: Secure Systems and Software

6.5.2 Confirm PCI DSS controls after significant change

When a significant change is complete, the entity must confirm that every applicable PCI DSS requirement is in place on all new or altered systems and networks, and must update documentation where relevant. It applies to all entities. Applicability: such significant changes should also be recorded in, and reflected by, the scope confirmation the entity performs each year under Requirement 12.5.2. Customized approach objective: after a significant change, all system components are checked to be compliant with the PCI DSS requirements that apply to them.

Source: PCI DSS v4.0.1, 6.5.2. 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
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
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

none for this control

periodic reviewEvidence produced at each review

  • Evidence new systems were added to vulnerability scanning, logging, anti-malware and FIM · Vulnerability scanner / patch tooling
  • Link from significant changes to the annual scope confirmation record · Ticketing / ITSM

governing documentDocuments that govern the control

  • Significant change criteria definition · Policy repository / GRC workspace
  • Post-change PCI DSS validation checklists for recent significant changes · Policy repository / GRC workspace
  • Updated network and data-flow diagrams and system inventory after the change · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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

6.5.1 Change control procedure for production · 6.5.3 Separate pre-production from production