This glossary explains the terms used most often across our PCI DSS guide, in plain language. PCI SSC’s own definitions appear in Appendix G of PCI DSS v4.0.1, and the standard’s wording controls wherever the two differ.
- Account data
- Cardholder data and/or sensitive authentication data. PCI DSS applies wherever account data is stored, processed, or transmitted.
- Acquirer
- An entity, typically a financial institution, defined by a payment brand as an acquirer, that processes card transactions for merchants. Also called a merchant bank. Acquirers and payment brands determine how a merchant must validate compliance.
- Approved Scanning Vendor (ASV)
- A company PCI SSC has approved to run the external vulnerability scans required by PCI DSS Requirement 11.3.2.
- Attestation of Compliance (AOC)
- The signed form an entity uses to declare the results of its PCI DSS assessment, completed alongside a ROC or SAQ.
- Cardholder data (CHD)
- At minimum, the full primary account number. It can also include cardholder name, expiration date, and service code together with the full PAN.
- Cardholder data environment (CDE)
- The system components, people, and processes that store, process, or transmit account data, plus systems with unrestricted connectivity to them.
- Compensating control
- An alternative control used when a legitimate, documented constraint prevents meeting a requirement as written. It must meet the intent and rigor of the original requirement.
- Customized approach
- A PCI DSS validation option in which an entity meets a requirement’s stated objective with its own control design, backed by a targeted risk analysis and tested by an assessor.
- Defined approach
- The traditional way to meet PCI DSS: implement the requirement as written and have it validated with the listed testing procedures.
- Incident response plan
- The documented, tested procedure an organization follows when it suspects or confirms a security incident. Requirement 12.10 sets what it must cover.
- Internal Security Assessor (ISA)
- An employee of an organization who holds a PCI SSC qualification and performs internal PCI DSS assessments for that organization.
- Multi-factor authentication (MFA)
- Authentication using at least two different factors: something you know, something you have, or something you are or do.
- Network security controls (NSCs)
- Firewalls and other technologies that control traffic between network segments based on defined rules.
- Payment brands
- The card networks whose cards a merchant accepts. American Express, Discover, JCB, Mastercard, and Visa founded PCI SSC, and each runs its own compliance program.
- PCI Security Standards Council (PCI SSC)
- The organization that develops and maintains PCI DSS and related standards. Payment brands, not PCI SSC, manage compliance enforcement programs.
- Point of interaction (POI)
- The initial point where account data is read from a card, such as a payment terminal.
- Point-to-point encryption (P2PE)
- A solution that encrypts account data at the payment terminal. Merchants using a validated, PCI-listed P2PE solution can have fewer applicable requirements.
- Primary account number (PAN)
- The unique payment card number that identifies the issuer and the cardholder’s account.
- Qualified Security Assessor (QSA)
- A company PCI SSC has qualified to perform independent PCI DSS assessments. The term also commonly refers to the qualified employees of that company who do the work.
- Report on Compliance (ROC)
- The detailed report documenting the results of a PCI DSS assessment, typically prepared by a QSA.
- Scope
- All system components, people, and processes that must be assessed against PCI DSS: the CDE, systems connected to it, and anything that could affect its security.
- Segmentation
- Isolating the CDE from other networks. PCI DSS does not require it, but effective segmentation can reduce what is in scope.
- Self-Assessment Questionnaire (SAQ)
- A validation tool eligible merchants and service providers complete to report their own PCI DSS assessment results. Several versions exist for different payment setups.
- Sensitive authentication data (SAD)
- Security data used to authenticate cardholders and authorize transactions, including full track data, card verification codes, and PINs or PIN blocks. Merchants must not store it after authorization.
- Service provider
- A business that is not a payment brand and that stores, processes, or transmits account data for another entity, or that could affect the security of that data.
- Targeted risk analysis (TRA)
- A focused, documented analysis used to set how often a control runs where PCI DSS allows flexibility, and to support the customized approach.
- Third-party service provider (TPSP)
- An outside business that handles account data or could affect its security on behalf of a customer. Using one does not remove the customer’s own responsibility to manage it.
- Tokenization
- Replacing a PAN with a substitute value. It may help reduce scope when properly implemented, though the token systems themselves may stay in scope.
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 (Appendix G, Glossary of Terms, Abbreviations, and Acronyms)
- PCI DSS v4.0.1 (Section 4, Scope of PCI DSS Requirements; Section 8, Approaches for Implementing and Validating PCI DSS; Appendix B, Compensating Controls)
