PCI DSS v4.x addresses vulnerability management primarily through Requirements 6 and 11. Requirement 6 requires organizations to identify new vulnerabilities using reputable industry sources, assign each a risk ranking, and install critical security patches within one month of release, with other patches applied within a timeframe the organization defines. It also requires secure development practices for bespoke and custom software and protection of public-facing web applications against known attacks. Requirement 11 requires internal vulnerability scanning at least once every three months, with high-risk and critical vulnerabilities resolved and rescans performed to confirm the fix; since March 2025, internal scans must be authenticated. External scans must be performed quarterly by a PCI SSC Approved Scanning Vendor (ASV), both internal and external scans are required after any significant change, and penetration testing must be performed at least annually.
Meeting these requirements consistently depends on defining scope accurately, since every system in or connected to the cardholder data environment is in scope, and on retaining documented evidence of each scan, risk ranking, remediation action, and rescan. Organizations that treat compliance as a quarterly exercise often struggle to produce passing results on time. Maintaining audit readiness year-round requires tracking findings to closure against defined SLAs and keeping records that demonstrate the process works as documented.
