Site icon RSI Security

What Is PCI DSS? The Payment Card Industry Data Security Standard Explained

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:

  1. Build and maintain a secure network and systems
  2. Protect account data
  3. Maintain a vulnerability management program
  4. Implement strong access control measures
  5. Regularly monitor and test networks
  6. 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
  • Primary account number (PAN), the card number
  • Cardholder name*
  • Expiration date*
  • Service code*
  • Full track data from the magnetic stripe or chip
  • Card verification code (CVV2, CVC2, CID)
  • PIN and PIN block
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:

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:

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

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

What does PCI DSS stand for?
PCI DSS stands for Payment Card Industry Data Security Standard. It is the security standard published by the PCI Security Standards Council for organizations that store, process, or transmit payment card data. “PCI compliance” is shorthand for meeting PCI DSS.
What is the PCI Security Standards Council?
The PCI Security Standards Council (PCI SSC) is the organization that develops and maintains PCI DSS and related payment security standards. American Express, Discover, JCB, Mastercard, and Visa founded it in 2006. The Council publishes the standards and qualifies assessors, but the card brands and acquiring banks enforce compliance.
What is the difference between cardholder data and sensitive authentication data?
Cardholder data is the primary account number, plus the cardholder name, expiration date, and service code when stored with it, and it may be stored if protected. Sensitive authentication data includes full track data, card verification codes, and PINs. It must never be stored after authorization, even if encrypted.
What is the cardholder data environment (CDE)?
The cardholder data environment is the people, processes, and technology that store, process, or transmit cardholder data or sensitive authentication data. PCI DSS applies to the CDE and to any system connected to it or able to affect its security. Reducing the size of the CDE reduces the scope of PCI DSS.
Is network segmentation required for PCI DSS?
No, but it is the most common way to reduce scope. Isolating the cardholder data environment from other networks can take those systems out of scope. Organizations that rely on segmentation must verify it works through penetration testing, at least annually for merchants and more frequently for service providers.
Does P2PE make a business PCI compliant?
No, but it can greatly reduce what applies. A point-to-point encryption solution validated and listed by the PCI Security Standards Council encrypts card data at the terminal, keeping it unreadable in the merchant’s systems. Eligible merchants may then validate with the shorter SAQ P2PE instead of a broader questionnaire.

Where to go next

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

Request a consultation

Exit mobile version