Payment standard

PCI DSS

The twelve requirement groups of the Payment Card Industry Data Security Standard, version 4.0, with evidence mapped per requirement.

Gap review Applies in: North America, Europe, Asia Pacific

Controls passing
2 of 4
Needs action
2
Readiness
50%

Sample data The framework defines 78 controls in total. The figures above and the checklist below track a sample of 4 of them, with owners and due dates.

What PCI DSS requires

PCI DSS is the payment card industry’s security standard. The PCI Security Standards Council maintains it, and the card brands and acquiring banks enforce it. It applies to every organisation that stores, processes, or transmits cardholder data, and the first task in any programme is fixing exactly where that data lives, because scope decides the size of everything that follows.

Version 4.0 organises the standard into twelve requirement groups across six goals: network security controls, protected account data, vulnerability management, access control, monitoring and testing, and an information security policy. Each requirement states the evidence an assessor expects, from firewall rule reviews and stored-data inventories to multi-factor authentication records and quarterly scan results.

How an organisation validates depends on its transaction volume and the card brands’ merchant levels. Larger merchants work with a qualified security assessor and file a Report on Compliance. Smaller ones complete a self-assessment questionnaire matched to the way they take payments. Either way, external vulnerability scans by an approved scanning vendor run at least once a quarter.

Evidence checklist

The sample controls tracked for this guide, in due-date order. A control marked as passing has current evidence on file; one marked as needing action has an owner and a deadline.

  • Req. 3 — Stored account data inventory verified

    Owner: Payments engineer · Due

    Needs action
  • Req. 8 — Multi-factor authentication for all remote access

    Owner: IT operations lead · Due

    Passing
  • Req. 11 — Vulnerability scans run and findings triaged

    Owner: Security lead · Due

    Needs action
  • Req. 12 — Incident response plan roles confirmed

    Owner: Compliance manager · Due

    Passing
PCI DSS sample controls by status (controls)
0 1 2 PCI DSS Passing Needs action

Related guides

Guides in the same family are listed first.