pci-dss-scoping
Scope a PCI DSS environment correctly — cardholder data flows, segmentation validation, and requirements mapping for compliance. Use when preparing for PCI DSS v4.0 assessments.
v2026.8.26-b2b6b523 instalaciones+3 en 7 días0 Estrellassincronizado hace 19 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install securityskills/pci-dss-scopingEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paqueted7dbce0c…b0de934e
d7dbce0c3aa0…b2fdb0de934e1 archivo · 1.3 KBEscaneoMedio1 hallazgo
- No se encontró licencia
Fuentegithub.com/securityskills/skills/tree/main/compliance/pci-dss/pci-dss-scoping@b2b6b52
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
Correct scoping is 80% of PCI DSS. Get the data flows right first.
1. Find the Cardholder Data
- Trace the full payment path: capture → transmission → processing → storage → destruction
- PAN storage locations: databases, logs (log scrubbing!), backups, email/ticket systems, dev/test environments
- Verify truncation/masking everywhere PAN appears; confirm no SAD (sensitive auth data) persistence post-authorization
2. Define the CDE
- Cardholder Data Environment: all systems that store/process/transmit CHD, plus connected systems
- Identify connected-to systems: security-impacting (shared services like AD, DNS, NTP, monitoring) and security-impacting-or-not based on their ability to impact CDE security
- Everything with potential CDE connectivity is in scope until segmentation is proven
3. Segmentation (the scope killer)
- Document segmentation controls: firewalls, network access control, separate credentials/privileged accounts for CDE
- Segmentation penetration test is mandatory (v4.0): verify from out-of-scope zones that CDE boundaries hold, both directions
- If no segmentation: entire network is the CDE. Usually more expensive than segmenting.
4. Requirements Mapping (v4.0 highlights)
- Req 1/2: network controls, secure configurations (now with defined "defined approach" targets)
- Req 3: protect stored account data; cryptography inventory and key management (3.6/3.7 expanded)
- Req 4: strong cryptography in transit — new in v4.0: PAN over open networks needs rendering unreadable (4.2.1)
- Req 8: MFA for all access into CDE (8.4 expanded beyond admin)
- Req 10/11: logging + testing; targeted risk analysis for customizing frequencies (11.3.x)
- Req 12: policy, third-party/service provider management, customizes approaches documented
5. Evidence Preparation
- ASV scan reports, internal/external pentest reports, segmentation pen test
- Quarterly scans, configuration standards, key management records, training logs
- compensating controls worksheet for any "not applicable" requirements
Output
Data-flow diagrams, scope document with in/out-of-scope justification, segmentation test plan, and a requirements evidence matrix.
Archivos de esta versión
- SKILL.md2.4 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
- MediaLicencia · No se encontró licencia
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.8.26-b2b6b52 | 13 nov 2026 | b2b6b52 | d7dbce0c | Firmada | – |
Más de securityskills
Todo de este publicadorMás en Informes y cumplimiento
Ver la categoría- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login