PCI DSS
What Is PCI DSS? The v4.0.1 Payment Security Standard
3 July 2026 · Updated 3 July 2026
PCI DSS is the Payment Card Industry Data Security Standard, the rulebook for protecting payment card data. It sets 12 core requirements for anyone who stores, processes or transmits cardholder data. The current version is v4.0.1, published June 2024, with a set of new requirements that became mandatory on 31 March 2025.
If a business touches a card number, PCI DSS applies. It is not a certification chased for marketing. It is a condition of being allowed to accept cards, written into the contract with the bank.
What is PCI DSS and who maintains it?
PCI DSS is the Payment Card Industry Data Security Standard (PCI DSS), a baseline of technical and operational requirements built to protect payment account data. It is maintained by the PCI Security Standards Council (PCI SSC), a body founded by the major card brands including Visa and Mastercard. The Council writes the standard and the supporting documents. It does not enforce compliance or decide whether a given implementation passes. That job belongs to the card brands and the acquiring banks that hold merchant relationships. The current version is v4.0.1, published on 11 June 2024, which replaced v4.0 as the only active version from 31 December 2024. The standard applies globally, so an Australian merchant works to the same document as one in the United States or the United Kingdom. What differs is how each card brand and acquirer sets validation and reporting obligations on top of the standard.
Who has to comply with PCI DSS?
Any entity that stores, processes or transmits cardholder data or sensitive authentication data, or that could affect the security of that data. That is a wide net. It captures merchants of every size, payment processors, acquirers, issuers and third party service providers (TPSPs). There is no revenue threshold and no exemption for small volume. A cafe taking one card payment a day is in scope, the same as a national retailer. What changes with transaction volume is the validation path, covered by the merchant levels and the Self-Assessment Questionnaire types. Cardholder data means the primary account number (PAN) and, where present, the cardholder name, expiry date and service code. Sensitive authentication data means the full track data, card verification codes and PINs, which must never be stored after authorisation. If card handling is outsourced entirely to a compliant provider, the scope shrinks, but it does not vanish.
What are the 12 requirements of PCI DSS?
The 12 requirements are organised under six goals. Build and maintain a secure network and systems (requirements 1 and 2): install and maintain network security controls, and apply secure configurations to all system components. Protect account data (requirements 3 and 4): protect stored account data, and protect cardholder data with strong cryptography during transmission over open public networks. Maintain a vulnerability management program (requirements 5 and 6): protect all systems and networks from malicious software, and develop and maintain secure systems and software. Implement strong access control measures (requirements 7, 8 and 9): restrict access to system components and cardholder data by business need to know, identify users and authenticate access, and restrict physical access to cardholder data. Regularly monitor and test networks (requirements 10 and 11): log and monitor all access, and test security of systems and networks regularly. And maintain an information security policy (requirement 12): support information security with organisational policies and programs. Under those 12 headings run hundreds of sub-requirements.
What is the difference between the defined approach and the customised approach?
v4.0 introduced two ways to meet most requirements: the defined approach and the customised approach. The defined approach is the traditional path. The control is implemented exactly as the standard describes it and the assessor tests against that defined method. The customised approach lets a risk mature organisation design its own control to meet the stated Customised Approach Objective, provided it gives at least equivalent protection to the defined requirement. It is not a shortcut. It requires a targeted risk analysis (TRA), documented evidence, and a Qualified Security Assessor (QSA) to test the bespoke control rather than a checklist. Most organisations still use the defined approach for most requirements. The customised approach suits mature teams with unusual architectures where the prescribed control does not fit but the security outcome can still be met and proven. For more on how v4.0.1 handles these, see what changed in PCI DSS 4.0.1, including the client-side payment page security requirements that became mandatory in March 2025.
How is PCI DSS compliance validated?
Validation depends on the merchant level, which the card brands set by annual transaction volume. Larger merchants, typically Level 1, undergo an annual assessment by a QSA producing a Report on Compliance (ROC), plus quarterly network scans by an Approved Scanning Vendor (ASV). Smaller merchants usually validate through an annual Self-Assessment Questionnaire (SAQ) and an Attestation of Compliance (AOC), with ASV scans where the SAQ type requires them. The specific thresholds vary by card brand, so treat any exact number as indicative and confirm with the acquirer. PCI DSS is not a one time event. v4.0 added requirement 12.5.2, an annual scope confirmation, forcing a yearly re-check of where cardholder data flows and what falls in scope. Compliance is a state maintained continuously, then evidenced at the assessment, not a certificate earned once and filed away.
PCI DSS and Australian obligations
PCI DSS is contractual, not legislative, in Australia. It is taken on through the merchant agreement with the acquiring bank and the card brand operating rules, not through an Act of Parliament. That does not make it optional. Failing it can mean fines passed down by the acquirer, higher transaction fees, or in serious cases losing the ability to accept cards. It also does not stand alone. A breach of cardholder data can trigger the Notifiable Data Breaches scheme under the Privacy Act 1988, so a card data incident carries legal reporting duties on top of the card brand consequences. Organisations already running an ISO 27001 information security management system or a SOC 2 program will recognise much of the control discipline, though neither maps cleanly onto PCI DSS. Where the cardholder data environment is hosted on a government or enterprise cloud platform that also requires IRAP assessment, both obligations run in parallel and share much of the same evidence base. For weighing which frameworks apply, our guide on choosing a cyber security framework is a useful starting point.
Frequently asked questions
What is PCI DSS in simple terms?
PCI DSS is the Payment Card Industry Data Security Standard, a set of technical and operational requirements for any organisation that stores, processes or transmits payment card data. It is maintained by the PCI Security Standards Council and enforced through the card brands and acquiring banks, not by a government regulator. The current version is v4.0.1, published in June 2024.
Who has to comply with PCI DSS?
Any entity that stores, processes or transmits cardholder data or sensitive authentication data, or that can affect the security of that data. That covers merchants of every size, payment processors, acquirers, issuers and service providers. There is no annual revenue floor. A single card transaction brings an entity into scope. What changes with size is how compliance is validated, not whether the standard applies.
Is PCI DSS a law in Australia?
No. PCI DSS is a contractual standard, not legislation. An organisation agrees to it through the merchant agreement with its acquiring bank and the card brand rules. That said, a breach of cardholder data in Australia can still trigger the Notifiable Data Breaches scheme under the Privacy Act, so PCI DSS obligations run alongside real legal ones.
What are the 12 requirements of PCI DSS?
The 12 requirements are grouped under six goals. They cover installing and maintaining network security controls, applying secure configurations, protecting stored account data, encrypting cardholder data in transit, protecting against malware, developing secure systems and software, restricting access by business need to know, authenticating access, restricting physical access, logging and monitoring, testing security regularly, and maintaining an information security policy.
What is the difference between PCI DSS v4.0 and v4.0.1?
v4.0.1 is a limited revision of v4.0 published in June 2024. It corrects typographical errors and clarifies the intent of some requirements and guidance. It adds no new requirements and deletes none. It also does not move the 31 March 2025 effective date for the future-dated v4.0 requirements. Since 31 December 2024, v4.0.1 is the only active version.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- Just Published: PCI DSS v4.0.1, PCI Security Standards Council blog, 11 June 2024
- Now is the Time for Organizations to Adopt the Future-Dated Requirements of PCI DSS v4.x, PCI Security Standards Council blog, 20 August 2024
- At a Glance: PCI DSS v4.0, PCI Security Standards Council blog, 13 April 2022
- PCI DSS v4.0: Is the Customized Approach Right For Your Organization?, PCI Security Standards Council blog
Last updated: 3 July, 2026
