Home
About Us
Blog
Pricing
Services
AI Penetration Testing
PCI DSS HIPAA Pentesting
Home
About Us
Blog
Pricing
Services
AI Penetration Testing
PCI DSS HIPAA Pentesting
More
  • Home
  • About Us
  • Blog
  • Pricing
  • Services
  • AI Penetration Testing
  • PCI DSS HIPAA Pentesting
  • Home
  • About Us
  • Blog
  • Pricing
  • Services
  • AI Penetration Testing
  • PCI DSS HIPAA Pentesting
Requirement 11.4 · Segmentation · Free retest

PCI DSS Penetration Testing

If you store, process or transmit cardholder data, PCI DSS requires penetration testing. Zero Day Security delivers the internal, external and segmentation testing Requirement 11.4 describes, with a report your QSA or acquirer can review and a free retest to verify fixes.

Book a Free Scoping Call

Who It's For

E-commerce Merchants

SAQ D & ROC Merchants
SAQ D & ROC Merchants

Merchants that host or control their own payment pages, or whose SAQ includes penetration testing requirements.

SAQ D & ROC Merchants

SAQ D & ROC Merchants
SAQ D & ROC Merchants

Retailers, hospitality groups and franchise operators with in-store payment networks completing SAQ D or a Report on Compliance.

Service Providers

SAQ D & ROC Merchants
Service Providers

Payment facilitators, gateways, fintech platforms, call centers and hosting providers that touch cardholder data on behalf of others.

What Gets Tested

External & Internal Network

Applications, APIs & Wireless
External & Internal Network

Every internet-facing system in or connected to the CDE, plus testing from inside the corporate network and the CDE for reach, escalation and movement.

Segmentation

Applications, APIs & Wireless
External & Internal Network

Confirming that out-of-scope networks truly can't reach the cardholder data environment, from each segment you claim is isolated.

View All Services

Applications, APIs & Wireless

Applications, APIs & Wireless
Applications, APIs & Wireless

Checkout flows, payment APIs and admin portals against the OWASP Top 10, and Wi-Fi at card-handling locations, including guest network isolation.

What Requirement 11.4 Calls For

11.4.1 to 11.4.3

11.4.5 & 11.4.6 Segmentation
11.4.1 to 11.4.3

A documented methodology plus internal and external testing at least every 12 months and after significant changes, by a qualified, independent tester.

11.4.4 Retesting

11.4.5 & 11.4.6 Segmentation
11.4.1 to 11.4.3

Exploitable vulnerabilities corrected and the corrections verified by repeat testing. The free retest provides exactly that verification.

See Pricing

11.4.5 & 11.4.6 Segmentation

11.4.5 & 11.4.6 Segmentation
11.4.5 & 11.4.6 Segmentation

Segmentation controls tested at least every 12 months, or every six months for service providers, and after any change to them.

PCI DSS Pentest FAQ

Questions about PCI DSS testing? Email info@zerodaysecurity.net or book a free scoping call and bring your network diagram.

Yes, if your validation includes Requirement 11.4. ASV scans satisfy the external vulnerability scanning in Requirement 11.3.2 and are automated. Requirement 11.4 is a separate control calling for manual internal and external penetration testing that tries to exploit weaknesses, at least every 12 months and after significant changes. Most assessors will ask for evidence of both, with dates, scope and remediation.


It depends on how you accept cards. SAQ D, for merchants and service providers, includes the full set of 11.4 requirements. Some shorter SAQs include only parts of it, and some, for fully outsourced payment pages, include none. Check the current SAQ for your channel, or ask your acquirer or QSA. The scoping call can help you confirm what applies before you buy testing you don't need.


PCI DSS leaves the definition to your organization, but typical examples are new internet-facing systems, changes to the CDE network, new payment applications or major version upgrades, a change of hosting or cloud provider, and changes to firewalls or segmentation controls. Document your definition. When a change qualifies, a targeted test of the affected systems is usually enough, rather than repeating the full annual engagement.


Every six months, under Requirement 11.4.6, and after any change to segmentation controls or methods. Merchants test segmentation at least once every 12 months under 11.4.5. Service providers can combine one segmentation test with the annual internal and external test and run a lighter segmentation-only check at the six-month point, which keeps the second test smaller and more focused.


It starts with a free scoping call to agree targets, test windows and rules of engagement, and you receive a fixed price in writing. Testing is manual and non-destructive, and critical findings are reported immediately. The report includes an executive summary, CVSS-scored findings with evidence and remediation steps, and a methodology section for auditors. Once you've fixed the findings, a free retest confirms what's closed.


Every test is performed by a CREST-certified tester who also holds CREST CPSA, OffSec OSCP, OSWA, OSWP and OSAI, plus the HTB Certified Offensive AI Expert (COAE). All are practical, exam-based credentials. The same tester handles your engagement from scoping to retest, and every engagement is fixed-price with a free retest included.


Scoping a PCI DSS Pentest?

Book a free scoping call. Tell us what you need tested and any deadline, and you'll get a clear fixed-price proposal.

Get Started

Copyright © 2026 Zero Day Security - All Rights Reserved.

  • Book a Free Scoping Call
  • Blog
  • Privacy Policy
  • Contact
  • FAQ
  • Healthcare Pentesting
  • SaaS Penetration Testing
  • Pentesting Denver
  • PCI DSS Penetration Test
  • SOC 2 Penetration Testing
  • Pentesting Boulder
  • Pentest Colorado Springs
  • Fintech Pentesting
  • Certifications

CREST CRT, OSCP, OSWA, OSWP, OSAI, COAE certified

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

DeclineAccept