PCI DSS v4.x

Prove segmentation and penetration testing.
Continuously.

PCI DSS v4.x expects documented, qualified, independent testing on a schedule and after every significant change. SpartanX keeps that evidence current between assessments instead of once a year.

Segmentation testingInternal and externalDated evidence
The problem

What the mandate expects

PCI DSS v4.x, now in force, calls for a documented penetration testing methodology, with internal and external testing at least every 12 months and after any significant change (Req 11.4). Segmentation controls must be tested at least every 12 months, and every 6 months for service providers (11.4.5, 11.4.6).

The standard also requires regular internal and external vulnerability scans (11.3.1, 11.3.2). The tester must be qualified and organizationally independent, but need not be a QSA or ASV. The practical gap is time: a once-a-year test leaves most of the year without current proof that segmentation holds and that new changes were tested.

How it works

How SpartanX supports it

01

Internal and external testing

The same adversary runs against your external surface, and SpartanX Fabric runs it inside the perimeter, so both internal and external penetration testing stay current rather than landing once a year.

02

Segmentation testing on cadence

SpartanX Fabric exercises segmentation controls between CDE and out-of-scope networks, so you can show testing well inside the 12-month window, and the 6-month window service providers carry.

03

Scans plus validation

Continuous vulnerability scanning feeds the loop, and every exploitable issue is confirmed with a working exploit and proof of concept, which cuts the false positives a reviewer would otherwise wade through.

04

Test after every change

Because the loop runs continuously, a significant change is retested in days, with dated evidence that the change was assessed.

The outcome

What you can tell auditors and executives

Segmentation proven, not assumed

Show dated results that CDE segmentation holds, with a reproducible proof for any path that crossed.

Methodology on the record

Present a documented, repeatable testing methodology with internal and external coverage.

Change is covered

Demonstrate that significant changes were retested promptly, not deferred to the next annual cycle.
The honest line

SpartanX supports and streamlines your PCI DSS program and complements your independent assessor or QSA. It does not certify you or make you compliant on its own.

Internal and external penetration testing run continuously across the cardholder data environment and its surface.
SpartanX Fabric tests segmentation between in-scope and out-of-scope networks with reproducible proof.
Every exploitable finding ships with a working exploit and a reproducible proof of concept.

Keep PCI evidence current all year

See how continuous internal, external, and segmentation testing produces evidence your QSA can rely on.