CMMC 2.0 SI.L2-3.14.4: Update Malicious Code Protection

What else in your programme already covers this

This control maps to 31 controls across 23 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 3 controls

NIST800-SI-3 SI-3 Malicious Code Protection
NIST800-SI-7 SI-7 Software, Firmware, and Information Integrity
SP800-53-SI System and Information Integrity Family

PCI DSS 4.0 · 3 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.1 5.3.1 Anti-malware kept current through automatic updates

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

ASD37-12 Antivirus software with heuristics (Very Good)
ASD37-16 Antivirus software with signatures (Limited)

Azure Security Benchmark · 2 controls

ASBv3-ES-3 Ensure anti-malware software and signatures are updated
ES-2 Use modern anti-malware software

ISO 27001:2022 · 2 controls

8.7 Protection against malware
8.8 Management of technical vulnerabilities

ISO 27002:2022 · 2 controls

8.7 Protection against malware
8.8 Management of technical vulnerabilities

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-24 Protect the Corporate Mail Service

AWS Well-Architected Security Pillar · 1 control

SEC06-BP05 Automate compute protection

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

CIS Controls v8 · 1 control

CIS-10.2 Configure Automatic Anti-Malware Signature Updates

CMMC 2.0 Level 1 · 1 control

SI.L1-3.14.4 Update Malicious Code Protection

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-TVM-04 Detection Updates

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-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

UK Cyber Essentials · 1 control

CE-MP.2 Anti-Malware Signatures Updated

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 CMMC 2.0 have you already done?

CMMC 2.0 SI.L2-3.14.4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 controls already carry evidence.

If you hold FedRAMP Moderate98.2% covered · 2 gaps If you hold NIST SP 800-171 Rev 394.5% covered · 6 gaps If you hold NIST SP 800-53 Rev 585.5% covered · 16 gaps If you hold ISO 27001:202279.1% covered · 23 gaps If you hold ISO 27002:202267.3% covered · 36 gaps If you hold CIS Controls v864.5% covered · 39 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. 1 were rejected on the FedRAMP Moderate pair alone.

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