CMMC 2.0
System and Information Integrity

CMMC 2.0 SI.L2-3.14.2: Malicious Code Protection

Provide malicious code protection at the points in the system where such code is likely to enter or execute.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 49 controls across 27 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 · 7 controls

  • CIS-10.1 Deploy and Maintain Anti-Malware Software
  • CIS-10.2 Configure Automatic Anti-Malware Signature Updates
  • CIS-10.5 Enable Anti-Exploitation Features
  • CIS-10.6 Centrally Manage Anti-Malware Software
  • CIS-10.7 Use Behavior-Based Anti-Malware Software
  • CIS-9.6 Block Unnecessary File Types
  • CIS-9.7 Deploy and Maintain Email Server Anti-Malware Protections
  • ASD37-05 Automated dynamic analysis of email and web content (Excellent)
  • ASD37-06 Email content filtering (Excellent)
  • ASD37-07 Web content filtering (Excellent)
  • ASD37-12 Antivirus software with heuristics (Very Good)
  • ASD37-16 Antivirus software with signatures (Limited)
  • ASD37-29 Host-based IDS/IPS (Very Good)

PCI DSS 4.0 · 5 controls

  • 5.4.1 5.4.1 Mechanisms detect and protect against phishing
  • 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
  • 5.3.2 5.3.2 Periodic and real-time scans or continuous behavioural analysis
  • ASBv3-GS-9 Define and implement endpoint security strategy
  • ES-1 Use Endpoint Detection and Response (EDR)
  • ES-2 Use modern anti-malware software

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

C5 (Germany) · 2 controls

  • C5-OPS-04 Protection Against Malware - Concept
  • C5-OPS-05 Protection Against Malware - Implementation

HIPAA Security Rule · 2 controls

  • E8-MACRO-ML1 Configure Microsoft Office Macro Settings (ML1)
  • AUCDR-IS-5 Limit, prevent, detect and remove malware

CMMC 2.0 Level 1 · 1 control

FedRAMP High · 1 control

  • SI-3 Malicious Code Protection

FedRAMP Moderate · 1 control

  • SI-3 Malicious Code Protection

ISO 27001:2022 · 1 control

  • 8.7 Protection against malware

ISO 27002:2022 · 1 control

  • 8.7 Protection against malware

ISO 27701:2019 · 1 control

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

NIST SP 800-172 · 1 control

  • 3.13.3e Confuse and Mislead Adversaries

NIST SP 800-218 · 1 control

SOC 2 · 1 control

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

UK Cyber Essentials · 1 control

  • CE-MP.1 Anti-Malware Software Deployed

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.

Other controls in System and Information Integrity

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 SI.L2-3.14.2 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.

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.

Query this from an agent

The graph holds this control, the 49 it maps to, and the evidence behind each claim, over MCP and REST.