PCI DSS 4.0
Req 5: Anti-Malware

PCI DSS 4.0 5.2.1: 5.2.1 Anti-malware deployed on all system components

An anti-malware solution (one or more) must be installed on every system component, with the only exception being components that the periodic evaluations under Requirement 5.2.3 have concluded are not at risk from malware. A component counts as affected by malware when real-world active exploits exist for it, not merely theoretical ones. Applicability: applies to every entity in scope, with no special notes. Customized approach objective: automated mechanisms stop systems from turning into a route for malware attacks.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 73 controls across 24 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 · 11 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
  • CIS-13.5 Manage Access Control for Remote Assets
  • CIS-13.7 Deploy a Host-Based Intrusion Prevention Solution
  • CIS-16.5 Use Up-to-Date and Trusted Third-Party Software Components
  • CIS-2.2 Ensure Authorized Software is Currently Supported
  • CIS-2.3 Address Unauthorized Software
  • CIS-9.6 Block Unnecessary File Types
  • CIS-9.7 Deploy and Maintain Email Server Anti-Malware Protections

NIST SP 800-53 Rev 5 · 9 controls

FedRAMP High · 7 controls

  • CM-7(2) Prevent Program Execution
  • CM-7(5) Authorized Software Allow-by-Exception
  • MA-3(2) Maintenance Tools | Inspect Media (MA-3(2))
  • MP-7 Media Use
  • SA-22 Unsupported System Components (SA-22)
  • SI-3 Malicious Code Protection
  • SI-4(23) System Monitoring | Host-based Devices (SI-4(23))

FedRAMP Moderate · 7 controls

  • CM-7(2) Prevent Program Execution
  • CM-7(5) Authorized Software Allow-by-Exception
  • MA-3(2) Maintenance Tools | Inspect Media (MA-3(2))
  • MP-7 Media Use
  • SA-22 Unsupported System Components (SA-22)
  • SI-3 Malicious Code Protection
  • SI-4(23) System Monitoring | Host-based Devices (SI-4(23))

CMMC 2.0 · 6 controls

ASD Strategies to Mitigate Cyber Security Incidents · 5 controls

  • ASD37-01 Application control (Essential)
  • ASD37-06 Email content filtering (Excellent)
  • ASD37-12 Antivirus software with heuristics (Very Good)
  • ASD37-16 Antivirus software with signatures (Limited)
  • ASD37-30 Endpoint detection and response (Very Good)

ISO 27001:2022 · 4 controls

  • 8.1 User end point devices
  • 8.12 Data leakage prevention
  • 8.19 Installation of software on operational systems
  • 8.7 Protection against malware

ISO 27701:2019 · 4 controls

  • 6.3.2 Mobile devices and teleworking
  • 6.9 Operations security
  • 6.9.2 Protection from malware
  • 6.9.5 Control of operational software

NIST Cybersecurity Framework 2.0 · 3 controls

  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk
  • NIST-CSF-PR.PS-05 Installation and execution of unauthorized software are prevented

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

ISO 27002:2022 · 2 controls

  • 8.12 Data leakage prevention
  • 8.7 Protection against malware

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

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

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

Azure Security Benchmark · 1 control

  • ES-2 Use modern anti-malware software

C5 (Germany) · 1 control

  • C5-OPS-05 Protection Against Malware - Implementation

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

HIPAA Security Rule · 1 control

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-172 · 1 control

  • 3.4.2e Automated Detection and Remediation of Unauthorized Software

NIST SP 800-66 Rev 2 · 1 control

PCI 3DS Core Security Standard · 1 control

  • P1-4.1.2 P1-4.1.2 Anti-malware controls active and maintained

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 Req 5: Anti-Malware

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 5.2.1 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.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 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. 415 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll PCI DSS 4.0 controls