Malicious code prevention. Level 1 (a to g): detection, prevention and recovery against malicious code; anti-malware protecting all systems; solutions able to detect, remove and protect against common malicious software; solutions kept current, running and generating audit trails; updates at least daily or on vendor release; the ability to roll back or mitigate an update that causes malfunction; and awareness procedures for cloud administrators. Level 2 is the same; Level 3 (a and b) adds periodic testing of prevention, detection and recovery against malicious code, and sandboxing or isolation of customer-supplied code so the platform and other tenants are unaffected.
This control maps to 1 controls across 1 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.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.