PCI DSS, the Payment Card Industry Data Security Standard, is a set of security requirements for any organization that stores, processes, or transmits payment card data, or that can affect its security. It’s published by the PCI Security Standards Council and enforced by the card brands and acquiring banks through their contracts. The current version is PCI DSS v4.0.1, which has 12 requirements grouped under six goals.
What does PCI stand for?
PCI stands for Payment Card Industry. DSS stands for Data Security Standard. “PCI compliance” and “PCI DSS compliance” mean the same thing: meeting the Data Security Standard.
The standard is maintained by the PCI Security Standards Council (PCI SSC). American Express, Discover, JCB, Mastercard, and Visa founded the Council in 2006 to replace their separate security programs with one shared standard. The card brands still run their own compliance programs and enforce PCI DSS through them.
What PCI DSS covers
PCI DSS covers the people, processes, and technology that touch payment card data. Its 12 requirements fall under six goals:
- Build and maintain a secure network and systems
- Protect account data
- Maintain a vulnerability management program
- Implement strong access control measures
- Regularly monitor and test networks
- Maintain an information security policy
PCI DSS is one of several PCI SSC standards. Others cover PIN security, point-to-point encryption (P2PE), payment software (the Software Security Framework), and payment devices. For a business that accepts or handles cards, PCI DSS is the one that applies. The full list is in PCI DSS requirements. For the big picture, see the PCI DSS compliance guide.
What data does PCI DSS protect?
PCI DSS protects account data, in two kinds:
| Cardholder data (CHD) | Sensitive authentication data (SAD) | |
|---|---|---|
| Elements |
|
|
| Storage | May be stored if protected (Requirement 3) | Must not be stored after authorization, even encrypted |
*In scope only when stored, processed, or transmitted with the PAN.
The PAN is the key. Any system that stores, processes, or transmits it, or that could affect its security, falls under PCI DSS.
Scope: the cardholder data environment
PCI DSS applies to your cardholder data environment (CDE): the people, processes, and technology that store, process, or transmit account data. Scope also includes systems that connect to the CDE or could affect its security. Every system falls into one of three groups:
- In the CDE: systems that handle card data, such as payment servers, POS terminals, and databases holding PANs.
- Connected-to or security-impacting: systems that touch the CDE or protect it, such as directory services, jump hosts, logging servers, and management tools.
- Out of scope: systems with no connection to the CDE and no way to affect its security. You must be able to show this.
Scope decides how much work PCI DSS takes. A smaller CDE means fewer systems to secure, test, and assess.
Data-flow and network diagrams
PCI DSS requires a current network diagram (Requirement 1) and data-flow diagrams showing how account data moves through your systems and networks. A useful data-flow diagram shows:
- every point where card data enters your organization (web, phone, POS, mail, partners)
- every system it passes through or rests in
- every point where it leaves, such as to your processor or a service provider
- the CDE boundary and any segmentation controls
Assessors start with these diagrams. If they’re out of date, scope is in doubt.
Network segmentation
PCI DSS doesn’t require network segmentation, but it’s the most common way to reduce scope. Isolate the CDE from the rest of your network with firewalls or other controls, and systems on the other side can fall out of scope.
If you rely on segmentation to reduce scope, you must prove it works. Penetration testing confirms the segmentation controls are effective. It’s required at least annually for merchants and more often for service providers. See PCI DSS requirements.
P2PE and tokenization
- Point-to-point encryption (P2PE) encrypts card data at the payment terminal, and only the solution provider can decrypt it. Merchants using a P2PE solution validated and listed by the PCI SSC may qualify for the much shorter SAQ P2PE.
- Tokenization replaces the PAN with a token that’s useless if stolen. Systems that handle only tokens may fall out of scope, though the tokenization system itself stays in scope. Payment networks also use tokenization through token service providers.
Neither one eliminates PCI DSS. Both can sharply reduce how much of it applies.
Key PCI DSS terms
| Term | Meaning |
|---|---|
| PCI SSC | The PCI Security Standards Council, which publishes the standard |
| QSA | Qualified Security Assessor: a firm and individuals certified to assess PCI DSS compliance and issue a Report on Compliance |
| ASV | Approved Scanning Vendor: a company approved to run the quarterly external vulnerability scans PCI DSS requires |
| SAQ | Self-Assessment Questionnaire: a self-validation form, in several types matched to how you accept payments |
| ROC / AOC | Report on Compliance / Attestation of Compliance: the detailed assessment report and the signed declaration of compliance |
| Non-console administrative access | Administrative access over a network rather than at the physical console. It requires multifactor authentication. |
| Common point of purchase (CPP) | The location card brands identify as the shared source of compromised cards. See what CPP means. |
For the full list, see the PCI DSS glossary.
Is PCI DSS a law?
No. PCI DSS is an industry standard that applies through contracts with acquiring banks and card brands. Some U.S. states reference it in their data security laws, and a card data breach can trigger breach-notification laws regardless. See who enforces PCI DSS.
Frequently asked questions
Where to go next
- Who needs PCI DSS: merchants, service providers, and levels
- How PCI DSS assessment works: SAQs, ROCs, and ASV scans
- How to prepare for PCI DSS
Work with RSI Security
RSI Security is a PCI Qualified Security Assessor (QSA) company and an Approved Scanning Vendor (ASV). It performs PCI DSS assessments and quarterly ASV scans. Organizations that need help with scoping or readiness can work with RSI Security through a separate advisory engagement. RSI Security provides either advisory or assessment to a given client, never both.
Schedule a PCI DSS assessment · Talk to an advisor about scoping

