# PCI SSC FAQ 1115: connected systems and assessment scope

> 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.

Canonical page: https://datacenterlabeling.com/references/s81

Original source: [PCI SSC FAQ 1115: connected systems and assessment scope](https://www.pcisecuritystandards.org/faqs/1115/)

## Scope of this source

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.

Connected-system scope and per-system requirement applicability are different questions. The entity’s actual scope decision remains outside this labeling exercise.

Source review: 2026-10-29.

Rackstamp provides editorial field guidance. IDs, cases, and worksheet entries are fictional examples unless identified otherwise. Distinguish local conventions from adopted standards. Source notes describe the evidence scope; a linked overview is not the full standard or a project approval.

## Related guidance

- [Label the PCI DSS scope boundary so the room matches the diagram](https://datacenterlabeling.com/guides/labeling-for-pci-dss-scope)