PCI DSS 4.0
Req 5: Anti-Malware

PCI DSS 4.0 5.1.1: 5.1.1 Requirement 5 policies and procedures maintained and communicated

The organisation must hold security policies and operational procedures covering every activity named in Requirement 5 (protection against malware and phishing), and each of them must be: written down; reviewed and refreshed so they stay current; actually followed in practice; and communicated to everyone they affect. Documents should be revised soon after a relevant change in processes, technologies or business objectives, not only on a schedule. Applicability: applies to every entity in scope, with no special notes. Customized approach objective: people involved in Requirement 5 work know what is expected and follow it, so supporting activities are repeatable, consistent and in line with management intent.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

ISO 27701:2019 · 6 controls

NIST SP 800-53 Rev 5 · 5 controls

CIS Controls v8 · 4 controls

  • CIS-14.1 Establish and Maintain a Security Awareness Program
  • CIS-15.2 Establish and Maintain a Service Provider Management Policy
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-4.1 Establish and Maintain a Secure Configuration Process

ISO 22301:2019 · 4 controls

  • 5.2.2 Communicating the business continuity policy
  • 6.3 Planning changes to the business continuity management system
  • 7.5.3 Control of documented information
  • 8.4.1 General

ISO 27001:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.37 Documented operating procedures
  • 6.3 Information security awareness, education and training

ISO 27002:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.37 Documented operating procedures
  • 6.3 Information security awareness, education and training

ISO/IEC 42001:2023 · 3 controls

SOC 2 · 3 controls

  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission

Azure Security Benchmark · 1 control

  • ASBv3-GS-9 Define and implement endpoint security strategy

C5 (Germany) · 1 control

  • C5-OPS-04 Protection Against Malware - Concept

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

  • CCM-TVM-02 Malware Protection Policy and Procedures

FedRAMP High · 1 control

  • SI-1 Policy and Procedures

FedRAMP Moderate · 1 control

  • SI-1 Policy and Procedures

NIST SP 800-171 Rev 3 · 1 control

PCI 3DS Core Security Standard · 1 control

  • P1-4.1.1 P1-4.1.1 Malware-protection policy and procedures

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

MCP endpointAll PCI DSS 4.0 controls