Black Friday Our software, PenTest Project: Slate Enterprise at €53 instead of €173 per user a month, and Flint free for 12 months. Until 30 November. See the offer →
PenTest Hub logo

PCI DSS · Cardholder data environment

PCI DSS Segmentation Testing

Segmentation keeps your PCI DSS scope small, but only if it works. We test from every out-of-scope network to confirm your cardholder data environment really is isolated.

  • PCI DSS v4.0
  • Every out-of-scope segment
  • Evidence for your assessor
Sample results · Segmentation testSample
FAILOffice network can reach the payment databaseFile sharing allowed by a broad firewall rule
FAILGuest Wi-Fi routes to a CDE jump hostRemote desktop open
PASSDevelopment network isolated from the CDEAll ports filtered
PASSBackup network isolated from the CDEAll ports filtered
Every segment tested, with evidence for your assessorSample results

In one sentence

What is PCI segmentation testing?

PCI segmentation testing confirms that the controls separating your cardholder data environment (CDE) from the rest of your network work, by testing from each out-of-scope network whether the CDE can be reached.

If segmentation fails, every connected system falls into PCI DSS scope. PCI DSS v4.0 requires segmentation controls to be tested at least once every 12 months and after significant changes, and every six months for service providers.

What you get

  • Results for every network segment tested
  • Evidence your assessor can review
  • The exact rule or route behind each failure
  • Retesting after you fix it

Scope

What we test

Every route between your cardholder data environment and the rest of the network.

CDE boundary

Whether systems in the CDE can be reached from each out-of-scope network.

  • Reachability
  • Ports
  • Services

Firewall rules

Rules between segments, checked in practice rather than on paper.

  • Rules
  • Exceptions
  • Overly broad access

Routing and access lists

Routes, VLANs and access lists that could bypass the intended separation.

  • Routing
  • VLANs
  • ACLs

Connected-to systems

Systems that connect to the CDE, such as jump hosts and management tools, and how they are protected.

  • Jump hosts
  • Management
  • Monitoring

Approach

How a segmentation test runs

Systematic, repeatable and documented for your assessor.

Step 1

Map the segments

We agree the CDE and every out-of-scope network to test from.

Step 2

Test each segment

From each segment we test whether any system or service in the CDE is reachable.

Step 3

Evidence and fixes

Results per segment, the cause of each failure and a retest once it is fixed.

Engagement

How we work with you

  1. Scope online

    Describe what you need in Flint, our scoping platform. Answer only the questions that apply.

  2. Proposal, signed online

    Effort, price and the statement of work are built from your answers.

  3. Ready for day one

    Authorisation, test accounts and rules of engagement are agreed before testing starts.

  4. Senior-led testing

    Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.

  5. Report and retest

    Your report is ready in Slate, our client portal, within 48 hours of testing ending.

What you receive

Everything stays in one place, in your own client portal.

  • A report in Slate within 48 hours of testing ending
  • Every finding with evidence, a risk rating and a fix
  • An executive summary for leadership
  • Retests you can request finding by finding
  • Downloads as PDF or Excel
  • Evidence you can hand to your auditors

Standards

Standards

Aligned with PCI DSS segmentation testing requirements.

  • PCI DSS v4.0
  • PCI SSC guidance on scoping and segmentation

FAQ

Frequently asked questions

Can't find yours? Ask a senior tester and we'll reply directly.

How often does PCI DSS require segmentation testing?
At least once every 12 months and after significant changes to segmentation controls, and every six months for service providers, under PCI DSS v4.0.
Is segmentation testing part of a penetration test?
It is a specific test PCI DSS requires when you use segmentation to reduce scope. It can be done together with your internal penetration test or on its own.
Do you need to be on site?
Not always. We can test from each segment on site or through devices or virtual machines placed in each network.
What will our assessor receive?
A report with results for every segment tested, the method used and the evidence behind each result.
When will we receive the report?
Within 48 hours of testing ending, in Slate, our client portal.

Contact

Tell us what you need to test

A senior tester reads every message and replies directly.