PCI 3DS Core Security Standard P1-4.1.1: P1-4.1.1 Malware-protection policy and procedures

What else in your programme already covers this

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

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 Part 1 Requirement P1-4: Vulnerability management – PCI 3DS Core Security Standard

• P1-4.1.2 P1-4.1.2 Anti-malware controls active and maintained
• P1-4.2.1 P1-4.2.1 Vulnerability-management policy and procedures
• P1-4.2.2 P1-4.2.2 Quarterly internal and external vulnerability scans
• P1-4.2.3 P1-4.2.3 Scans run by qualified parties, external by an ASV
• P1-4.2.4 P1-4.2.4 Vulnerabilities ranked by criticality
• P1-4.2.5 P1-4.2.5 Annual penetration testing
• P1-4.2.6 P1-4.2.6 Penetration tests by qualified personnel
• P1-4.2.7 P1-4.2.7 High-risk findings fixed within a month, others promptly