Standards · PCI DSS · Version 4.0.1
PCI DSS, and howto have less of it.
The Payment Card Industry Data Security Standard applies to every organisation that stores, processes or transmits card data. The most useful thing most merchants can do is reduce how much of their estate that describes. This page covers what the standard asks for, with the detail on testing and monitoring, where we come in.
Version 4.0.1Twelve requirementsAnnual penetration testDaily log reviewChecked 21 November 2026
A contractual standard, enforced through your acquiring bank.
PCI DSS is written by the PCI Security Standards Council, which the card brands founded, and it binds you through your agreement with the bank or payment provider that processes your card transactions. How you demonstrate compliance depends on how many transactions you handle: larger merchants and service providers are assessed by a Qualified Security Assessor, and smaller ones complete a self-assessment questionnaire. Version 4.0.1 is the current edition, and the requirements that version 4 introduced with a later start date have all been mandatory since 31 March 2025.
- Written by
- The PCI Security Standards Council
- Current edition
- Version 4.0.1
- Applies to
- Anyone who stores, processes or transmits card data, and their service providers
- Shown by
- A self-assessment questionnaire, or an assessment by a Qualified Security Assessor
- Enforced through
- Your acquiring bank or payment provider
Testing and monitoring
What the standard asks for, where we come in
Penetration testing
External and internal penetration tests at least once every twelve months and after any significant change, with exploitable findings corrected and retested.
Segmentation testing
If you rely on network segmentation to keep systems out of scope, tests that it works: every twelve months for merchants and every six for service providers.
Vulnerability scanning
Internal and external scans at least once every three months, the external ones by an Approved Scanning Vendor.
Logging and review
Audit logs for every system in scope, reviewed at least daily using automated mechanisms, and kept for at least twelve months.
Payment page integrity
An inventory of the scripts on your payment pages, and a way to detect unauthorised changes to them.
Incident response
A plan that is tested at least once a year, with people available to respond at any hour.
Scope
The cheapest control is a smaller scope
Every system that touches card data, and every system that can reach one that does, is in scope. Most of the cost of PCI DSS follows from that sentence, and so does the best way to reduce it.
A merchant who sends customers to a payment provider's hosted page, or uses point-to-point encrypted terminals, keeps card numbers out of its own systems almost entirely and answers a much shorter questionnaire. A merchant who takes card numbers on its own web page, stores them, or lets them cross the office network has a large scope and a long list.
Before paying for testing and monitoring across a wide scope, ask whether the scope can be made smaller. Where it cannot, segmentation is the next best thing, and the standard requires you to prove that it works. That is a penetration tester's job, and we would rather test a small, well-fenced environment for you than a sprawling one.
The standard itself is available free from the PCI Security Standards Council.
How we help
What we do towards it
- _01Penetration and segmentation testingExternal and internal testing to requirement 11.4 by CREST-certified testers, at £950 + VAT a day with the retest included.Test
- _02SOC365Log collection, daily automated review and alerting for the systems in scope, with the records an assessor asks for.Detect
- _03Scoping and gap analysisWorking out what is in scope, how to make it smaller, and what stands between you and a clean assessment.Consulting
- _04Incident response planningA plan and an annual test of it, as requirement 12.10 asks.Consulting
Questions
Questions about PCI DSS
How often do we need a penetration test for PCI DSS?
At least once every twelve months, and after any significant change to the environment. Both external and internal tests are required, and findings have to be fixed and retested.
Is a vulnerability scan enough?
No. The standard requires both: scans every three months, and a penetration test every year. They are separate requirements because they find different things.
Who carries out the formal assessment?
A Qualified Security Assessor for larger merchants and service providers, or you yourselves, by self-assessment questionnaire, if your acquirer permits it. Our part is the testing, monitoring and preparation that the assessment looks for.
What does a PCI DSS penetration test cost?
The same as any other test: £950 + VAT a day, with the days set by the size of the environment in scope. That is one more reason to keep the scope small. The cost guide has worked examples.
Start a conversation
Start by making the scope smaller.
Thirty minutes on where card data goes in your estate and what would have to be tested.