Recorded scope and limits
Read PCI SSC FAQ 1115, dated June 2012, for the distinction between connected-system scope and the requirements applicable to an individual system. Used with the current glossary to correct the guide’s misleading three-state shorthand. This source does not determine any entity’s scope, validate segmentation or establish compliance. Checked October 29, 2026.
Use the task guides below to see how this source informs a labeling decision. Check the publication scope and the edition adopted by your project before applying it. A publisher overview is not the full text of a standard, and software documentation does not prescribe a physical label format.
Read the library’s edition and applicability notes.
What this source establishes
Connected-system scope and per-system requirement applicability are different questions. The entity’s actual scope decision remains outside this labeling exercise.
Review date: 2026-10-29. This note describes the source scope; it is not a project approval.
Used in these planning guides
Used in these guides
The linked planning guides explain the specific statements supported by this source. Their trial methods and fictional cases are editorial examples.