PCI scope
The set of systems that PCI DSS applies to: every system that stores, processes or transmits card data, plus anything connected to or able to affect them.
In more detail
The core of the scope is the cardholder data environment, or CDE. Scope spreads silently when card numbers leak into logs, support tickets or chat tools, which pulls those systems in too. The cheapest way to comply is to shrink scope: segment card systems onto their own network, tokenise so most systems never see a real number, or send payments to a hosted payment page.
Example
line 2: 411111******1111 card number # the ticketing system is now in scopeRelated terms
- PCI DSS — The Payment Card Industry Data Security Standard, the security rules every organisation that stores, processes or transmits payment card data must follow.
- segmentation — Dividing a network into separate zones with controlled paths between them, so a problem or attacker in one zone cannot freely reach the others.
- tokenization — Replacing a sensitive value with a meaningless token and keeping the mapping in a separate, protected system.
- scope — The boundary that says exactly which systems, locations, services or activities an audit, certificate, test or requirement covers.
Taught in
- Regulatory Compliance: SOC 2, HIPAA, GDPR & PCI-DSS — Cybersecurity Fundamentals, GRC & Cryptography