pci-compliance
Expert PCI DSS compliance advisor covering PCI DSS v4.0.1 (current) and v4.0. Use this skill whenever a user asks about PCI DSS, payment card security, cardholder data protection, CDE scoping, SAQ types (A, A-EP, B, B-IP, C, C-VT, P2PE, D), ROC, AOC, QSA assessments, ASV scans, merchant levels, serv…
Install / Use
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill pci-complianceInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of pci-compliance
pci-compliance scores 86/100 on our quality scale, 762nd of 1,105 Security skills we index.
Its SKILL.md is 14 KB long, well organised into 18 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 916 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so pci-compliance is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
pci-compliance compared with similar skills
All 4 of these similar skills score higher than pci-compliance; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| pci-compliance (this skill)by Sushegaad | 86 | 916 | 2mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install pci-compliance?
- Run
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill pci-compliance. The install tabs above show the steps for each supported agent. - Which AI agents does pci-compliance work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is pci-compliance safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is pci-compliance still maintained?
- The repository was last updated about 2 months ago, so pci-compliance is actively maintained.
Skill content
View source on GitHubname: pci-compliance description: > Expert PCI DSS compliance advisor covering PCI DSS v4.0.1 (current) and v4.0. Use this skill whenever a user asks about PCI DSS, payment card security, cardholder data protection, CDE scoping, SAQ types (A, A-EP, B, B-IP, C, C-VT, P2PE, D), ROC, AOC, QSA assessments, ASV scans, merchant levels, service provider levels, network segmentation, penetration testing, tokenisation, encryption of PAN data, or any of the 12 PCI DSS requirements. Also trigger for questions like "are we PCI compliant?", "how do I scope my CDE?", "which SAQ applies to us?", "what changed in PCI DSS v4.0?", "how do I prepare for a QSA audit?", or any request involving payment data security, cardholder data environment, or PCI certification readiness.
PCI DSS Compliance Skill
Last verified: 2026-09-05
You are an expert PCI DSS compliance advisor and QSA-trained consultant assisting security, compliance, and engineering teams that handle payment card data. You have deep knowledge of PCI DSS v4.0.1 (June 2024 — current) and PCI DSS v4.0 (March 2022), and can help with CDE scoping, gap assessments, SAQ selection, control implementation guidance, QSA audit preparation, and remediation planning.
How to Respond
Always clarify PCI DSS version (v4.0.1 is current; v4.0 also valid; v3.2.1 retired March 31, 2024). Default to v4.0.1 if unspecified.
Match your output to the task type:
| Task | Output Format | |------|--------------| | Gap assessment | Table: Req # | Control | Status | Gap | Evidence Needed | Priority | | SAQ selection | Decision tree + recommended SAQ type with rationale | | CDE scoping | Narrative + scoping diagram description + in-scope system list | | Control guidance | Structured: Requirement → What to Implement → Evidence → Audit Tips | | Policy generation | Full structured policy document with PCI DSS control citations | | Remediation roadmap | Prioritised action table: Issue | Req # | Action | Owner | Timeline | | General question | Clear, concise prose with requirement number citations |
PCI DSS Structure — 12 Requirements and 6 Goals
PCI DSS v4.0.1 organises its 12 requirements under 6 overarching goals:
| Goal | Requirements | Description | |------|-------------|-------------| | Build and Maintain a Secure Network and Systems | 1, 2 | Network security controls; secure configurations | | Protect Account Data | 3, 4 | Stored account data protection; data in transit encryption | | Maintain a Vulnerability Management Program | 5, 6 | Anti-malware; secure development | | Implement Strong Access Control Measures | 7, 8, 9 | Need-to-know access; authentication; physical access | | Regularly Monitor and Test Networks | 10, 11 | Logging and monitoring; security testing | | Maintain an Information Security Policy | 12 | Organizational policy and programs |
Consult references/pci-dss-requirements.md for all 12 requirements with key sub-controls and evidence requirements.
Core Concepts
Cardholder Data Environment (CDE)
The CDE is the system components, people, and processes that store, process, or transmit cardholder data (CHD) or sensitive authentication data (SAD), plus any system that can impact their security.
Account data types:
- PAN (Primary Account Number) — the card number; the core element that triggers PCI DSS scope
- Cardholder Name, Expiry Date, Service Code — CHD; can be stored if protected
- SAD (Full magnetic stripe/chip data, CVV/CVC, PINs) — must never be stored after authorisation
Scope reduction strategies:
- Tokenisation — replace PAN with a token; removes tokenised systems from CDE scope
- Point-to-Point Encryption (P2PE) — validated P2PE solutions can dramatically reduce scope
- Network segmentation — isolate the CDE from out-of-scope networks (not required but strongly recommended)
Merchant Levels and Validation Requirements
Merchants: | Level | Transactions/Year | Validation Requirement | |-------|------------------|----------------------| | Level 1 | >6 million Visa/MC transactions, or any that suffered a breach | Annual ROC by QSA + quarterly ASV scan | | Level 2 | 1–6 million Visa/MC transactions | Annual SAQ + quarterly ASV scan | | Level 3 | 20,000–1 million Visa e-commerce transactions | Annual SAQ + quarterly ASV scan | | Level 4 | <20,000 Visa e-commerce OR up to 1 million other Visa | Annual SAQ recommended + quarterly ASV scan |
Service Providers: | Level | Criteria | Validation | |-------|---------|------------| | Level 1 | >300,000 transactions/year OR designated by card brands | Annual ROC by QSA + quarterly ASV scan | | Level 2 | ≤300,000 transactions/year | Annual SAQ-D for Service Providers + quarterly ASV scan |
Defined Approach vs Customised Approach (New in v4.0)
| Approach | Description | Best For | |----------|-------------|----------| | Defined Approach | Follow prescriptive requirements as written | Most organisations; standard controls | | Customised Approach | Implement alternative controls that meet the stated Objective | Mature organisations with innovative security practices |
The Customised Approach requires a Targeted Risk Analysis (TRA) for each customised control, approved by senior management, and assessed by a QSA.
SAQ Selection Guide
Consult references/pci-dss-saq-guide.md for the full SAQ selection decision tree and per-SAQ control counts.
FAQ 1331 (updated August 31, 2026) — critical scoping rule: SAQ eligibility criteria may no longer be used as a guide for determining PCI DSS requirement applicability in a ROC assessment "unless explicitly reviewed, discussed and agreed upon with the merchant's compliance accepting entity (e.g., payment brands and acquirers)". QSA agreement alone no longer suffices — flag this to any ROC merchant marking requirements N/A via SAQ-A-style criteria (notably 6.4.3/11.6.1 e-commerce scoping), and advise obtaining acquirer/payment-brand approval in writing.
Quick reference: | SAQ | Applies To | ~Controls | |-----|-----------|----------| | A | Card-not-present merchants; all CHD functions fully outsourced to PCI-compliant third parties | ~22 | | A-EP | E-commerce merchants; outsource payment processing but control how customers redirect to third party | ~191 | | B | Merchants using only imprint machines or standalone dial-out terminals; no e-commerce | ~41 | | B-IP | Merchants using standalone IP-connected PTS POI devices only; no e-commerce | ~83 | | C | Merchants with payment application systems connected to internet; no e-commerce | ~160 | | C-VT | Merchants using web-based virtual terminals on isolated device; no e-commerce | ~90 | | P2PE | Merchants using validated P2PE solution only; no e-commerce | ~33 | | D (Merchant) | All other merchants not covered above | ~340 | | D (Service Provider) | All service providers eligible for SAQ | ~340 |
Core Workflows
1. CDE Scoping
When asked to help scope the CDE:
- Ask: What data flows involve PANs? (intake, processing, storage, transmission channels)
- Identify all system components that store, process, or transmit CHD/SAD
- Identify connected systems that could impact CDE security (jump hosts, monitoring, AD)
- Assess network segmentation: is the CDE isolated from out-of-scope networks?
- Identify scope reduction opportunities (tokenisation, P2PE, outsourcing)
- Produce: In-scope system inventory, data flow description, segmentation assessment, scope reduction recommendations
Scoping rules:
- Any system that stores/processes/transmits PAN → in scope
- Any system connected to a CDE system without adequate segmentation → in scope
- Cloud components that touch CHD (even briefly) → in scope
- Third-party service providers that could impact CDE security → must be PCI-compliant
2. Gap Assessment
When asked to assess compliance against PCI DSS v4.0.1:
- Ask for: merchant/SP level, in-scope systems, existing controls, SAQ type or ROC requirement
- Produce a table for each of the 12 requirements with sub-controls
- For each control: Status (Compliant / Partial / Non-Compliant / N/A), Gap Description, Evidence Needed
- Highlight critical findings (any non-compliant SAD storage, lack of MFA, no ASV scans)
- Offer remediation roadmap
Status definitions:
- ✅ Compliant — control is fully in place and operating effectively with evidence
- 🟡 Partial — some controls exist but gaps, exceptions, or inconsistencies remain
- ❌ Non-Compliant — control not implemented; compensating control or remediation required
- N/A — not applicable to this environment with documented justification
3. SAQ Selection
When asked which SAQ applies:
- Ask: Merchant or service provider? How are card transactions accepted? (card-present, CNP, e-commerce, MOTO)
- Ask: Is all cardholder data processing outsourced to a PCI-compliant third party?
- Ask: Are P2PE validated devices used exclusively?
- Ask: Is there any card-present processing?
- Walk through the decision logic to select the correct SAQ type
- Explain what controls the selected SAQ covers and what is excluded from scope
- If the merchant files a ROC (Level 1 or voluntary): apply the FAQ 1331 rule above — SAQ eligibility criteria cannot reduce ROC scope without documented acquirer/payment-brand agreement
4. Control Implementation Guidance
For any PCI DSS requirement or sub-control, structure your response as:
Requirement [X.X]: [Name]
- What it requires: Plain-language description
- How to implement: Concrete, actionable steps
- Evidence for QSA: What a QSA or ISA will look for during assessment
- Common gaps: What organisations typically miss or get wrong
- v4.0 note (if changed from v3.2.1): What is new or different
5. Policy Generation
When generating PCI DSS-aligned policies:
- Include: Purpose, Scope, Policy Statement, Roles & Responsibilities, Standards/Procedures, Review Cycle, PCI DSS Requirement references
- Include document control block: Version | Author | Approved By | Date | Next Review
Common PCI-aligned policies: | Policy | Primary Requirement(s) | |--------|----------------------| | Network Security Control Policy | Req 1 | | System Configuration/Hardening Policy | Req 2 | | Data Retention and Disposal Policy | Req 3 | | Cryptography and Key Management Policy | Req 3.5, 4 | | Vulnerability Management Policy | Req 5, 6 | | Secure Development Policy (SDLC) | Req 6 | | Access Control Policy | Req 7 | | User Authentication and Password Policy | Req 8 | | Physical Security Policy | Req 9 | | Audit Log Management Policy | Req 10 | | Penetration Testing and ASV Scan Policy | Req 11 | | Information Security Policy | Req 12 | | Incident Response Plan | Req 12.10 |
v4.0 Key Changes from v3.2.1
| Topic | v3.2.1 | v4.0 / v4.0.1 | |-------|--------|--------------| | Compliance approach | Defined approach only | + Customised Approach (alternative controls with TRA) | | MFA | Required for non-console admin and remote access to CDE | Extended: Required for all access into the CDE (Req 8.4.2) | | Password length | Minimum 7 characters | Minimum 12 characters (or 8 if system cannot support 12) | | Anti-phishing | Not explicitly required | Req 5.4.1: Automated technical solution to detect/protect against phishing | | E-commerce script integrity | Limited | Req 6.4.3 / 11.6.1: Inventory and integrity checks on all payment page scripts | | Targeted Risk Analysis | Not formalised | Required for each customised control and several defined controls | | Penetration testing | Req 11.3 | Enhanced scope: internal + external + CDE segmentation validation | | ASV scanning | Quarterly | Unchanged; ASV must be validated against v4.0 tests | | Log review | Manual acceptable | Req 10.4.1.1: Au
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
