FREE FIELD GUIDEProvider responsibilities · 8-minute working session
thrivePCIAll training →

A USEFUL START, AVAILABLE FREE

The service behind
the provider name.

A provider’s name and a current compliance document can be useful starting points. The real review asks whether the service you use, its assessed coverage, the responsibility split, and your own retained work line up.

A practical worksheet · PCI DSS v4.0.1 references · No signup required

A CLEARER PROVIDER REVIEW
01service
02coverage
03responsibility

THE 4-PART ALIGNMENT CHECK

Trace the service to the work.

01 · Define

What do you actually use?

Name the specific product, service, options, environment, and activities in your arrangement. A company may offer multiple services with different coverage.

02 · Correlate

What does the status record cover?

Check the applicable validation or compliance status record and confirm its service scope and period. Do not assume a provider’s general status automatically covers every product.

03 · Map

Who performs each activity?

Use service-specific responsibility information to identify provider-managed, customer-managed, and shared activities. Resolve missing or unclear entries with the provider.

04 · Retain

What evidence stays with you?

Record your own configurations, decisions, monitoring, and follow-up. Outsourcing a service does not automatically establish that customer responsibilities are complete.

A SHORT PRACTICE CASE

One provider. Two services. One gap.

A fictional organization’s provider status record names its hosting service. The organization also buys an optional managed monitoring service. The responsibility document describes hosting but says nothing about the optional service.

Good next step

Keep the question open. Identify the consumed optional service and relevant activities, request current service-specific coverage and responsibility information, and assign an owner to reconcile the response with the organization’s retained work.

Do not conclude that the hosting document covers the optional service without evidence.

KEEP THE REVIEW CONCRETE

Capture one row per service.

Service and relevant options: ______________________________________________

Status record, scope and period: __________________________________________

Provider-managed activities: ______________________________________________

Customer-managed activities: _____________________________________________

Shared activities and coordination: ________________________________________

Evidence we retain: _____________________________________________________

Open question, owner and follow-up date: ___________________________________

Source boundary. PCI DSS v4.0.1 requirements 12.8.3–12.8.5 address due diligence, ongoing status monitoring, and responsibility information. Requirement 12.9.2 adds a requirement for service providers to support customer requests for compliance status and responsibility information. Apply the standard’s specific language and applicability to the actual arrangement; this worksheet does not determine scope or compliance.

GO DEEPER WHEN YOU’RE READY

From a checklist to a repeatable provider review.

The planned Provider Responsibilities course expands this method with a worked mapping example, an oversight cadence, practice scenario, knowledge check, and owner-recorded narration script.

The complete course is still in draft review. No paid course is available for purchase or playback yet.

Explore the training library →