The PCI Security Standards Council used to release new versions of its Data Security Standard every three years, so it came as a surprise in 2015 when PCI DSS version 3.1 was released just two years after the release of 3.0 in November 2013. PCI DSS 3.1 formally replaced 3.0 on 30 June 2015.
Why the sudden release? The main reason was believed to be major security flaws such as BEAST and POODLE in the Secure Sockets Layer protocol and the early version of its successor, Transport Layer Security (TLS).
With the release of 3.1, SSL and early versions of TLS were prohibited, with the final migration deadline later set at 30 June 2018, and security penetration testing became mandatory rather than an option. Today, the current version of the standard is PCI DSS v4.0.1, published in June 2024, and penetration testing sits under Requirement 11.4.
Requirement 11.4.1 of PCI DSS v4.0.1 says a penetration testing methodology must be defined, documented and implemented, and must include:
Requirements relating to penetration testing that were considered as “best practices” in earlier versions became compulsory with PCI DSS 3.x. In simple words, without meeting these requirements, you cannot achieve PCI compliance.
Although penetration testing has always been a part of PCI DSS, what changed in version 3.1 was how it was mandated, and PCI DSS v4.0.1 keeps the same approach. The standard directs the inclusion of some key provisions to penetration testing, but does not specifically define what to do and how to meet those provisions.
The bottom line of this requirement is that your penetration testing methodology should be in a written form and you must use a qualified internal resource or a penetration testing firm to carry out the tests according to the methodology and requirements of PCI DSS. The tester must be organisationally independent, but does not need to be a QSA or an Approved Scanning Vendor. Penetration testing should not only be internal and external, carried out at least once every 12 months and after any significant change, but should also validate network segmentation for reducing scope and provide entire coverage of your cardholder data environment. Exploitable vulnerabilities that the tests find must be corrected and the testing repeated to verify the fixes.
So what’s the best way to comply with this requirement? PCI DSS does not specify which particular methodology you should use but it’s obvious that it wants a robust methodology. You can use NIST SP 800-115 as a reference to get an idea of what is really required. You can also try publications by SANS, for instance, “Conducting a Penetration Test on an Organization”. The PCI SSC’s own Penetration Testing Guidance information supplement (version 1.1, September 2017) is also useful, although it uses the older Requirement 11.3 numbering. That being said, when choosing a penetration testing firm to carry out the penetration test for you, choose a firm that has developed its own methodology and a reliable one too. You should make sure that whichever methodology for penetration testing you adopt, it must be detailed, easily examinable and justified.
What makes an effective penetration testing methodology?
Penetration testing done for PCI clients is often low budget and a bare-minimum process, mostly done as a vulnerability scan. For instance, if a compromise is detected in a missing patch, it is not the missing patch that is the vulnerability, but rather the process that failed to apply the patch to the target. The focus of the penetration testing process should be to discover faults in processes and procedures, and find the missing links with evidence to prove your findings.
As a general rule, a good methodology should include:
Segmentation of data within the cardholder data environment must also be a part of security penetration testing. In other words, penetration testing should test that the “ring fencing” that is supposed to be in place is actually in place. This is important because you actually test that the segmentation controls are working, rather than only assuming that they are!
It’s necessary to test access to cardholder data from each network that comes under the umbrella of the merchant. This is to prove to the Qualified Security Assessor (QSA) that each control is in place and functioning correctly. It helps ensure that cardholder data is safe from not only external threats but internal ones as well. Another segmentation area that is quite often overlooked is penetration testing within the CDE; this needs to be taken care of too. PCI DSS v4.0.1 requires segmentation controls to be tested at least once every 12 months and after any changes to them, and at least once every six months for service providers.
All businesses must consider and review the threats and vulnerabilities encountered during the last twelve months. This will require penetration testers to consider often-ignored threats like social engineering – such as password hacking or phishing scams – that have a high rate of success. The goal of this requirement is to provide a real-life scenario and test the system against it. This helps you analyse your security measures and flaw detection capability in case of a real attack.
If you’re a small merchant and thinking this probably does not apply to you, you may be wrong. Small merchants relying on Self-Assessment Questionnaires (SAQ) to validate PCI DSS compliance may also need to comply with Requirement 11.4. SAQ A-EP merchants need a penetration testing methodology, external penetration testing and remediation of what it finds; SAQ C and SAQ A-EP merchants that use segmentation must penetration test it; and SAQ D merchants must meet the full requirement.
All in all, we think it’s a good thing, and hope that this mandatory requirement of security penetration testing and implementation of a methodology for penetration testing will result in fewer cardholder data compromises, more secure networks and fewer breaches and frauds.
Is your business looking to get PCI DSS compliant? StickmanCyber’s PCI DSS compliance service deploys a 5-step methodology to help you build trust with your customers and secure your card transactions with PCI DSS compliance. Book a free consultation to talk to one of our experts.
No. Vulnerability scans fall under Requirement 11.3 and are automated checks for known weaknesses, run at least once every three months. Penetration tests fall under Requirement 11.4 and involve a tester actively trying to exploit weaknesses, following a documented methodology. PCI DSS treats them as separate requirements, so one can’t replace the other.
PCI DSS v4.0.1 allows either a qualified internal resource or a qualified external third party to perform the tests, as long as the tester is organisationally independent of the systems being tested. The tester does not need to be a QSA or an Approved Scanning Vendor, but they should have the skills and experience to follow your documented methodology.
Requirement 11.4.1 asks for penetration testing results and remediation activity results to be kept for at least 12 months. Keeping them lets your assessor see what was tested, what was found and how it was fixed, and helps you compare results from one test to the next.
Under Requirement 11.4.4, exploitable vulnerabilities and security weaknesses found during testing must be corrected in line with your assessment of the risk they pose. The penetration test must then be repeated to verify that the corrections work.
Yes. Since 31 March 2025, Requirement 11.4.7 has required multi-tenant service providers, such as shared hosting or cloud providers, to support their customers’ external penetration testing. They can do this by giving customers evidence of comparable testing or by providing prompt access so customers can carry out their own tests.