EvidenceSheet
PCI DSS v4.0.1 · Req 5: Anti-Malware

5.3.2.1 Targeted risk analysis sets malware scan frequency

Where the entity relies on periodic malware scans to satisfy Requirement 5.3.2, the scan frequency must be fixed by a targeted risk analysis of the entity, and that analysis must be performed according to every element specified in Requirement 12.3.1. Applicability: applies to entities using periodic malware scans to meet 5.3.2. This was advisory only up to 31 March 2025 and is now required and fully assessed. Objective under the customized approach: the malware solution scans at a frequency matching the entity's risk. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

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

4
artefacts
2
held by a system
1
at each review
easy
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

  • Scan schedule configuration matching the frequency in the analysis · Vulnerability scanner / patch tooling
  • Scan completion reports across the assessment period · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

  • Evidence the analysis covers the 12.3.1 elements and has an approver and review date · Document repository

governing documentDocuments that govern the control

  • Targeted risk analysis defining the periodic scan frequency and rationale · Policy repository / GRC workspace

First move

Automate the pull from your Vulnerability scanner / patch tooling. Scan schedule, findings and remediation age straight from the scanner; patch compliance from the patch console.

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

5.3.2 Periodic and real-time scans or continuous behavioural analysis · 5.3.3 Anti-malware covers removable electronic media