What evidence do auditors commonly ask for on 5.2.2 Anti-malware detects and handles all known malware?

Vendor documentation describing detection coverage across malware types; Policy configuration exports showing detection engines and remediation actions (quarantine, block, remove) enabled; Sample detection events showing malware was blocked or quarantined; Configuration showing script and malicious link protection modules enabled where offered.

What is the most common gap auditors find on 5.2.2?

Solution configured to detect only, with automatic block or quarantine turned off

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

`5.2.2` Anti-malware detects and handles all known malware

The anti-malware solution or solutions deployed must both: identify all known types of malware; and remove, block or contain all known types of malware. Solutions may combine network-based, host-based and endpoint security controls and use techniques beyond signatures, for example machine learning, sandboxing and controls on privilege escalation. Examples of malware include ransomware, worms, Trojans, viruses, keyloggers, spyware, rootkits and malicious scripts, code or links. Applicability: applies to every entity in scope, with no special notes. Objective under the customized approach: malware is unable to run or to spread to other system components.

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

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

Policy configuration exports showing detection engines and remediation actions (quarantine, block, remove) enabled · Endpoint management (MDM / EDR)
Sample detection events showing malware was blocked or quarantined · Endpoint management (MDM / EDR)
Configuration showing script and malicious link protection modules enabled where offered · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Vendor documentation describing detection coverage across malware types · 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

Solution configured to detect only, with automatic block or quarantine turned off
Behavioural or script protection modules licensed but disabled
Different policies on server and workstation groups, with servers left on a weaker profile

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.2.1 Anti-malware deployed on all system components · 5.2.3 Periodic evaluation of components not at risk from malware