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.
This control maps to 37 controls across 22 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.2.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.
The graph holds this control, the 37 it maps to, and the evidence behind each claim, over MCP and REST.