pci-compliance

Enforce PCI DSS v4.0 technical controls for payment card data.

3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill pci-compliance-mauriciodelrio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pci-compliance
Source: https://github.com/mauriciodelrio/delriodev-skills/tree/main/es-skills/governance-risk-and-compliance/pci-compliance
Command: npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill pci-compliance-mauriciodelrio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineering and security teams eliminate PCI DSS scope and reduce the risk of cardholder data breaches by providing actionable technical controls, secure design patterns, and enforcement guidance for processing, storing, or transmitting payment card data.

Core Features & Use Cases

  • Tokenization & Storage Guidance: Patterns and Prisma schema examples to store only tokens and last4/fingerprint information.
  • Encryption in Transit: TLS 1.2+ configuration and HSTS recommendations for protecting cardholder data in transit.
  • Input Validation & PAN Detection: Middleware examples using strict schemas and Luhn-based PAN detection to block sensitive data leakage.
  • Audit Logging & Retention: Audit trail design with redaction, event taxonomy, and retention guidance to meet PCI logging requirements.
  • CDE Segmentation & Architecture: Docker-compose and network segmentation examples to isolate the Cardholder Data Environment.
  • Use Case: Audit a checkout implementation to remove PAN exposure, implement tokenization with Stripe, apply network segmentation, and enable PCI-compliant logging before an external assessment.

Quick Start

Use the pci-compliance skill to audit your payment flow, identify PCI DSS v4.0 gaps, and generate a prioritized remediation plan.

Frequently Asked Questions about pci-compliance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement tokenization to reduce PCI DSS scope for payment card data?

Tokenization reduces PCI DSS scope by replacing sensitive cardholder data with non-sensitive tokens. This skill provides patterns and Prisma schema examples to securely store only tokens and card fingerprints, eliminating raw PAN exposure.

What are the PCI DSS v4.0 requirements for encryption in transit and audit logging?

PCI DSS v4.0 requires TLS 1.2+ encryption for data in transit and audit logs with 12-month retention. This skill provides TLS configuration guidance and audit logging designs with redaction and event taxonomy to satisfy these specific controls.

How do I detect and block PAN leakage in my checkout application?

You can block PAN leakage using strict input validation schemas and Luhn-based PAN detection. This skill provides middleware examples that intercept and identify sensitive payment card data before it enters your application logs or storage.

How do I isolate my Cardholder Data Environment using network segmentation?

You can isolate your Cardholder Data Environment (CDE) using network segmentation. This skill provides Docker-compose examples and architectural patterns to strictly separate CDE components from your broader application network, reducing audit scope.

Can I use this to prepare my payment systems for an external PCI DSS assessment?

Yes, you can prepare for external assessments by using this skill to audit your payment flow. It identifies PCI DSS v4.0 gaps, implements tokenization, applies network segmentation, and enables compliant logging to generate a prioritized remediation plan.