Nov 18th, 2026

Your Vendor Is PCI Compliant. So Whose Problem Is the Rest?

TL;DR

PCI SSC issued new guidance on third-party service providers. A vendor AOC is useful but does not replace determining which services are covered, documenting customer and provider responsibilities, obtaining applicable evidence, and monitoring TPSPs. Requirements 12.8 and 12.9 work together; governance must be ongoing.

Your Vendor Is PCI Compliant. So Whose Problem Is the Rest?

Your payment gateway has an Attestation of Compliance. Your hosting provider says it takes security seriously. Your managed service provider has a security page with enough badges to decorate a Christmas tree. So your PCI program is covered, right?

Not quite. A vendor's compliance status is not a magical force field around your business. And the PCI Security Standards Council just published a timely reminder that the work of understanding third-party service providers does not end when somebody emails you an AOC.

On November 10, 2026, the PCI SSC announced a new information supplement, Understanding PCI DSS Service Providers. It addresses questions about third-party service provider (TPSP) relationships, including who qualifies as a TPSP, how responsibilities are allocated, what evidence customers should expect, and how ongoing monitoring works. The supplement is guidance, not a replacement for the PCI DSS requirements. But its message should sound familiar to anyone who has been through an assessment: outsourcing a service does not mean outsourcing accountability for understanding it.

The AOC Is a Starting Point, Not a Permission Slip

An Attestation of Compliance can be valuable evidence, but it is not a universal certification that every service the provider offers, every configuration you use, and every control you depend on is covered. Before you put an AOC in your evidence folder and declare victory, ask what services were assessed, which environments are included, whether the document is current, and which requirements the provider actually performs on your behalf.

Consider an ISV that relies on a gateway for payment processing and a cloud provider for infrastructure. The gateway may protect cardholder data within its assessed services. The cloud provider may maintain security controls for its platform. Neither fact, by itself, answers who configures access, monitors relevant logs, manages application vulnerabilities, or documents the customer's own security responsibilities. Those answers depend on the service, architecture, and agreed division of work.

A good PCI program connects evidence to the actual services in use. It does not collect certificates like baseball cards and hope the QSA never asks a follow-up question.

Requirements 12.8 and 12.9 Are Supposed to Work Together

The Council's announcement emphasizes two connected requirements. Under PCI DSS Requirement 12.8, customers using TPSPs must manage and monitor those relationships. That includes maintaining a list of providers, written agreements, due diligence before engagement, monitoring compliance status at least once every 12 months, and documenting which requirements belong to the provider, the customer, or both.

Requirement 12.9 addresses the other side of the relationship. A TPSP must acknowledge its responsibility to customers in writing and support customer requests for information about its PCI DSS responsibilities and compliance status. Those two requirements are complementary. A customer cannot reasonably manage a provider relationship without useful information from that provider, and a provider's documentation cannot replace the customer's own governance process.

This is where many programs get uncomfortable. Procurement has the contract. Security has the AOC. Compliance has a spreadsheet. Engineering knows what the provider actually does. Unfortunately, none of those people may have compared notes.

Who Counts as a Service Provider? More Than the Obvious Names

Payment processors and gateways are easy examples. The harder questions often involve providers whose services can affect the security of a cardholder data environment even when they do not directly process card payments. The Council specifically calls out examples such as managed network services, remote administration, hosting, and backup services when discussing what it means to impact security.

That does not mean every vendor automatically becomes a TPSP. It means organizations need to evaluate the service's actual access and influence, rather than decide based on the vendor's marketing category. The new supplement includes a decision flow to help with that determination and examples of services that generally do or do not impact security.

A vendor that can administer a relevant firewall or access systems in scope may have a very different PCI relationship than a vendor delivering office supplies. The distinction should be based on what the vendor can do, not what its sales deck says.

The Responsibility Matrix Is Where the Truth Comes Out

One of the most practical exercises in PCI governance is documenting responsibility requirement by requirement. For each relevant control, identify whether your organization performs it, the provider performs it, or both have work to do. Then identify the evidence that demonstrates each party's contribution.

Shared responsibility is not a polite way of saying 'somebody else probably handles it.' For example, a hosting provider might secure the underlying infrastructure while the customer remains responsible for application configuration and user access. The exact split depends on the contracted service and implementation. A useful matrix names owners, clarifies boundaries, and identifies the evidence each party must produce.

The Council also addresses multi-tenant and nested service providers. Administrative control matters in distinguishing multi-tenant service providers, and a provider may depend on another provider to deliver part of its service. That layered relationship makes it especially important to understand where responsibilities sit. A familiar vendor name at the top of the contract does not necessarily tell you who operates every relevant control underneath it.

Monitoring Once a Year Is a Floor, Not a Strategy

Requirement 12.8 calls for monitoring TPSP PCI DSS compliance status at least every 12 months. That minimum matters, but effective governance should also respond when the relationship changes. A new integration, a revised service, an acquisition, expanded administrative access, or a change in how payment data flows can alter the responsibilities you thought were settled.

Treat third-party oversight as a lifecycle, not a once-a-year scavenger hunt for PDFs. The Council's new guidance outlines seven steps for TPSP management, including identifying providers, determining security impact, documenting responsibilities, and monitoring compliance status. In practice, that means assigning an owner for each provider, tracking evidence expiration, reviewing material changes, and making sure the teams using the service understand the controls they still own.

If your PCI vendor inventory lives in a spreadsheet last updated before your last product launch, you may have a governance problem hiding in plain sight.

What to Ask Your Vendors Before Your Next Assessment

Start with five practical questions. First, which specific services we use are covered by your PCI assessment? Second, which applicable PCI DSS requirements do you perform, and which remain ours? Third, what current evidence can you provide to support those responsibilities? Fourth, do you rely on other service providers for relevant controls, and how is that dependency managed? Fifth, how will you tell us when a material change affects your service or our responsibilities?

The answers should make their way into your contracts, provider inventory, responsibility matrix, and assessment evidence. If the answers are vague, do not wait until assessment week to discover the gap. Escalate it while there is still time to resolve it.

Your Vendor Can Help You Comply. It Cannot Understand Your Business for You.

The new PCI SSC supplement is useful because it brings attention to a problem that is rarely solved by buying another security product: unclear ownership. Organizations can have capable, compliant vendors and still struggle with PCI because nobody has connected the vendors' responsibilities to the organization's own controls.

At Payments Therapist, we see third-party governance as part of an operating PCI program, not a document-collection exercise. Our PCI Governance as a Service approach helps organizations keep scope, responsibilities, evidence, and vendor oversight aligned throughout the year instead of rebuilding the picture every assessment season.

Your vendor's AOC matters. Your contracts matter. Your responsibility matrix matters. But the most important question is still the simplest: when a control needs to be performed, can you say exactly who owns it and prove that it happened?

Because 'we thought the vendor handled that' is not an especially compelling answer when the assessor asks for evidence.

Sources