PCI SSC

Payment Card Industry Data Security Standard (PCI DSS)

PCI Security Standards Council standard for protecting payment account data wherever it is stored, processed or transmitted. Current: v4.0.1.

At a glance

Short name
PCI DSS
Issuing / stewarding body
PCI SSC
Jurisdiction
International
Also known as / related labels
PCI DSS v4.0.1 · PCI Secure Software Standard · PCI Secure SLC Standard · PCI SSC

What this entry covers

The Payment Card Industry Data Security Standard (PCI DSS) is a set of technical and operational requirements for protecting payment account data. It is maintained by the PCI Security Standards Council, an industry body, and applies to entities that store, process or transmit cardholder data or that can affect its security. The current version is PCI DSS v4.0.1.

MyRHC indexes this framework so practitioners, auditors, and automated agents can find the authoritative primary sources in one place. This page is a navigation aid. It is not legal advice and is not a substitute for the official text.

Official documentation

Recent changes

  • 2026-06-03: PCI SSC opened a request for comments on PCI DSS v4.0.1, running to 20 July 2026, as it begins work on the next iteration of the standard. PCI SSC
  • 2025-03-31: Requirements that v4.0 marked as future-dated became effective. PCI SSC
  • 2024-12-31: PCI DSS v4.0 was retired, leaving v4.0.1 as the active version. PCI SSC
  • 2024-06-11: PCI SSC published PCI DSS v4.0.1, a limited revision with clarifications and no new requirements. PCI SSC
  • 2022-10-28: PA-DSS was retired, replaced by the PCI Secure Software Standard and Secure Software Lifecycle Standard. PCI SSC

How to use this index entry

  1. Open the official link above (or the agency home if the deep link drifts).
  2. Confirm edition / revision date against your program scope.
  3. Map applicability by sector and jurisdiction listed in the metadata.
  4. Follow related frameworks only after checking their own official sources.

Disclaimers

  • MyRHC does not host proprietary standards text (ISO, some industry bodies).
  • Where standards are paywalled, we link to the publisher’s catalog page.
  • Always verify current requirements with counsel and the issuing authority.
Index only — not legal advice. MyRHC does not certify compliance. Confirm current requirements with the issuing authority and qualified counsel. Proprietary standards text remains with its publisher.