UNLISTED REVIEW EDITIONTranche T1 · Three request lessons · Draft for Scott
thrivePCISite v0.43.62+20261122T201000Z · Published November 22, 2026

THRIVEPCI · EVIDENCE REQUEST CURRICULUM · T1 · DRAFT 0.1.0

Read the request.
Build a traceable response.

Three governing-document requests teach three different evidence habits: reconcile diagrams to the environment, maintain useful inventories, and record scope confirmation as work that repeats and responds to change.

D-04Diagrams
D-05Inventories
D-08Scope confirmation
Review status: new lesson draft based on the three supplied request documents. The documents describe requested evidence and assessor procedures; they contain no actual entity diagrams, inventory records, or scope-review results. Exercises below are fictional and are not compliance determinations. This page is unlisted and noindex, but is not access-controlled.

LEARNER COMPANION · EDITABLE DOCX

Practice alongside the lessons

Three lessons: network diagrams, inventories, and scope confirmation. This workbook is based on the published lesson decks; it does not include the original mock-engagement request documents.

RECORDING EDITIONS · THREE EDITABLE PPTX DECKS

Download a lesson to prepare narration

Each deck has six slides, the Forest Zen bamboo-and-waves theme, and an owner narration script in speaker notes. No audio or video has been recorded. These are review drafts; source request documents are not included in the downloads.

A REUSABLE EVIDENCE WORKFLOW

Request, artifact, conclusion

Keep these separate. A request defines what to provide. An artifact is what the entity actually provides. A conclusion follows assessor procedures and the applicable scope; a training exercise cannot decide it.

01

Decode

Identify requested subject, age, owner, format, and the questions the evidence is meant to support.

02

Trace

Connect each statement to a source, custodian, system record, section, and any limit or gap.

03

Check

Compare the artifact to current records and configuration. Record the evidence age in days where useful.

04

Index

Give each file a stable name and record title, version, owner, approval details, and sections answered.

REQUEST D-04 · NETWORK AND DATA-FLOW DIAGRAMS

Diagrams must describe the environment people operate

Requested owner role: network architect · Nine listed testing procedures · Six sub-requirements · PCI DSS v4.0.1 source mapping appears in the request.

What the request asks for

A current network diagram showing connections into and out of the cardholder data environment and security-impacting systems, plus data-flow diagrams for account-data flows. The request also maps diagram evidence to configuration reviews, records, and interviews.

Exercise · A missing connection

In a fictional change note, a new alert relay can call a payment service. The latest diagram does not show it. No traffic capture or account data is supplied.

  1. List the exact facts and records you need before updating the diagram.
  2. Identify which roles or configuration sources can corroborate the connection.
  3. Explain how you would index the revised diagram and show its use.
  4. State what the diagram alone cannot establish.

Debrief

Record the source change, endpoints and direction, relevant system roles, any account-data flow, the diagram version and owner, and the configuration or interview sources used to verify accuracy. Cross-reference each requested sub-requirement in the file index. A diagram is not configuration proof by itself; do not infer that an unshown flow does not exist.

Freshness practice: label the diagram “42 days since last confirmed” only as an exercise value. If a later change exists, note that relationship even when the age seems low. Do not decide adequacy from age alone.

Source map and assessor-use cues

The request maps procedures 1.2.3.a–b, 1.2.4.a–b, 1.3.3, 1.4.1.a–b, 1.4.4.a, and 11.5.1.a. Its listed methods include examining documentation and configuration, records, and interviewing responsible personnel. Treat this as a request-supplied map; confirm applicability and wording against the assessment source.

REQUEST D-05 · INVENTORIES

An inventory needs a clear purpose and reliable source

System components, software, keys and certificates, scripts, devices, and cipher suites · Requested owner roles: asset and platform owners · Eleven listed testing procedures.

What the request asks for

Maintained inventories with an owner, last update, and source system. The request spans multiple inventory subjects, including in-scope components and their functions, software components, trusted keys and certificates, payment-page scripts, electronic media, and authorized wireless access points.

Exercise · One inventory, two gaps

A fictional inventory lists a retired payment-page script as active. A current configuration shows a different script that is absent from the inventory. The key and certificate register has a recent date, but no evidence explains whether every relevant item is covered. Secret values are not provided.

  1. Separate the two inventory discrepancies.
  2. For each, name the authoritative source and responsible custodian to consult.
  3. List useful key/certificate metadata without exposing secret material.
  4. Record evidence age in days and identify what the age does not tell you.

Debrief

Reconcile the retired and newly observed scripts to the approved inventory process and the relevant current configuration. Preserve the mismatches and their sources in working notes; do not silently overwrite them. For keys and certificates, use non-secret identifiers, purpose, owner, lifecycle status, and source reference as allowed by the organization. Never include key material or tokens.

Inventory age is a clue for follow-up, not evidence that coverage is complete. For each inventory, identify its population boundary, inclusion rule, source, owner, update history, and what was compared. Follow the request’s specific handling and sampling direction.

Source map and assessor-use cues

The request maps procedures 4.2.1.1.a–b, 6.3.2.a–b, 6.4.3.b, 9.4.5.a–b, 9.4.5.1.a–b, 11.2.2, and 12.5.1.a. Its methods include examining documentation, records and configuration, interviewing personnel, and sampling from populations. Its source list spans seven sub-requirements; applicability and population boundaries still require assessment context.

REQUEST D-08 · SCOPE DOCUMENTATION AND CONFIRMATION RESULTS

Scope confirmation is recurring work and change response

Requested owner role: compliance lead · Eleven listed testing procedures · Seven sub-requirements, including procedures explicitly marked in the request as service-provider-only.

What the request asks for

Documented scope, including locations, flows, systems, segmentation, and third parties, together with results of scope confirmations in the relevant period. The supplied excerpt distinguishes annual review under 12.5.2, six-month review for the marked service-provider procedures, and quarterly review under A3.2.1. Significant changes also trigger review where the applicable procedure says so. Verify applicability before using a cadence.

Exercise · Review exists, change does not

A fictional scope review record is 94 days old. A significant network change has a completed change ticket, but the file set has no linked scope-impact review. The organization’s assessment type and specific control applicability have not been established.

  1. Identify the review records and change evidence needed to follow up.
  2. Separate recurring review cadence from change-triggered review.
  3. Flag the applicability question before using any service-provider or appendix procedure.
  4. Describe the next evidence request without assigning a compliance result.

Debrief

Trace the recorded review to its scope inputs, participants, decisions, unresolved items, and communication. Link the change record to an impact review and updated scope artifacts where the source process requires them. Ask what assessment context makes each mapped procedure applicable before treating the request list as a conclusion.

The 94-day age is only a fictional prompt. Compare age and event chronology with the applicable source and engagement requirements; do not turn the exercise value into a general threshold. The missing link is a question to resolve, not a finding by itself.

Source map and assessor-use cues

The request maps 12.5.2.a–b, 12.5.2.1.a–b, 12.5.3.a–b, A3.2.1.a–b, A3.2.2, A3.2.2.1, and A3.2.3. Its source text labels some procedures as service-provider-only or Appendix A3.2. Confirm assessment type, scope, and applicable source text before teaching a requirement as applicable.

TRANCHE T1 · INTEGRATED EXERCISE

Prepare three responses without collapsing them into one claim

A fictional team has a diagram with an unexplained connection, an inventory with mismatched entries, and a scope review that predates a significant change. Build a short response plan for D-04, D-05, and D-08.

Learning check: Can another reviewer follow each request item to a specific source, understand its age and limitation, and see what remains unresolved?

Return to the full practice catalog