PUBLIC REVIEW EDITIONOwner validation in progress · no engagement-specific dates
thrivePCISite v0.43.62+20261122T201000Z · Published November 22, 2026

THRIVEPCI · CADENCE ATLAS

Let each activity
keep its own time.

A calm, source-linked starter for separating fixed intervals, event triggers, permitted risk-analysis frequencies, and internal planning rhythms. Use the worksheet to build your own owner-and-evidence schedule.

Workbook v0.4.0 uses a corrected, versioned PCI DSS source corpus, including the restored testing procedure for 9.4.1. The March 31, 2025 phase-in has elapsed: applicable requirements and specified bullets are now effective. Requirements 6.4.1, 8.3.10 and 10.7.1 are superseded; their current successors are 6.4.2, 8.3.10.1 and 10.7.2. Historical mappings remain visible with lifecycle notes. The 277-ID source ledger and formula-driven currency planner remain available for owner applicability review.

Separate winding water channels pass through green hills and meet at a shared pond near a small pavilion. Conceptual metaphor for coordinating distinct activity timing; no required frequency is shown.

COORDINATE THE PORTFOLIO

One calm view. Many activity clocks.

Use a shared planning view to see dependencies while each activity retains its own requirement-defined timing, event triggers, and owners.

A CALM, FORMULA-LED WORKFLOW

Set the anchor. Let each request find its window.

Warm gold marks dates you enter. River blue marks linked and calculated dates. The Forest palette, sage surfaces, and restrained Georgia headings carry the workbook theme into a practical planning tool.

01 · SET A DATE

Choose each anchor

Enter a Due By date for T1–T5 and an owner-selected start date for Fieldwork. No mock engagement dates are carried into the workbook.

02 · CALCULATE

Count the window back

Tranche currency day counts come from the supplied index. The workbook calculates when each request’s window opens and closes on its Due By date.

03 · REVIEW

Check an evidence date

Add the date evidence was last refreshed. The planner calculates its age and shows whether it falls within the window. Fieldwork day limits are owner-set because none were supplied.

A SIMPLE CLASSIFICATION

Start with the rule, then put it on a calendar.

Do not infer one universal PCI DSS rhythm. The applicable requirement tells you whether timing is fixed, event-triggered, or may be established through a targeted risk analysis. Your internal meeting schedule helps coordinate work, but it does not replace the underlying control activity.

Requirement-defined

Record the interval stated by the applicable requirement and testing procedure, plus any named trigger.

Event-triggered

Track the event separately so a regular calendar reminder does not hide a change-triggered obligation.

TRA-defined, when permitted

Use a documented targeted risk analysis only where the requirement explicitly permits it. Do not use a TRA to replace a fixed interval.

SELECTED EXAMPLES

A few different clocks, side by side.

These examples are selected for teaching and are not a complete requirement inventory. The six-sheet formula-led workbook maps all 74 supplied evidence and fieldwork requests to 729 requirement rows, with a 69-clause timing-signal register, and a deduplicated source screen of all 277 mapped requirement IDs, alongside request-level currency windows. Source reconciliation is complete; owner applicability and extracted timing signals remain for Scott’s review. The examples below have been checked against the supplied PCI DSS v4.0.1 Requirements and Testing Procedures document.

ActivityTiming basisKeep visible
NSC configuration review · 1.2.7At least once every six monthsReviewed rule-set/configuration, owner, exceptions and follow-up
Specified log review · 10.4.1Daily, for the specified event and system categoriesApplicable log sources, anomalies, investigation and disposition
Data-flow diagram maintenance · 1.2.4Update as needed when the environment changesChange trigger and a current, accurate diagram
Internal and external vulnerability scans · 11.3.2At least every three months; schedule as close to three months apart as possibleScope, scan report, remediation, rescan and significant-change trigger
User account and privilege review under 7.2.4At least once every six monthsPopulation, appropriateness, remediation, management acknowledgement
Application and system account review under 7.2.5.1Frequency established by a targeted risk analysisPermitted TRA basis, review record and resulting action
Security awareness training · 12.6.3Upon hire and at least once every 12 monthsCovered personnel, completion and acknowledgements
Incident response plan review and test · 12.10.2At least once every 12 monthsReview, test coverage, outcomes and follow-up
PCI DSS scope confirmation · 12.5.2At least once every 12 months and upon significant changeScope review population, boundaries, providers and decisions

Source and applicability boundary. The examples on this page were checked against the user-provided PCI DSS v4.0.1 Requirements and Testing Procedures document (June 2024), including requirement IDs 1.2.4, 1.2.7, 7.2.4, 10.4.1, 11.3.2, 12.5.2, 12.6.3, and 12.10.2. The workbook is a review edition, not an approved assessment schedule. Its timing register includes candidate signals and clauses requiring validation; a missing match does not prove that no timing obligation exists. Confirm applicability, entity type, testing procedures, and assessment instructions in the current authoritative standard and PCI SSC guidance before use.

A NOTE ABOUT THE OTHER KIND OF FREQUENCY

Sound can set a mood; Hz is not a shortcut.

The companion music study uses A4 = 440 Hz as its interoperable tuning reference. A separate 432 Hz tuning is available to compare as an artistic choice, not as a proven universal calming frequency. Arrangement, tempo, timbre, dynamics, and listener preference matter more than a single reference pitch.

Open the sound identity review (opens in a new tab)