PCI DSS Compliance
The Complete Guide to PCI DSS Requirement 11: Penetration Testing and Vulnerability Scanning
Everything you need to know about security testing for payment card compliance
If your organization stores, processes, or transmits credit card data, you’re required to comply with the Payment Card Industry Data Security Standard (PCI DSS). Among the twelve main requirements, Requirement 11—”Test security of systems and networks regularly”—is often the most misunderstood and frequently leads to compliance failures during QSA audits.
This comprehensive guide breaks down everything you need to know about PCI DSS security testing: what’s required, who needs to do it, how to scope it properly, and how to ensure you pass your next audit. Whether you’re new to PCI compliance or looking to improve your testing program, this article will help you understand the specific testing obligations under Requirement 11.
Understanding PCI DSS Requirement 11
Requirement 11 mandates that organizations regularly test their security systems and processes to identify vulnerabilities and weaknesses. This isn’t optional—it’s a core component of maintaining PCI compliance.
Requirement 11.1
Processes and mechanisms for regularly testing security of systems and networks
Requirement 11.2
Wireless access points are identified and monitored
Requirement 11.3
External and internal vulnerabilities are regularly identified, prioritized, and addressed
Requirement 11.4
External and internal penetration testing is regularly performed
Who Needs to Comply with PCI DSS?
Before diving into testing requirements, it’s important to understand whether PCI DSS applies to your organization and at what level. The card brands (Visa, Mastercard, American Express, Discover) categorize merchants and service providers into different levels based on transaction volume.
Merchant Levels:
Level 1 Merchants: Process over 6 million card transactions annually (across all channels). Must undergo annual on-site assessment by a Qualified Security Assessor (QSA), submit a Report on Compliance (ROC), and perform quarterly network scans by an Approved Scanning Vendor (ASV).
Level 2 Merchants: Process 1-6 million transactions annually. Must complete an annual Self-Assessment Questionnaire (SAQ), conduct quarterly ASV scans, and may be required to conduct penetration testing depending on their acquiring bank’s requirements.
Level 3 Merchants: Process 20,000-1 million e-commerce transactions annually. Must complete an annual SAQ and conduct quarterly ASV scans. Penetration testing requirements vary by acquirer.
Level 4 Merchants: Process fewer than 20,000 e-commerce transactions or less than 1 million total transactions annually. Must complete an annual SAQ and may be required to conduct ASV scans depending on their acquiring bank.
Service Providers: Any entity that stores, processes, or transmits cardholder data on behalf of other organizations. Service providers have their own level classifications, and those at higher levels face the same rigorous requirements as Level 1 merchants.
Important Note: Even if you're a Level 3 or Level 4 merchant, your acquiring bank can require more stringent testing. Always check with your acquirer about their specific requirements—many now mandate annual penetration testing regardless of merchant level.
Requirement 11.3: Vulnerability Scanning
Quarterly ASV Scans and Internal Vulnerability Assessments
Requirement 11.3 mandates regular vulnerability scanning to identify and address security weaknesses. This requirement has two distinct components: external scanning by an Approved Scanning Vendor (ASV) and internal vulnerability scanning.
External Vulnerability Scanning (11.3.1):
External scans must be performed at least quarterly and after any significant change to the network (such as new system installations, network topology changes, or firewall rule modifications). These scans must be conducted by a PCI SSC Approved Scanning Vendor (ASV).
ASV scans focus on your internet-facing infrastructure—everything visible to potential attackers from the outside. This includes:
– Web servers and application servers
– Firewall external interfaces
– DNS servers
– Mail servers
– Any other systems with public IP addresses in your cardholder data environment (CDE)
The ASV scan must achieve a “passing” result, meaning no vulnerabilities scoring 4.0 or higher on the Common Vulnerability Scoring System (CVSS). Any vulnerabilities at this level must be remediated and rescanned until you achieve a clean scan.
Internal Vulnerability Scanning (11.3.2):
Internal vulnerability scans must also be performed at least quarterly and after significant changes. Unlike external scans, internal scans can be performed by qualified internal staff or a third-party vendor—they don’t require an ASV.
Internal scans assess vulnerabilities within your network, including:
– Servers storing, processing, or transmitting cardholder data
– Databases containing card information
– Internal workstations and systems
– Network devices within the CDE
– Any systems that could impact the security of cardholder data
Internal scans should be authenticated scans (scans using credentials to log into systems) to identify missing patches, configuration weaknesses, and other vulnerabilities that wouldn’t be visible from an unauthenticated perspective.
ASV Scanning: What You Need to Know
Only Use Approved Vendors
You must use a PCI SSC-approved ASV. The list is available on the PCI Security Standards Council website. Using a non-approved vendor means your scans won’t count for compliance purposes, even if they’re technically sound.
Scan All External IPs
You must scan all external IP addresses in your CDE. This includes not just web servers, but also firewall interfaces, VPN concentrators, and any other system with a public IP that’s part of or connected to your cardholder data environment.
Achieve Passing Scans
A “passing” scan shows no vulnerabilities rated 4.0 or higher. If you have high-scoring vulnerabilities, you must remediate them and rescan. You can’t submit a failing scan and explain why vulnerabilities are acceptable—the scan must be clean.
Pro Tip: Schedule your ASV scans early in the quarter. If you discover vulnerabilities, you'll need time to patch, retest, and potentially rescan multiple times to achieve a passing result. Many organizations fail to maintain compliance simply because they wait until the last minute and can't remediate findings in time.
Requirement 11.4: Penetration Testing
The Most Comprehensive Testing Requirement
While vulnerability scanning identifies known weaknesses, penetration testing simulates real-world attacks to discover how vulnerabilities could be chained together and exploited. PCI DSS Requirement 11.4 mandates both external and internal penetration testing.
External Penetration Testing (11.4.1):
External penetration tests must be performed at least annually and after any significant infrastructure or application upgrade or modification. The test should attempt to exploit vulnerabilities from an external, untrusted network perspective—simulating what an internet-based attacker would attempt.
External penetration testing must include:
– Network-layer penetration tests to identify vulnerabilities in infrastructure
– Application-layer testing for all web applications in the CDE (including payment applications, customer portals, admin interfaces)
– Testing to exploit any vulnerabilities identified during scanning
– Attempts to access the CDE from the outside
Internal Penetration Testing (11.4.2):
Internal penetration tests simulate an attacker who has gained access to your internal network—either through compromising an employee workstation, physical access, or exploiting a vulnerability from the outside. Internal tests must be performed at least annually and after significant changes.
Internal penetration testing should include:
– Testing from inside the network perimeter
– Attempts to access the CDE from non-CDE networks (testing segmentation)
– Privilege escalation testing
– Lateral movement testing (can an attacker pivot from one system to another?)
– Testing whether an attacker on a general corporate network could reach cardholder data
Segmentation Testing (11.4.3):
If you use network segmentation to reduce your PCI scope (isolating the CDE from other networks), you must perform penetration testing specifically to validate that segmentation controls are effective. This testing proves that a compromised system on a non-CDE network cannot access the CDE.
Segmentation testing is crucial because many organizations rely on network segmentation to minimize their compliance scope. If segmentation fails, your entire network may be in scope for PCI compliance—dramatically increasing your compliance burden and cost.
What Makes a PCI DSS Penetration Test Different?
PCI DSS penetration testing isn’t just a generic security test. It has specific requirements:
Industry-Accepted Methodologies: Tests must follow industry-accepted penetration testing methodologies such as NIST SP 800-115, OWASP Testing Guide, or PTES (Penetration Testing Execution Standard).
Scope Coverage: Testing must cover the entire CDE perimeter and any critical systems. You can’t just test a subset of systems and call it compliant.
Exploitability Testing: Tests should include attempts to actually exploit identified vulnerabilities, not just scan for them.
Documented Results: The final report must document scope, methodology, findings, risk ratings, and recommendations. Your QSA will review this report during your assessment.
Who Can Perform Penetration Testing?
Unlike external vulnerability scanning (which requires an ASV), penetration testing can be performed by qualified internal resources or third-party penetration testers. The key word is “qualified.”
PCI DSS requires that penetration testers have:
– Organizational independence from the systems being tested
– Industry-recognized certifications (such as OSCP, CEH, GPEN) or equivalent experience
– Knowledge of current attack techniques and tools
– Understanding of the specific technologies in your CDE
Many QSAs scrutinize internal penetration testing more heavily than external testing, so using a qualified third-party pentester often smooths the audit process. Additionally, external perspectives often identify issues that internal teams might miss due to familiarity with the environment.
Scoping Your Cardholder Data Environment
One of the most critical aspects of PCI DSS compliance—and one that directly impacts your testing requirements—is properly scoping your Cardholder Data Environment (CDE). The CDE includes any system that stores, processes, or transmits cardholder data, plus any system that could impact the security of cardholder data.
What’s In Scope:
– System Components: Any server, application, database, or device that handles cardholder data
– Connected Systems: Systems that connect to or could affect the CDE (even if they don’t handle card data themselves)
– Segmentation Controls: Firewalls, VLANs, and other security controls that isolate the CDE
– Support Systems: DNS, NTP, authentication servers that service the CDE
What Can Be Out of Scope:
Systems can be excluded from PCI scope if:
– They’re completely isolated from the CDE with no network connectivity
– They’re segmented from the CDE and segmentation has been validated through testing
– They cannot impact the security of cardholder data in any way
Many organizations make the expensive mistake of not properly segmenting their environment, leading to massive PCI scope. If your point-of-sale systems are on the same network as your corporate laptops, guess what? Those laptops are now in scope for PCI compliance.
Cost Savings Through Segmentation: Proper network segmentation can dramatically reduce PCI compliance costs. A retailer with 50 stores might have 500 in-scope systems without segmentation, but only 50 payment terminals with proper segmentation. This impacts scanning costs, penetration testing costs, and general compliance overhead. Invest in segmentation early—it pays for itself.
Testing After Significant Changes
PCI DSS doesn’t just require testing on a fixed schedule—you must also test after “significant changes” to your environment. This is one of the most commonly overlooked requirements and frequently leads to compliance failures.
What Constitutes a Significant Change?
PCI DSS defines this broadly. Examples include:
– New system component installations
– Changes to network topology
– Firewall rule modifications
– Application upgrades or new application deployments
– Changes to wireless infrastructure
– Moving to a new data center or cloud provider
Essentially, any change that could impact the security of cardholder data should trigger testing. This doesn’t necessarily mean a full penetration test after every change—the testing should be commensurate with the change. A firewall rule modification might require verification scans of affected systems. A complete infrastructure migration requires comprehensive penetration testing.
Documenting Change-Driven Testing:
Your QSA will ask about changes during your assessment. You need documented evidence that:
– You have a change management process
– Security testing is part of that process
– Testing is performed after significant changes
– Results are reviewed before changes go into production
Many organizations implement a quarterly schedule for vulnerability scanning but forget to scan after changes. Then during the QSA audit, the assessor discovers a major infrastructure change from seven months ago that was never tested—instant compliance failure.
Common PCI DSS Testing Mistakes
After conducting hundreds of PCI DSS assessments, we see organizations make the same mistakes repeatedly:
1. Testing Too Late in the Compliance Cycle
Organizations wait until weeks before their assessment deadline to conduct penetration testing. Then they discover critical vulnerabilities that require significant remediation effort. By the time they remediate and retest, they’ve missed their deadline.
Solution: Conduct annual penetration testing at least 3-4 months before your assessment deadline. This provides buffer time for remediation and retesting.
2. Confusing Vulnerability Scanning with Penetration Testing
Some organizations think running Nessus or Qualys constitutes penetration testing. It doesn’t. Vulnerability scanning and penetration testing are different activities with different requirements under PCI DSS.
Solution: Ensure you’re conducting actual penetration tests (manual testing with exploitation attempts) for Requirement 11.4, not just automated vulnerability scans.
3. Incomplete Scope Coverage
Testing only web applications but ignoring network infrastructure, or testing external systems but not internal systems. PCI DSS requires comprehensive testing of both network and application layers, external and internal.
Solution: Work with your QSA before testing begins to document exactly what’s in scope. Ensure your testing covers all in-scope systems and clearly documents the scope in your report.
4. Failing to Retest After Remediation
Organizations remediate vulnerabilities but never verify the fixes worked. Then during the QSA assessment, the auditor discovers the vulnerabilities still exist or the fixes introduced new issues.
Solution: Always retest after remediation. Most penetration testing providers include retesting as part of the engagement—use it.
5. Not Testing Segmentation
Organizations rely on network segmentation to limit PCI scope but never actually test whether segmentation controls work. During the assessment, they can’t prove segmentation is effective, causing their entire network to come into scope.
Solution: Specifically test segmentation controls during your internal penetration test. Document attempts to access the CDE from non-CDE networks and show they failed.
6. Inadequate Testing Documentation
Reports lack required detail about methodology, tools used, vulnerabilities discovered, or risk ratings. The QSA can’t validate that testing meets PCI requirements without proper documentation.
Solution: Ensure your penetration test report includes: scope definition, methodology reference (NIST 800-115, OWASP, etc.), testing timeline, detailed findings with CVSS scores, exploitation evidence, risk ratings, and remediation recommendations.
What Your QSA Will Look For
During your PCI assessment, your QSA will review your security testing documentation carefully. Here’s what they’ll examine:
For Vulnerability Scanning:
– Evidence of quarterly external ASV scans from a PCI-approved vendor
– “Passing” scan results (no vulnerabilities rated 4.0 or higher)
– Evidence that all external IP addresses in the CDE were scanned
– Quarterly internal vulnerability scans
– Evidence of rescanning after significant changes
– Documented process for vulnerability remediation
– Evidence that high and critical vulnerabilities were addressed promptly
For Penetration Testing:
– Comprehensive penetration test report from the past 12 months
– Evidence of both external and internal testing
– Testing scope that covers the entire CDE
– Industry-accepted methodology (NIST 800-115, OWASP, PTES, etc.)
– Documentation of segmentation testing (if segmentation is used for scoping)
– Evidence that vulnerabilities discovered during testing were remediated
– Qualifications of the individuals who performed testing
– Evidence of testing after significant changes
Process Documentation:
– Documented testing schedule
– Change management procedures that include security testing
– Vulnerability management procedures
– Evidence that testing results are reviewed by appropriate personnel
– Process for tracking remediation efforts
Your QSA isn’t just checking that you had tests done—they’re validating that you have a systematic, documented approach to security testing that’s actually working to identify and address vulnerabilities.
Annual Testing Timeline: A Practical Example
Here’s how a well-run PCI compliance program schedules testing throughout the year:
Q1 (Jan-Mar)
January: External ASV scan, Internal vulnerability scan
February: Review and remediate findings
March: Rescan to verify remediation
Q2 (Apr-Jun)
April: External ASV scan, Internal vulnerability scan, Annual external penetration test
May: Annual internal penetration test, Segmentation testing
June: Remediate findings, Retest critical vulnerabilities
Q3 (Jul-Sep)
July: External ASV scan, Internal vulnerability scan
August: Review and remediate findings
September: Rescan to verify remediation, Prepare documentation for QSA
Q4 (Oct-Dec)
October: External ASV scan, Internal vulnerability scan, QSA assessment begins
November: Complete QSA assessment
December: Final remediation of any findings, Submit compliance documentation
Key Strategy: Notice that penetration testing happens in Q2, giving you months to remediate and prepare for the Q4 assessment. Organizations that test in Q4 right before their assessment frequently fail due to insufficient remediation time.
Beyond Compliance: The Security Benefits
While this guide focuses on meeting PCI DSS compliance requirements, it’s worth noting that regular security testing provides benefits beyond avoiding audit findings:
Breach Prevention: Verizon’s Data Breach Investigations Report consistently shows that the majority of breaches exploit known vulnerabilities. Regular testing helps you find and fix these vulnerabilities before attackers do.
Reduced Breach Costs: The average cost of a payment card breach is $3.86 million according to IBM’s Cost of a Data Breach Report. Even a single prevented breach pays for years of security testing.
Insurance Benefits: Many cyber insurance policies require evidence of regular penetration testing. Some insurers offer premium discounts for organizations with mature testing programs.
Customer Trust: Being able to demonstrate rigorous security testing builds trust with customers and business partners. Many B2B customers now ask for evidence of security testing before signing contracts.
Improved Security Posture: Organizations that test regularly don’t just check a compliance box—they continuously improve their security. Each testing cycle reveals not just technical vulnerabilities but also process gaps and security control weaknesses.
Reduced Scope Over Time: Effective segmentation testing can help you continuously refine and reduce your PCI scope, lowering long-term compliance costs.
Choosing a PCI DSS Testing Provider
Not all security testing providers are equal, and choosing the wrong one can lead to compliance failures even if testing technically occurred. Here’s what to look for:
PCI DSS Expertise: Ensure the provider has specific experience with PCI DSS testing requirements. Generic penetration testers may not understand the specific scoping, methodology, and documentation requirements that QSAs expect.
ASV Certification: For external vulnerability scanning, you must use a PCI-approved ASV. Check the PCI Security Standards Council website for the current list of approved vendors.
Qualified Testers: Look for penetration testers with industry certifications (OSCP, GPEN, CEH) and demonstrable experience testing payment environments. Ask about their specific PCI testing experience.
Comprehensive Reporting: Ask to see sample reports. They should include detailed methodology documentation, comprehensive findings with CVSS scores, exploitation evidence, risk ratings, and clear remediation guidance. The report format should explicitly address PCI DSS requirements.
Remediation Support: Good testing providers don’t just hand you a report and disappear. Look for providers who offer remediation consultation calls, retesting to verify fixes, and support during your QSA assessment if questions arise about the testing.
Understanding of Your Industry: Payment environments vary significantly between retail, e-commerce, hospitality, and other sectors. A provider with experience in your specific industry will better understand your unique challenges and requirements.
Get PCI DSS Compliant Testing
Graynode Security specializes in PCI DSS Requirement 11 testing. We provide ASV-compliant external vulnerability scanning, internal vulnerability assessments, and comprehensive penetration testing designed specifically to meet PCI DSS requirements.
Our reports explicitly map findings to PCI DSS requirements, include all documentation your QSA expects, and provide clear remediation guidance. We’ve helped hundreds of organizations pass their PCI assessments—from small e-commerce merchants to multi-location retail chains.
Whether you need quarterly ASV scans, annual penetration testing, or help scoping your entire PCI compliance program, we deliver testing that satisfies auditors and actually improves your security.
