PCI DSS 4.0
Req 5: Anti-Malware

PCI DSS 4.0 5.3.2: 5.3.2 Periodic and real-time scans or continuous behavioural analysis

The anti-malware solution or solutions must do at least one of the following: run periodic scans combined with real-time or active scans; or carry out continuous behavioural analysis of systems or processes. Scans should cover the whole file system, including disks, memory, start-up files and boot records, and commonly missed software such as mail servers, browsers and IM clients. Real-time scanning inspects a file whenever it is opened, closed, renamed or otherwise accessed. Applicability: applies to every entity in scope, with no special notes. Objective under the customized approach: malware is unable to finish executing.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 34 controls across 18 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 · 9 controls

  • CIS-10.1 Deploy and Maintain Anti-Malware Software
  • CIS-10.4 Configure Automatic Anti-Malware Scanning of Removable Media
  • 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.7 Deploy a Host-Based Intrusion Prevention Solution
  • 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 · 4 controls

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

C5 (Germany) · 2 controls

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

CMMC 2.0 · 2 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-05 Installation and execution of unauthorized software are prevented
  • ASD37-12 Antivirus software with heuristics (Very Good)

FedRAMP High · 1 control

  • SI-3 Malicious Code Protection

FedRAMP Moderate · 1 control

  • SI-3 Malicious Code Protection

HIPAA Security Rule · 1 control

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

SOC 2 · 1 control

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

UK Cyber Essentials · 1 control

  • CE-MP.3 Anti-Malware Scans Files on Access and Web Pages

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

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.

Query this from an agent

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