PCI DSS penetration testing (requirement 11.4)

What requirement 11.4 asks for, how often, and what counts as significant change.

A card being tapped on a payment terminal

What 11.4 covers

PCI DSS v4.0.1 requirement 11.4 covers penetration testing. In summary, it asks entities in scope to:

  • Define and follow a penetration testing method based on industry-accepted approaches.
  • Test internally and externally at least once every 12 months and after significant infrastructure or application changes.
  • Fix exploitable vulnerabilities and repeat the test to verify the fixes.
  • Test segmentation controls, if segmentation is used to reduce scope. Service providers test segmentation more often.

Significant change

The standard leaves it to each entity to define significant change in its own risk assessment. A new payment flow, a new network segment or a major upgrade to systems in scope usually qualifies. Agree the definition with your QSA.

What we provide

We perform the internal, external and segmentation tests, retest your fixes, and write a report your QSA can use. We are not a QSA and do not perform the PCI DSS assessment itself.

Sources

General guidance, not legal, audit or compliance advice. Confirm requirements with your auditor or assessor.

Need this done?

Tell us what needs testing and when. We reply within 1 business day.

Request a proposal
Ready to test?

Tell us what needs testing and by when.

You receive a written proposal with scope, method, timeline and a fixed price. We reply within 1 business day.