# Six Zones, Four Boundaries — source analysis and review notes

**Package:** ThrivePCI Course 07, draft 0.1.1+20261119T165029Z
**Source set:** RA-001 v1.5 (Markdown), GDE-001 v1.2 (DOCX), and TRN-001 v1.2 (PPTX)
**Disposition:** Adapted into a ThrivePCI-branded training draft. Technical review by Scott remains open.

## What the source set teaches well

The materials have a coherent instructional spine: classify systems by their relationship to account data and CDE security; draw the network and account-data flows; document allowed connections; describe claimed out-of-scope paths; and compare the resulting artifacts with segmentation evidence. The guide is practical and the deck uses a progressive reveal that supports owner-recorded narration. The variants for cloud, multi-tenant service providers, and merchants show where architecture changes the discussion.

## Source alignment and editorial findings

| Finding | Evidence in the supplied set | Course treatment |
|---|---|---|
| Boundary count can confuse learners | The title says four boundaries, while NSC-1, NSC-2, NSC-2a, and NSC-3 are all shown. NSC-2a is described as intra-CDE. | Explain NSC-2a as a nested sub-boundary within NSC-2 in this teaching model. A real design can have a different number of logical controls. |
| Practitioner choices and standard language are blended | The source recommends tokenization at the first CDE hop, a particular egress gateway, a dedicated CDE directory, and “no route” examples alongside PCI DSS citations. | Label them as scenario or practitioner design choices. PCI DSS applicability and exact scope conclusions must follow the standard and actual architecture. |
| Scope labels could look automatic | The six zones are vivid, but their labels can be mistaken for an official PCI SSC taxonomy or a substitute for component-by-component analysis. | State that the zones are an independent teaching map; components require evidence-based classification under PCI DSS. |
| Deny identifiers drift | The deck refers to D3/D4 in one note while surrounding material uses D-01 through D-06; D-07 also appears before D-06. | Call out the mismatch and require one controlled register whose IDs agree across diagram, register, and test records. |
| Monitoring statement needs attribution | The source recommends detection coverage at the scope boundary by reading “critical points” guidance into NSC-3. | Present this as the source author’s practitioner interpretation, not an unqualified universal rule. Scott should verify the exact PCI DSS text and intended statement before recording. |
| Frequency claims vary by applicability | Annual and six-month segmentation or scope-confirmation intervals are discussed for different populations. | Avoid generalizing service-provider-specific timing. The applicable requirement and organization type determine the interval. |
| Payment-page classification depends on function | The source distinguishes a page handling/transmitting PAN from a page that only delivers an iframe container. | Preserve the conditional language and avoid one-size-fits-all CDE claims. |
| Attribution and status are important | The source identifies the framework as a practitioner model, not a PCI SSC publication, and limits attribution of opinions. | Keep that boundary in the course and companion guide. Confirm any brand, byline, and source-distribution rights before external redistribution. |

## Course structure

The 14-slide sequence moves from outcomes and scope categories into the six-zone map, the nested boundary convention, payment and shared-service flows, administrator paths, segmentation claims, flow/deny registers, variants, artifact cross-checking, and a single learner action. Every speaker-note script is owner-recording copy; it is not prerecorded audio. Slides cite PCI DSS sections and requirements at a high level for Scott’s technical verification.

## Open review items for Scott

1. Verify each requirement and applicability note against the authoritative PCI DSS v4.0.1 Requirements and Testing Procedures source and current program materials.
2. Decide whether the title’s “four boundaries” convention is the clearest treatment for NSC-2a, or whether the title/model should be revised.
3. Resolve the source register’s deny IDs and confirm the model’s interpretation of the scope boundary, detection coverage, and service-provider intervals.
4. Confirm the accuracy of the cloud, merchant, multi-tenant, payment-page, and authentication examples for the intended learner audience.
5. Approve attribution, licensing, and whether any source figures may be adapted or redistributed. No source illustration is reproduced in this first ThrivePCI deck.
6. Record the narration from the supplied speaker notes, then return the exported MP4 for captions, playback, accessibility, and publication review.

## Limits

This draft is an educational aid. It does not determine an entity’s scope, control applicability, validation path, compliance status, or assessment result. Its technical citations are not a substitute for Scott’s source review. No narration has been recorded and no audio/video playback is available yet.


## Visual revision 0.1.1

The trainer deck now follows the established ThrivePCI Forest slide system: approved light and dark backgrounds, Poppins typography, the Forest palette, the approved cover and wordmark, and the established transparent upper-right corner leaf on every content slide. The light/dark corner-leaf PNGs and botanical SVG masters are included with provenance notes. The 14-slide PPTX and PDF were rendered and visually reviewed against the slide images. The learner guide was carried forward unchanged from v0.1.0.
