PCI DSS v4.0.1 requires internal and external penetration testing at least once every 12 months and after any significant change to your environment (Requirements 11.4.2 and 11.4.3). If you rely on segmentation to shrink your cardholder data environment, you also have to prove it works (11.4.5), every six months if you are a service provider (11.4.6).
Coastline tests your cardholder data environment the way an attacker would, then gives you a report you can hand straight to your QSA.
We follow a documented, industry-accepted methodology that covers the CDE perimeter and critical systems at both the network and application layers, as Requirement 11.4.1 asks. Every PCI engagement includes:
We test your internet-facing systems and your internal network, looking for the paths an attacker would use to reach cardholder data.
We confirm that out-of-scope networks truly cannot reach the CDE, so your scope reduction holds up under review.
Payment pages, web applications and APIs that touch card data are tested for injection, authentication and access control flaws.
Testing is done by qualified, organizationally independent testers, which PCI DSS requires whether you use an internal team or an outside firm.
A report that documents scope, methodology, every exploitable vulnerability with evidence, and clear steps to fix it. Once you have remediated, we retest so you can show the issues are closed (Requirement 11.4.4).
Not sure how often you need to test? See our guide to penetration testing frequency by framework, or start with a free AI external scan.