PCI DSS 4.0 is now fully in effect, and its penetration testing requirements under Requirement 11.4 go further than the 3.2.1 baseline most teams built their program around — explicit segmentation testing at least every six months (11.4.5), penetration testing after any significant infrastructure or application change, and a documented methodology covering the full cardholder data environment.
We test against the 4.0 requirements as they actually apply now, not the version your last report was written for.
We scope testing to your cardholder data environment and the systems connected to it, covering network-layer and application-layer testing, segmentation validation between the CDE and the rest of your network, and testing after significant changes — exactly what 11.4 requires, reported in the format your QSA expects to review.
Why it matters
Merchants and service providers who have not revisited their testing scope since 3.2.1 often carry gaps 4.0 explicitly closes — segmentation testing that used to be encouraged is now mandated on a fixed cadence, and "significant change" testing catches infrastructure most legacy programs never retested. A QSA finding this at assessment time is a far more expensive conversation than catching it first.
What we test
- Cardholder data environment network penetration testing
- Application-layer penetration testing (CDE-connected systems)
- Segmentation testing (Requirement 11.4.5)
- Post-significant-change penetration testing (11.4.3)
- Authenticated internal vulnerability scanning support
- QSA-ready evidence pack preparation
Common vulnerabilities we uncover
- Segmentation controls that have never been independently tested
- Testing scope still based on the 3.2.1 baseline, not 4.0
- No testing triggered after significant infrastructure changes
- Cardholder data reachable from out-of-scope network segments
- Application-layer flaws in CDE-connected systems
- Evidence not structured for QSA review
Our methodology
- Scoping & rules of engagement. We agree objectives, targets and boundaries for your pci dss 4.0 penetration testing, so testing is safe, authorized and focused on what matters to your business.
- Reconnaissance & mapping. We enumerate the full attack surface in scope, building a complete picture before any exploitation begins.
- Manual exploitation. Our senior testers chain vulnerabilities by hand — going far beyond automated scanners — to prove real, demonstrable impact.
- Analysis & reporting. Every finding is triaged, risk-rated with CVSS and written up with a copy-paste reproduction and clear remediation.
- Remediation support & free retest. We support your team through the fixes and retest the remediated issues to confirm they are genuinely closed.
Tools & techniques
We test both the network layer and the application layer of your cardholder data environment, validate segmentation controls between the CDE and out-of-scope systems on the cadence 11.4.5 requires, and structure testing around any significant infrastructure or application change per 11.4.3, so your evidence trail matches what a QSA will ask for line by line.
When you need this engagement
- You are a merchant or service provider due for your annual PCI DSS assessment
- Your last penetration test scope predates the 4.0 requirements
- You have made significant infrastructure or application changes since your last test
- Your QSA has flagged missing segmentation testing evidence
- You are reducing PCI scope and need to validate the new segmentation boundary
What you receive
- Network & application-layer penetration test report
- Segmentation testing evidence (11.4.5)
- Post-change testing documentation
- QSA-ready evidence pack
- Prioritised remediation roadmap
- Free retest after remediation
What’s included in your report
Every pci dss 4.0 penetration testing engagement concludes with a comprehensive, board-ready report and a working session to walk your team through it. Your report includes:
- An executive summary with overall risk posture for non-technical stakeholders
- Detailed technical findings, each with a step-by-step, copy-paste reproduction
- CVSS v3.1 severity ratings and business-impact context for every issue
- Prioritized, actionable remediation guidance your engineers can apply directly
- A complimentary retest to confirm fixes and update finding status
- A formal attestation letter for customers, auditors and compliance programs
Standards & frameworks
PCI DSS v4.0.1
Requirement 11.4
Outcomes you can expect
After your pci dss 4.0 penetration testing, you will have clear, evidence-based visibility into your real security risk — not a scanner’s guesswork. You will know exactly which weaknesses an attacker could exploit, what the business impact would be, and the precise steps to fix them in priority order. Teams use our findings to close critical gaps, satisfy customer and regulator security requirements, and demonstrate due diligence to their board. With a complimentary retest included, you also get documented proof that the issues are genuinely resolved.
Engagement details & logistics
Every pci dss 4.0 penetration testing starts with a short, no-obligation scoping call to understand your goals, environment and constraints, followed by a fixed-price proposal and a clear statement of work. Most engagements are delivered fully remotely, with on-site work arranged where it genuinely adds value. Throughout testing we maintain an agreed communication cadence and escalate any critical, high-impact finding to you immediately rather than waiting for the final report. All work is performed under a signed NDA with strict data-handling controls, using safe, non-disruptive techniques and carefully coordinated rules of engagement to protect your production systems. On completion you receive your report and a walkthrough session, followed by a complimentary retest once your fixes are in place. Typical engagements are booked one to three weeks in advance, and urgent or pre-deadline testing can often be accommodated — just ask at hi@agentoffense.com.
Why organizations choose AgentOffense
Our pci dss 4.0 penetration testing is delivered by senior offensive-security engineers who test the way real attackers do — manually, creatively and with a relentless focus on proving genuine, demonstrable impact. Here is what sets our engagements apart:
- Manual, exploit-driven testing that chains vulnerabilities the way a real attacker would, going far beyond what automated scanners can find.
- Reproducible proof for every finding, with copy-paste reproduction steps your engineers can follow and independently verify.
- Honest severity calibration so you invest in fixing what genuinely matters and avoid wasting effort on false positives and noise.
- Clear, business-focused reporting that speaks to engineers and executives alike, tying every issue to real-world impact.
- A complimentary retest included, so you get documented proof that your fixes actually close the attack path.
- Responsible, collaborative delivery with a named point of contact and secure handling of all data throughout the engagement.
Explore related services
PCI DSS 4.0 Penetration Testing is frequently scoped alongside our other offensive-security services for broader coverage. Explore related engagements that complement it:
How much does PCI DSS 4.0 Penetration Testing cost?
Every pci dss 4.0 penetration testing is scoped and priced individually, so you pay for exactly the coverage you need — with no hidden extras. After a short, no-obligation scoping call we send a fixed-price quote, usually within one business day, with clear deliverables, a firm timeline and a complimentary retest included. The price of your pci dss 4.0 penetration testing depends on the size and complexity of the target and the depth of testing required, so you always know the cost up front before any work begins.
Get a fixed-price quote
Frequently asked questions
What changed in PCI DSS 4.0 penetration testing requirements?
Requirement 11.4 now explicitly mandates segmentation testing at least every six months, penetration testing after significant infrastructure or application changes, and a documented, risk-based methodology — going further than the 3.2.1 baseline most existing programs were built around.
How often do we need segmentation testing under 4.0?
At least every six months for service providers, and at least annually for merchants, under Requirement 11.4.5 — more frequently if your environment changes significantly.
Does every infrastructure change trigger a new test?
Only "significant" changes, but the definition is broader than most teams assume — we help you determine what counts and build a testing cadence that matches your actual change velocity.
Can this support our SOC 2 or ISO 27001 evidence too?
Yes, we structure findings so the same testing evidence can support multiple frameworks where the scope overlaps.