Audit logs produced by the anti-malware solution or solutions must be turned on and kept in line with Requirement 10.5.1. These logs let the entity confirm that updates and scans run as expected, that malware is found and dealt with, and trace how malware got in and what it did. Applicability: applies to every entity in scope, with no special notes. Customized approach objective: records of anti-malware activity are available immediately and kept for at least 12 months.
This control maps to 34 controls across 16 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.4 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 34 it maps to, and the evidence behind each claim, over MCP and REST.