/pci-dss-expert
PCI DSS v4.0.1 compliance expert. Provides guidance on payment card industry security, ROC completion, SAQ selection, requirement interpretation, and the new March 2025 mandatory requirements.
$ npx -y skills add GRCEngClub/claude-grc-engineering --skill pci-dss-expert --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/pci-dss-expert
Context preview
The summary Claude sees to decide when to auto-load this skill.
PCI DSS v4.0.1 compliance expert. Provides guidance on payment card industry security, ROC completion, SAQ selection, requirement interpretation, and the new March 2025 mandatory requirements.
SKILL.md
pci-dss-expert.SKILL.mdname: pci-dss-expert
description: PCI DSS v4.0.1 compliance expert. Provides guidance on payment card industry security, ROC completion, SAQ selection, requirement interpretation, and the new March 2025 mandatory requirements.
allowed-tools: Read, Glob, Grep, Write
PCI DSS Expert
Deep expertise in Payment Card Industry Data Security Standard v4.0.1.
Expertise Areas
Core Requirements (12)
| Req | Title | Focus | |-----|-------|-------| | 1 | Network Security Controls | Firewalls, segmentation, NSCs | | 2 | Secure Configurations | Hardening, inventory, defaults | | 3 | Protect Stored Data | Encryption, PAN, SAD, retention | | 4 | Cryptography in Transit | TLS, secure channels | | 5 | Malware Protection | Anti-malware, phishing | | 6 | Secure Development | SDLC, patches, web apps | | 7 | Access Restriction | Need-to-know, RBAC | | 8 | User Authentication | MFA, passwords, accounts | | 9 | Physical Security | Facility, media, visitors | | 10 | Logging & Monitoring | Audit trails, SIEM, review | | 11 | Security Testing | Scans, pen tests, IDS/IPS | | 12 | Security Policies | Policies, training, IR |
Validation Types
**ROC (Report on Compliance)**:
- Required for Level 1 merchants and service providers
- Completed by Qualified Security Assessor (QSA)
- Comprehensive assessment of all requirements
**SAQ (Self-Assessment Questionnaire)**:
- For Level 2-4 merchants
- Multiple types (A, A-EP, B, B-IP, C, C-VT, D, P2PE)
- Self-assessment with attestation
**AOC (Attestation of Compliance)**:
- Summary document confirming compliance status
- Accompanies ROC or SAQ
Cardholder Data Environment (CDE)
Key concepts:
- **CDE**: Systems that store, process, or transmit CHD
- **CHD**: Cardholder Data (PAN, name, expiration, service code)
- **SAD**: Sensitive Authentication Data (CVV, PIN, track data)
- **PAN**: Primary Account Number (the card number)
March 2025 Mandatory Requirements
Critical new requirements:
- 6.4.3: Payment page script management
- 8.4.2: MFA for all CDE access
- 10.4.1.1: Automated log review
- 11.6.1: Payment page change detection
- 12.3.1: Targeted risk analysis
Scoping Guidance
- Define CDE boundaries clearly
- Identify all connected and security-impacting systems
- Network segmentation reduces scope
- Document scope and maintain annually
Capabilities
- Compliance readiness assessment
- ROC section guidance and completion help
- SAQ type selection and completion
- Requirement interpretation and evidence guidance
- Compensating control evaluation
- Customized approach support
- Gap analysis and remediation planning
- QSA assessment preparation
Read more
name: pci-dss-expert description: PCI DSS v4.0.1 compliance expert. Provides guidance on payment card industry security, ROC completion, SAQ selection, requirement interpretation, and the new March 2025 mandatory requirements. allowed-tools: Read, Glob, Grep, Write
PCI DSS Expert
Deep expertise in Payment Card Industry Data Security Standard v4.0.1.
Expertise Areas
Core Requirements (12)
| Req | Title | Focus | |-----|-------|-------| | 1 | Network Security Controls | Firewalls, segmentation, NSCs | | 2 | Secure Configurations | Hardening, inventory, defaults | | 3 | Protect Stored Data | Encryption, PAN, SAD, retention | | 4 | Cryptography in Transit | TLS, secure channels | | 5 | Malware Protection | Anti-malware, phishing | | 6 | Secure Development | SDLC, patches, web apps | | 7 | Access Restriction | Need-to-know, RBAC | | 8 | User Authentication | MFA, passwords, accounts | | 9 | Physical Security | Facility, media, visitors | | 10 | Logging & Monitoring | Audit trails, SIEM, review | | 11 | Security Testing | Scans, pen tests, IDS/IPS | | 12 | Security Policies | Policies, training, IR |
Validation Types
**ROC (Report on Compliance)**:
- Required for Level 1 merchants and service providers
- Completed by Qualified Security Assessor (QSA)
- Comprehensive assessment of all requirements
**SAQ (Self-Assessment Questionnaire)**:
- For Level 2-4 merchants
- Multiple types (A, A-EP, B, B-IP, C, C-VT, D, P2PE)
- Self-assessment with attestation
**AOC (Attestation of Compliance)**:
- Summary document confirming compliance status
- Accompanies ROC or SAQ
Cardholder Data Environment (CDE)
Key concepts:
- **CDE**: Systems that store, process, or transmit CHD
- **CHD**: Cardholder Data (PAN, name, expiration, service code)
- **SAD**: Sensitive Authentication Data (CVV, PIN, track data)
- **PAN**: Primary Account Number (the card number)
March 2025 Mandatory Requirements
Critical new requirements:
- 6.4.3: Payment page script management
- 8.4.2: MFA for all CDE access
- 10.4.1.1: Automated log review
- 11.6.1: Payment page change detection
- 12.3.1: Targeted risk analysis
Scoping Guidance
- Define CDE boundaries clearly
- Identify all connected and security-impacting systems
- Network segmentation reduces scope
- Document scope and maintain annually
Capabilities
- Compliance readiness assessment
- ROC section guidance and completion help
- SAQ type selection and completion
- Requirement interpretation and evidence guidance
- Compensating control evaluation
- Customized approach support
- Gap analysis and remediation planning
- QSA assessment preparation
Open-source GRC Engineering resource for Claude. claude-grc-engineering turns technical evidence from cloud, SaaS, code, and security tools into framework-aligned findings, gap reports, remediation guidance, evidence packages, and OSCAL workflows.
Repo: GRCEngClub/claude-grc-engineering
Other skills on trust-center.
- /academic-research-companion
Guide a research project through the full academic lifecycle — from raw idea to concrete research question, literature grounding, methodology, writing, feedback, and publication. Use this skill whenever the user shares a research idea, asks to "flesh out" a topic, wants sources
Open skill - /aws-inspector-expert
Expertise in evaluating AWS accounts for compliance — what checks are meaningful, which SCF controls they map to, and how to interpret aws CLI output.
Open skill - /azure-inspector-expert
Expertise in evaluating Azure subscription findings from azure-inspector and mapping them to SCF controls.
Open skill - /crowdstrike-inspector-expert
Interpret CrowdStrike Falcon findings for sensor coverage, policy visibility, and host group scoping.
Open skill - /datadog-inspector-expert
Interpret datadog-inspector findings and translate Datadog monitoring, audit, log-retention, SSO, and RBAC results into GRC evidence and remediation.
Open skill - /drata-inspector-expert
Interpret drata-inspector findings generated from drata-cli workflows and turn Drata control, monitor, evidence, personnel, and integration posture into GRC action.
Open skill

