← ClaudeAtlas

pci-dss-assessmentlisted

Use when assessing PCI DSS compliance for systems that store, process, or transmit cardholder data — scoping the CDE, selecting the SAQ type, validating segmentation, and tracking the 12 requirements. Triggers on "PCI DSS", "cardholder data", "CDE", "SAQ", "ROC", "ASV scan", "PCI 4.0", "tokenization".
noctua84/nescio-ai · ★ 0 · DevOps & Infrastructure · score 73
Install: claude install-skill noctua84/nescio-ai
# PCI DSS Assessment ## Purpose Create a PCI DSS assessment that delivers actionable, measurable results. **Category**: Cybersecurity & Information Security ## Inputs ### Required - **Objective**: What you want to achieve with this deliverable - **Context**: Relevant background information (systems, scope, environment) ### Optional - **Constraints**: Any limitations or requirements to consider - **Existing Work**: Previous documents or data to build on ## Context Before starting, read the repo's `CLAUDE.md` and any relevant notes under `memory/` (e.g. `memory/repo/<repo>/`, `memory/feedback/`) for prior decisions and constraints. ## Process ### Step 1: Context & Research - Review any existing pci dss assessment documents in the project - Identify key stakeholders and their requirements - Select the most appropriate framework: PCI DSS 4.0, PCI SSC SAQ Types, PA-DSS ### Step 2: Analysis & Framework Application - Apply the selected framework to structure the pci dss assessment - Identify gaps, opportunities, and risks - Define success metrics: Requirement Compliance Rate (12 Requirements), SAQ/ROC Completion Status, ASV Scan Pass Rate, Segmentation Validation Results - Document assumptions and dependencies - Validate approach against industry best practices ### Step 3: Build the Deliverable - Structure the pci dss assessment using the output format below - Include specific, actionable recommendations — not generic advice - Add concrete numbers, timelines, and benchma