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.
This control maps to 17 controls across 12 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
PCI DSS 4.0 5.3.2.1 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.
The graph holds this control, the 17 it maps to, and the evidence behind each claim, over MCP and REST.