Skip to main content
PCI DSS v4.0.1 · Payment security

PCI DSS compliance with Sumrite that keeps you taking card payments.

Card brands and acquirers expect proof that your cardholder environment holds up. Sumrite delivers gap analysis, penetration and segmentation testing, and retest evidence mapped to the requirements, so reviews move forward without surprises.

12
principal requirements in PCI DSS
6
control objectives they are grouped under
12
months, the maximum gap between penetration tests (and after major changes)
v4.0.1
the current version; future-dated v4.0 requirements became mandatory in March 2025
The detail

What PCI DSS actually is

The Payment Card Industry Data Security Standard is maintained by the PCI Security Standards Council and enforced through the card brands and acquiring banks. It applies to any organisation that stores, processes or transmits cardholder data, or whose systems could affect the security of that data.

It is organised into 12 principal requirements under six goals, from network security and secure configuration to encryption, access control, logging and testing. The current version is v4.0.1, and requirements that were future-dated in v4.0 became mandatory on 31 March 2025.

How you prove compliance depends on your size and role. Smaller merchants usually complete a Self-Assessment Questionnaire (SAQ). Larger merchants and service providers generally undergo an on-site assessment by a Qualified Security Assessor, which produces a Report on Compliance (ROC) and an Attestation of Compliance.

Key terms in plain English

CDE
Cardholder data environment: the people, processes and systems that store, process or transmit card data.
SAQ
Self-Assessment Questionnaire: the form most merchants use to validate compliance. There are several types.
QSA
Qualified Security Assessor: a firm approved by the council to perform formal assessments.
Segmentation
Network controls that isolate the CDE so fewer systems are in scope. It must be tested to be trusted.
Requirements

The 12 requirements, grouped by goal

These are summaries in plain language. The standard itself contains detailed sub-requirements and testing procedures.

1–2

Requirements 1 and 2: network controls and secure configuration

Install and maintain network security controls, and apply secure configurations to all system components. Remove vendor defaults and close what you do not need.

What it looks like in practice

  • Documented firewall and routing rules that are reviewed
  • Hardened baselines for servers and cloud services
  • No default accounts or passwords
3–4

Requirements 3 and 4: stored data and data in transit

Protect stored account data and use strong cryptography when cardholder data crosses open, public networks. Do not keep sensitive authentication data after authorisation.

What it looks like in practice

  • Data retention and discovery processes
  • Strong encryption and key management
  • TLS configured correctly on every public endpoint
5–6

Requirements 5 and 6: malware and secure software

Protect systems from malicious software and develop and maintain secure systems and software. For public-facing web applications, you must address new threats on an ongoing basis, for example through reviews or an automated technical solution.

What it looks like in practice

  • Anti-malware coverage and alerting
  • Secure development and code review practices
  • Patch management with defined timelines
7–9

Requirements 7 to 9: need to know, authentication, physical access

Restrict access by business need to know, identify users and authenticate access, and restrict physical access to cardholder data. Multi-factor authentication is expected for access into the CDE.

What it looks like in practice

  • Role-based access with periodic reviews
  • MFA for administrative and remote access
  • Physical access logs and visitor controls
10–11

Requirements 10 and 11: logging, scanning and penetration testing

Log and monitor all access to system components and cardholder data, and test security regularly. Requirement 11 covers wireless checks, internal and external vulnerability scans, penetration testing and change detection.

What it looks like in practice

  • Centralised, tamper-resistant logs
  • Quarterly vulnerability scans, with external scans by an approved scanning vendor
  • Internal and external penetration tests by qualified, independent testers
12

Requirement 12: policies, risk and awareness

Support information security with organisational policies and programmes: a security policy, formal risk assessment, awareness training, incident response and third-party management.

What it looks like in practice

  • An information security policy reviewed yearly
  • A tested incident response plan
  • A list of service providers and their responsibilities
Fit

Who usually needs PCI DSS

Merchants taking card payments

Any business accepting cards online or in person is covered, in different ways by volume and set-up.

Payment and platform providers

Service providers that handle card data for others face the most rigorous validation.

SaaS with embedded checkout

Even with a hosted payment page, your site design can affect scope and the SAQ you complete.

Banks and processors

Acquirers and issuers set contractual expectations and ask merchants and providers for evidence.

Board and leadership view

Why PCI DSS matters to your board

The work is technical. The consequences of getting PCI DSS wrong show up in revenue, liability and reputation, which is why we report on it in the language of the boardroom first.

Revenue and the right to take cards

Acquirers can raise fees or restrict card acceptance if validation lapses, putting payment revenue at risk.

Contractual exposure and fines

PCI DSS is enforced through contracts. Gaps can bring penalties and added costs after an incident.

Reputation with customers

A card data breach is public and costly. Tested controls reduce the chance of that headline.

Annual deadlines and ownership

Testing is due at least every 12 months and after major change. Clear owners avoid last-minute scrambles.

How it works

A realistic PCI DSS roadmap

Timelines are typical ranges, not promises. Yours depends on scope, team size and how much is already in place.

  1. 1

    Find where card data lives

    Weeks 1 to 2

    Map every place card data is stored, processed or transmitted, including third-party services.

  2. 2

    Reduce scope

    Weeks 2 to 6

    Use tokenisation, hosted payment pages and segmentation so fewer systems fall in scope.

  3. 3

    Choose the validation route

    Week 4

    Identify your merchant or service provider level and the SAQ or ROC you need.

  4. 4

    Close the gaps

    Months 2 to 4

    Fix configuration, access, logging and policy gaps against the 12 requirements.

  5. 5

    Run required tests

    Month 3 to 4

    Complete vulnerability scans, penetration testing and segmentation testing, then fix and retest.

  6. 6

    Validate and attest

    Month 4 to 6

    Complete the SAQ or ROC and submit your Attestation of Compliance to your acquirer or customers.

VAPT

Where VAPT is required for PCI DSS

PCI DSS is one of the few standards that spells out penetration testing. Requirement 11.4 asks for a defined methodology, coverage of the whole CDE and critical systems, application-layer and network-layer tests, and retesting after fixes.

11.4.1

Defined methodology

Testing follows an industry-accepted approach, covers the full CDE perimeter and critical systems, and includes both internal and external tests.

11.4.2–3

Internal and external tests

Penetration tests are performed at least every 12 months and after significant infrastructure or application changes by qualified testers.

11.4.4

Fix and retest

Exploitable vulnerabilities found are corrected and the testing is repeated to verify the fix.

11.4.5

Segmentation testing

If segmentation reduces scope, it must be tested. Service providers must repeat this at least every six months.

Avoid these

Common PCI DSS mistakes, and how to avoid them

!

Assuming a hosted checkout removes all scope

Redirects and embedded forms still change which SAQ applies, and your site can still affect payment page security.

!

Using a vulnerability scan as the penetration test

Requirement 11.4 expects expert-led testing and exploitation attempts, not just a scanner export.

!

Forgetting segmentation proof

If you claim segmentation, a tester must demonstrate it works. Otherwise the whole network can be pulled into scope.

!

Testing only once a year, regardless of change

Significant changes trigger a retest. Plan one after major releases or infrastructure moves.

Why Sumrite

Why teams choose Sumrite for PCI DSS

PCI DSS is a team effort between your people, your auditor and your customers. We take the weight off all three.

One team, start to finish

From the first question about PCI DSS to the final report, you deal with one accountable team and one timeline.

250+ clients cleared through audits

We have taken more than 250 clients through SOC 2 and similar audits, so we know what reviewers ask for and what they accept.

Plain English, not jargon

We explain what PCI DSS means for your business, your roadmap and your customers before any technical work starts.

Partner network for the formal step

Where a third party issues the report or certificate, we route that step through local partner firms so you never have to manage a second vendor.

Scope of work

What Sumrite delivers for PCI DSS

One accountable team takes you from scoping to retest. The people who test your systems are the people who explain the findings to your leadership.

Gap analysis

Scope and controls compared with the 12 requirements, with a plan to reduce what is in scope.

Penetration testing

Internal and external, application-layer and network-layer testing following a defined methodology.

Control validation

Segmentation testing and checks that network, access and logging controls operate as documented.

Evidence pack

Methodology, scope, findings and fix records laid out for your SAQ or ROC reviewer.

Remediation support and retest

Fix guidance for engineers, then a retest confirming exploitable findings are closed.

Board-ready report

A plain-language view of card data risk and progress for executives.

Fixed scope, one team, no hand-offsYou get a named lead, a clear scope document before work starts and a report your leadership, customers and reviewers can read without a translator. We stay with you through your review to answer questions about what we tested and found.
Need a formal PCI DSS assessment?We run the full engagement for you and route the formal assessment through our PCI QSA partner firms, so you deal with one team and one timeline. Talk to us →
Deliverables

What your leadership team receives

Every engagement ends with material written for two audiences: a plain-language view for executives and the board, and full technical detail for the engineers who fix things.

  • An executive summary

    Your card data exposure and top risks in plain language.

  • A scope map

    Where card data lives and which systems fall in scope.

  • Testing evidence for reviewers

    Reports and retest letters aligned to Requirement 11.4.

  • A remediation tracker

    Findings with owners, severity and closure status.

  • Support through reviews

    The same Sumrite team stays with you while assessors and acquirers ask questions.

FAQ

PCI DSS questions, answered

Is PCI DSS a law?

No. It is an industry standard enforced through contracts with card brands and acquiring banks. Non-compliance can lead to fines, higher fees or loss of the ability to take cards.

Does PCI DSS require penetration testing?

Yes. Requirement 11.4 requires external and internal penetration testing at least once every 12 months and after significant changes, using qualified and organisationally independent testers.

What is the difference between an SAQ and a ROC?

An SAQ is a self-assessment form many merchants complete. A ROC is a detailed report produced by a Qualified Security Assessor, typically for larger merchants and service providers.

Which version should I follow?

PCI DSS v4.0.1 is the current version. The earlier v4.0 was retired at the end of 2024, and its future-dated requirements became mandatory on 31 March 2025.

How can I reduce PCI scope?

Use a compliant payment provider with hosted fields or redirects, never store sensitive authentication data, tokenise card numbers and segment the systems that remain in scope.

Can Sumrite also arrange the formal step for me?

We run the full engagement for you and route the formal assessment through our PCI QSA partner firms, so you deal with one team and one timeline.

See all FAQs →

Ready to get PCI DSS sorted?

Tell us your scope, your deadline and who is asking. You get a fixed-scope quote and a named lead from day one.

Get a Quote →