FREE FIELD GUIDE · COURSE 06 PREVIEWNo signup · Print friendly
thrivePCIAll training →

THE ZEN OF PCI · A PRACTICAL FIELD GUIDE

Keep the program moving.

A prior assessment is a point in time. Your program continues through changing services, assigned owners, scheduled activities, evidence, and decisions. This worksheet helps you keep those threads visible between assessment engagements.

Go to the continuity worksheet

A SMALL, REPEATABLE PRACTICE

Make the next action easy to see.

01

Notice change

Surface new services, providers, payment flows, systems, ownership, and operating conditions.

02

Check the basis

Look up the exact applicable requirement, its frequency, and any permitted analysis or applicability conditions.

03

Keep the trail

Record who acts, what evidence exists, where it lives, and which questions still need an authorized decision.

TIMING HAS A SOURCE

Keep the basis beside the date.

These examples help organize work. They are not a complete requirement list or a substitute for applicability analysis. Confirm exact wording in PCI DSS v4.0.1 and current engagement instructions.

Program activityExample timing basisUseful continuity record
Review information security policyRequirement 12.1.2 specifies review at least once every 12 months and updates as needed to reflect changes to business objectives or risks to the environment.Approved policy version, review date, participants, changes, and follow-up.
Confirm entity scopeRequirement 12.5.2 specifies at least once every 12 months and after significant change. Requirement 12.5.2.1 adds a six-month frequency for service providers, alongside significant changes.Scope method, systems and flows considered, accountable reviewer, results, and unresolved items.
Review third-party provider statusRequirement 12.8.4 specifies monitoring the provider’s PCI DSS compliance status at least once every 12 months.Provider, service, status evidence, date checked, gaps, and owner follow-up.
Maintain responsibility informationRequirement 12.8.5 calls for information about which requirements are managed by each provider and which are managed by the entity to be maintained.Current responsibility information, source, version/date confirmed, and open coordination questions.

Keep these ideas separate: an internal check-in schedule is a coordination choice. A required frequency comes from the applicable requirement. A targeted risk analysis only affects timing where the specific requirement permits it and the analysis meets its conditions.

PRINTABLE CONTINUITY WORKSHEET

Leave the next owner a clear trail.

Use one row per activity. Record facts and evidence separately from assumptions or decisions that need the right authority.

Activity / requirementTiming basis and next dateOwner and backupEvidence locationGap, decision, or next action

Before you hand this over

  • Which entries rely on a specific requirement, and have you checked that requirement’s actual timing?
  • What changed since the last review, and who has authority to assess the impact?
  • Can the next owner locate the evidence and identify what remains unresolved?

This educational worksheet does not determine PCI DSS scope, compliance, provider responsibility, or assessment outcome. It does not replace required records, formal analyses, or instructions from the organization’s assessor.

THE COURSE 06 PREVIEW

Build habits that carry through the year.

The full draft course explores operating routines, change review, timing, evidence, and program continuity. It remains in private review and is not available for enrollment or playback.

Explore the training library