# Source map and claim register

| Lesson claim | Source | Location/use | Reviewer check |
|---|---|---|---|
| Scope is documented and confirmed at least every 12 months and upon significant change to the in-scope environment. | PCI DSS v4.0.1 Requirements and Testing Procedures, supplied authoritative DOCX; PCI SSC Document Library: https://www.pcisecuritystandards.org/document_library/?class=pcidss&doc=pci_dss | Slides 2 and 7, narration, handoff scenario | Confirm exact text, notes, and requirement numbering against supplied DOCX |
| Scope-validation minimum elements include payment flows/channels, account-data locations, system components, segmentation, and third-party connections. | PCI DSS v4.0.1, Requirement 12.5.2 | Slide 3 and narration | Confirm wording and whether the lesson's paraphrase preserves the full requirement |
| Significant-change examples are contextual; significance depends on the environment/configuration. | PCI SSC FAQ 1317: https://www.pcisecuritystandards.org/faqs/1317/ | Slide 4 and narration | Confirm FAQ is current and examples match the cited version |
| After a significant change, applicable requirements are confirmed on new/changed systems and networks; documentation is updated as applicable. | PCI DSS v4.0.1, Requirement 6.5.2 | Slide 7 and narration | Confirm exact completion timing and notes in supplied DOCX |
| Hosted payment pages or provider tokens alone do not establish scope result. | Instructional inference from the need to evaluate actual flows/configuration; no standalone scope claim is asserted. | Fictional exercise, slides 5 and 8 | Confirm phrasing does not imply a categorical scope result |

No direct quotations from PCI SSC publications are used. Paraphrased statements remain subject to Scott's technical review.
