PCI DSS 4.0
Req 5: Anti-Malware

PCI DSS 4.0 5.3.1: 5.3.1 Anti-malware kept current through automatic updates

The anti-malware solution or solutions must be kept up to date by means of automatic updates, covering signatures, security updates, threat analysis engines and any other protections the solution relies on. Updates should come from a trusted source as soon as they are available; they may be pulled first to a central location, for example for testing, before rollout to individual components. Applicability: applies to every entity in scope, with no special notes. Objective under the customized approach: anti-malware mechanisms are able to detect and deal with the newest malware threats.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 39 controls across 21 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 · 6 controls

  • CIS-10.1 Deploy and Maintain Anti-Malware Software
  • CIS-10.2 Configure Automatic Anti-Malware Signature Updates
  • CIS-10.6 Centrally Manage Anti-Malware Software
  • CIS-12.1 Ensure Network Infrastructure is Up-to-Date
  • CIS-14.7 Train Workforce on How to Identify and Report if Their Enterprise Assets are Missing Security Updates
  • CIS-9.7 Deploy and Maintain Email Server Anti-Malware Protections

FedRAMP High · 5 controls

  • CM-2(2) Automation Support for Accuracy and Currency
  • CM-8(1) Updates During Installation and Removal
  • SI-2(2) Automated Flaw Remediation Status
  • SI-3 Malicious Code Protection
  • SI-8(2) Spam Protection | Automatic Updates (SI-8(2))

FedRAMP Moderate · 5 controls

  • CM-2(2) Automation Support for Accuracy and Currency
  • CM-8(1) Updates During Installation and Removal
  • SI-2(2) Automated Flaw Remediation Status
  • SI-3 Malicious Code Protection
  • SI-8(2) Spam Protection | Automatic Updates (SI-8(2))

CMMC 2.0 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

ISO 27001:2022 · 2 controls

  • 8.7 Protection against malware
  • 8.8 Management of technical vulnerabilities

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-16 Antivirus software with signatures (Limited)

AWS Well-Architected Security Pillar · 1 control

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

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

Azure Security Benchmark · 1 control

  • ASBv3-ES-3 Ensure anti-malware software and signatures are updated

C5 (Germany) · 1 control

  • C5-OPS-05 Protection Against Malware - Implementation

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

HIPAA Security Rule · 1 control

ISO 27002:2022 · 1 control

  • 8.7 Protection against malware

ISO 27701:2019 · 1 control

  • 6.9.2 Protection from malware

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

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-66 Rev 2 · 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.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.

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.3.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 39 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls