A PCI DSS Attestation of Compliance (AOC) is the PCI Security Standards Council form that declares an entity's compliance status with the Payment Card Industry Data Security Standard, following either a Report on Compliance or a self-assessment questionnaire.
What AOC means
The current standard is PCI DSS v4.0.1, published in June 2024. Requirements that v4.0 introduced as future-dated became mandatory on 31 March 2025. Service providers complete either an AOC for a Report on Compliance, usually prepared by a Qualified Security Assessor, or an AOC for SAQ D for Service Providers, the self-assessment route.
Requirement 12.8 asks entities to manage their third-party service providers: keep a list, have written agreements, carry out due diligence before engagement, monitor each provider's PCI DSS compliance status at least once every 12 months, and record which requirements each provider manages. Requirement 12.9 asks service providers to acknowledge their responsibility in writing and to support customers' requests for information.
The AOC is the usual evidence for Requirement 12.8.4. Read it with the vendor's responsibility matrix, because a provider can be compliant for its part while leaving requirements to you. Shared responsibilities, where both parties operate part of a requirement, need particular attention, because each side may assume the other covers them.
What to check in vendor documents
- The entity name and the services covered, matching what you use.
- The PCI DSS version, the assessment date and whether it is within 12 months.
- Whether it follows a Report on Compliance or a self-assessment, and the assessor's details.
- Requirements marked not applicable, not tested or met with a compensating control.
- A responsibility matrix showing which requirements remain yours.
Related terms
- Compensating controlA compensating control is an alternative control that meets the intent of a requirement when the primary control cannot be implemented, giving a similar level of protection against the same risk.
- Penetration test reportA penetration test report is the written result of an authorised simulated attack on a system, documenting the scope, method, findings with severity and recommendations. Vendors usually share a summary or a letter from the tester rather than the full report.
- Vendor due diligenceVendor due diligence is the assessment an organisation carries out before contracting with a vendor, and again at renewal, to confirm the vendor can deliver the service safely and meet the legal, security, financial and operational requirements that apply.
- Continuous vendor monitoringContinuous vendor monitoring is the ongoing tracking of a vendor's risk between formal assessments, using triggers such as new reports, incidents, contract or sub-processor changes, financial events and external signals, so reviews happen when risk changes.
Sources
- PCI Security Standards Council, document library (PCI DSS v4.0.1 and AOC templates)www.pcisecuritystandards.org/document_library
Summarised for practitioners, not legal advice. Check the source text for your own obligations.