Defining the cardholder data environment, choosing the right validation path, and understanding who does what across the payment ecosystem. ← Back to PCI DSS: The Complete Guide
Guide | Focus |
|---|---|
PCI DSS Scope Determination: Cardholder Data Environment (CDE) Mapping | Defining what's in scope |
PCI DSS Self-Assessment Questionnaire (SAQ): Types and Selection | Which SAQ applies to you |
PCI DSS Approved Scanning Vendor (ASV): External Vulnerability Scanning | Quarterly external scans |
PCI DSS Qualified Security Assessor (QSA): Professional Assessment Process | Working with a QSA |
PCI DSS Report on Compliance (ROC): Documentation Requirements | The ROC deliverable |
The AOC deliverable | |
PCI DSS Service Provider Requirements: Level 1 and Level 2 Providers | Service provider obligations |
PCI DSS Merchant Requirements: Transaction Volume-Based Obligations | Merchant obligations by volume |
PCI DSS Acquirer and Processor Requirements: Payment Ecosystem Roles | Acquirer and processor roles |
PCI DSS Validation Requirements: Annual Compliance Demonstration | Annual validation obligations |
Resources: Scoping & CDE Worksheet · SAQ Selector · Merchant Level / SAQ Reference · ROC/AOC Reader's Guide