PCI DSS 4.0 5.3.2: 5.3.2 Periodic and real-time scans or continuous behavioural analysis
The anti-malware solution or solutions must do at least one of the following: run periodic scans combined with real-time or active scans; or carry out continuous behavioural analysis of systems or processes. Scans should cover the whole file system, including disks, memory, start-up files and boot records, and commonly missed software such as mail servers, browsers and IM clients. Real-time scanning inspects a file whenever it is opened, closed, renamed or otherwise accessed. Applicability: applies to every entity in scope, with no special notes. Objective under the customized approach: malware is unable to finish executing.
This control maps to 34 controls across 18 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 5.3.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.