
In this article
Suppose your provider sends you a PCI DSS Attestation of Compliance that names the hosted checkout you use. You also pay the same company for remote support. Can you rely on the attestation for that service too? Compare the services on your order with the services the assessment covered. Then ask who handles each security task for those services.
On 10 November 2026, the PCI Security Standards Council announced guidance on evidence and responsibilities for third-party service providers. It explains existing requirements. Start with the services you use and the records your provider gave you.
Start with the service you actually use
An Attestation of Compliance, or AOC, is a formal record of a PCI DSS assessment result. When a provider supplies one, check the service description against your order or service agreement. Look for the service you use and the requirements you rely on the provider to meet. One company can sell several services, and its assessment may cover only some of them.
Take the retailer in the opening example. Its checkout and remote support appear on the same invoice. The AOC clearly describes hosted checkout, but the retailer can’t tell whether the remote administration service was assessed. That’s a specific question the provider can answer: “Does this assessment include the support add-on our team uses? Where can we see that coverage?” The retailer keeps the checkout evidence and marks the add-on as unresolved while it waits for an answer.
In its public PCI FAQs, AWS describes making both an AOC and a Responsibility Summary available through AWS Artifact. That is one example of how the documents can be provided separately. The format may differ at your provider. What matters is that you can identify the exact service covered and find the information you need about who does the work.
Give each task an owner and a record
Once you know which service is in scope, ask what the provider does for that service. A responsibility matrix is a written list that shows which requirements the provider handles, which you handle and which you share. For a shared requirement, go one step further. Write down each side’s action and the record that would show it happened.
In our example, the provider runs its checkout platform. The retailer still decides who on its staff can sign in to the merchant dashboard and removes access when someone leaves. If remote support staff can make changes, ask who approves their access and who keeps the activity records. A row that simply says “access: shared” leaves those questions open. A row that names the task, its owner and its evidence gives each team something it can actually do.
Where applicable, PCI DSS Requirements 12.8.4 and 12.8.5 address the customer’s monitoring of the provider’s compliance status and the record of who is responsible for what. The corresponding service provider requirements in 12.9 cover written acknowledgement and support for customer information requests. Ask for both the written allocation and the evidence that fits it.
When the provider’s paperwork leaves a gap
In a PCI compliance forum, one commenter described a mismatch worth checking: the responsibility matrix assigns a requirement to the provider, but the attestation marks it as not applicable. Ask the provider to explain that line. The documents may cover different services, or the provider may need to show how it meets that requirement another way.
An applicable AOC can save you from asking for work that a provider has already demonstrated. If the provider doesn’t have an applicable AOC, PCI SSC’s evidence FAQ describes another route: specific evidence of the relevant requirements. The customer or its assessor needs to be able to evaluate that evidence. Requirement 12.8 calls for monitoring compliance status; by itself it does not require each provider to pass a separate validation. Check with the organisation that runs your compliance programme if you need to know what it will accept.
Make the next review easier
Keep the confirmed service name, provider contact, dated evidence and unresolved questions in one place. Under Requirement 12.8.4, the programme for monitoring provider compliance status must operate at least once every 12 months where the requirement applies. Consider checking the paperwork again when you add a service or change what a provider can access. PCI SSC’s FAQ 1601 distinguishes that routine from evidence your assessor has already reviewed. Evidence the assessor deemed valid at the time of review can remain valid through the end of that assessment. Keep the process for obtaining updated records in place.
For the retailer, the open question is remote support. Ask the provider to confirm the service is covered and identify the record that proves it. When the answer comes back, name the person who will check it and file it. If it leaves a gap, keep that gap open for follow-up.
Related 443 Labs guides
Bring your service list and any provider evidence you already have. 443 Labs can help you identify gaps before an assessment.
Get in TouchSources
- PCI SSC publishes new guidance on third-party service providers
- PCI SSC FAQ 1576: What evidence should a provider supply?
- AWS PCI DSS FAQs
- PCI DSS Requirements and Testing Procedures v4.0.1
- PCI SSC FAQ 1312: How provider use affects customer compliance
- 12.9.2 and PCI DSS Responsibility Matrix
- PCI SSC FAQ 1601: Provider assessment nearing a year old
Related Services















