PCI Requirement 11.4 – Use Intrusion-Detection and/or Intrusion-Prevention Techniques
PCI v4.0 - 11.4.5 & 11.4.6: Test the Effectiveness of Segmentation Controls Regularly
PCI Readiness Series: Requirement 11
PCI v4.0 - 11.4.4: Correct Vulnerabilities Found in Penetration Testing
PCI v4.0 - 11.4.1: Define, Document, and Implement a Penetration Testing Methodology
PCI v4.0 - 11.4.7: Multi-Tenant Service Providers Support Customer for External Penetration Testing
PCI Requirement 11 - Regularly Test Security Systems & Processes
PCI v4.0 - 11.4.2: Regularly Perform Internal Penetration Testing
PCI Requirement 11.3 – Implement a Methodology for Penetration Testing
PCI v4.0 - 11.4.3: Regularly Perform External Penetration Testing
PCI Requirement 11.6 – Ensure Security Policies for Security Monitoring are Documented
PCI Requirement 11.2.2 – Perform Quarterly External Vulnerability Scans
PCI Requirement 11.3.4.1 – Confirm PCI DSS Scope by Performing Penetration Testing on Segmentation
PCI Requirement 10.4.1 – Critical Systems Have the Correct and Consistent Time
PCI Requirement 10.7 – Retain Audit Trail History for at Least One Year, with Three Months Available
PCI Requirement 11.3.4 – Perform Penetration Tests if Segmentation is Used
Six crucial SIEM functions for complying with the PCI DSS
PCI Requirement 11.2 – Quarterly Internal & External Vulnerability Scans
PCI Requirement 11.2.3 – Perform Internal and External Scans and Rescans as Needed
PCI Requirement 12.1 & 12.1.1 – Establish, Publish, Maintain, and Disseminate a Security Policy
No waiting, no wondering: Streamline your PCI pentesting process with Horizon3.ai
PCI Requirement 8.8 – Ensure Policies & Procedures for Authentication are Documented
PCI Requirement 10.5.3 – Promptly Back Up Audit Trail Files to a Centralized Log Server
PCI Requirement 8.2.5 – New Passwords Can’t Be the Same as Any of the Last Four Passwords Used
