Most PCI DSS myths make the standard seem either narrower or more final than it is. Outsourcing, encryption, and small size can change how PCI DSS affects you, but none of them automatically takes you out of it. Each correction below comes from official PCI SSC documents.
For the basics, start with what PCI DSS is.
Myth: Outsourcing makes payments the provider’s problem
Outsourcing can reduce what you manage, and your responsibility stays with you. PCI DSS says entities that outsource remain responsible for ensuring the third party protects account data. Using a compliant third-party service provider (TPSP) does not make you compliant.
You also have work to do under Requirement 12.8. For example, you monitor each TPSP’s compliance status at least once every 12 months. You also record which requirements each party manages.
Myth: Small merchants are exempt
PCI DSS sets no size exemption. It is intended for all entities that store, process, or transmit account data or could affect its security. Size may influence how you validate, because the payment brands define merchant levels and who must validate.
A short form is still a form of validation. Ask your acquirer what it expects from your business.
Myth: PCI SSC issues the fines
The PCI Security Standards Council (PCI SSC) is the standards body. It maintains the standards and runs assessor programs. The QSA Program Guide assigns enforcement elsewhere: the payment brands manage enforcement programs and establish penalties and fees.
Direct questions about consequences to your acquirer or the relevant payment brand.
Myth: PCI SSC certifies your business
PCI SSC does not certify merchants. A QSA states whether an assessed entity has achieved compliance, and the entity submits its report and Attestation of Compliance as directed. PCI SSC performs quality reviews of assessor work, and it does not approve Reports on Compliance from a technical perspective.
Myth: One good assessment means you are finished
An assessment reflects what was tested at that time. The Program Guide expects customers to maintain compliance at all times, and payment brands may require annual assessments.
Several requirements also recur between assessments. External vulnerability scans run at least once every three months under Requirement 11.3.2. Scope is confirmed at least once every 12 months under Requirement 12.5.2. Business-as-usual processes help keep controls working in between.
Myth: Encryption takes card data out of scope
Encryption protects data, and PCI DSS accepts strong cryptography as a way to render stored data unreadable. However, encryption alone is generally insufficient to take cardholder data out of scope. Systems that encrypt, decrypt, or manage keys remain in scope.
A TPSP that only holds data it cannot decrypt may be able to exclude that data if certain conditions are met. A PCI-listed point-to-point encryption solution can significantly reduce applicable requirements, but it does not remove PCI DSS completely.
Myth: If we never store card data, PCI DSS does not apply
Storage is only one trigger. PCI DSS also covers processing and transmission, along with environments that could affect account data security.
SAQ A-EP shows this clearly. It applies to e-commerce merchants whose websites do not receive account data but do affect the security of the payment transaction.
For a wider view of the standard, return to the PCI DSS hub.
Frequently asked questions
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 readiness
Sources
- PCI DSS v4.0.1 (Section 2, PCI DSS Applicability Information)
- PCI DSS v4.0.1 (Section 4, Encrypted Cardholder Data and Impact on PCI DSS Scope)
- PCI DSS v4.0.1 (Section 4, Use of Third-Party Service Providers, and Requirements 12.8.4 and 12.8.5)
- PCI DSS v4.0.1 (Section 5, Best Practices for Implementing PCI DSS into Business-as-Usual Processes, and Requirements 11.3.2 and 12.5.2)
- PCI DSS v4.0.1 SAQ A-EP (Merchant Eligibility Criteria)
- QSA Program Guide v4.1 (Sections 2.1 to 2.4, Roles and Responsibilities, and Section 4, PCI DSS Assessment Process)
- Guidance for PCI DSS Scoping and Network Segmentation, v1.1 (Tools and technologies note on encryption and tokenization)
