Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-UEM-09: Anti-Malware Detection and Prevention

What else in your programme already covers this

This control maps to 33 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.

CIS Controls v8 · 4 controls

CIS-10.1 Deploy and Maintain Anti-Malware Software
CIS-10.5 Enable Anti-Exploitation Features
CIS-10.6 Centrally Manage Anti-Malware Software
CIS-10.7 Use Behavior-Based Anti-Malware Software

PCI DSS 4.0 · 4 controls

5.2.1 5.2.1 Anti-malware deployed on all system components
5.2.2 5.2.2 Anti-malware detects and handles all known malware
5.3.2 5.3.2 Periodic and real-time scans or continuous behavioural analysis
5.3.3 5.3.3 Anti-malware covers removable electronic media

ASD Strategies to Mitigate Cyber Security Incidents · 3 controls

ASD37-12 Antivirus software with heuristics (Very Good)
ASD37-16 Antivirus software with signatures (Limited)
ASD37-29 Host-based IDS/IPS (Very Good)

Azure Security Benchmark · 2 controls

ES-1 Use Endpoint Detection and Response (EDR)
ES-2 Use modern anti-malware software

CMMC 2.0 · 2 controls

SI.L2-3.14.2 Malicious Code Protection
SI.L2-3.14.5 System & File Scanning

UK Cyber Essentials · 2 controls

CE-MP.1 Anti-Malware Software Deployed
CE-MP.3 Anti-Malware Scans Files on Access and Web Pages

ACSC Essential Eight · 1 control

E8-MACRO-ML1 Configure Microsoft Office Macro Settings (ML1)

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-5 Limit, prevent, detect and remove malware

C5 (Germany) · 1 control

C5-OPS-05 Protection Against Malware - Implementation

FedRAMP High · 1 control

SI-3 Malicious Code Protection

HIPAA Security Rule · 1 control

164.308(a)(5)(ii)(B) Protection from Malicious Software (Addressable)

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events

NIST SP 800-161 Rev 1 · 1 control

161R1-SI-3 Malicious Code Protection

NIST SP 800-171 Rev 3 · 1 control

03.14.02 Malicious Code Protection

NIST SP 800-172 · 1 control

3.4.2e Automated Detection and Remediation of Unauthorized Software

NIST SP 800-53 Rev 5 · 1 control

NIST800-SI-3 SI-3 Malicious Code Protection

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(5)(ii)(B) Protection from Malicious Software (Addressable)

SOC 2 · 1 control

SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software

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.

You are reading one control. How much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-UEM-09 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 controls already carry evidence.

If you hold NIST SP 800-53 Rev 571.1% covered · 57 gaps If you hold FedRAMP Moderate60.4% covered · 78 gaps If you hold PCI DSS 4.060.4% covered · 78 gaps If you hold C5 (Germany)58.4% covered · 82 gaps If you hold ISO 27001:202256.3% covered · 86 gaps If you hold ISO 27002:202256.3% covered · 86 gaps

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. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free