Requirement 12.8: your providers are your responsibility
By Sam Rivera, Founder, SentinelPanda · October 14, 2026 · 3 min read · PCI DSS
Outsourcing the handling of card data does not outsource the accountability for it. Requirement 12.8 is where the standard says so in plain terms.
What the requirement covers
- A maintained list of service providers with a description of the service each provides.
- Written agreements in which providers acknowledge their responsibility for the cardholder data they possess, store, process or transmit on your behalf.
- A documented due diligence process before engaging a provider.
- Monitoring of each provider's PCI DSS compliance status at least annually.
- Documented information about which PCI DSS requirements each party is responsible for — the responsibility matrix.
Why the attestation requests arrive
When a customer asks you for an attestation of compliance, they are usually not being difficult. They are answering 12.8.4, which obliges them to monitor the compliance status of providers who handle card data for them.
That reframes the request usefully. It is not a negotiation about whether your security is good enough; it is a document the other side needs in order to satisfy their own assessor. A current attestation turns a recurring and unpredictable conversation into an attachment, which is worth more than it costs.
The responsibility matrix is the hard part
Everything else in 12.8 is administration. The matrix is the part that requires thought, because it forces both sides to say which of them covers each applicable requirement — and the answer is often neither.
The classic gap is logging and monitoring at a boundary: the provider logs their side, you log yours, and the handoff between them is monitored by nobody. Another is patching of a component the provider installs in your environment. These gaps are invisible until the matrix is written, which is exactly why the standard asks for it.
Good providers publish a shared-responsibility document and will give it to you on request. If a provider cannot produce one, that is itself a finding worth recording in your due diligence notes.
Where the list usually falls short
Most organisations list the obvious providers — the payment processor, the gateway, the hosting platform. The ones that get missed are the quiet ones: the chat widget on the checkout page, the tag manager, the analytics vendor, the fraud-scoring service, the customer support tool whose agents can see order details.
The test is not whether the vendor is important. It is whether they could affect the security of cardholder data, which includes anything running on the page where a card is entered.
Running it as a process
Review the list annually and tie the review to something you already do — renewals, budget planning, the compliance calendar. A list reviewed when someone remembers is a list that is out of date.
Collect each provider's attestation on a schedule rather than on demand. The attestation has a date on it, and an assessor will check whether the one you hold has expired. Diarising the renewal is a five-minute task that prevents a scramble.