What it does. Implements PCI DSS 4.0.1's 12 requirements across 6 control objectives Part of mukul975/Anthropic-Cybersecurity-Skills (817 security skills) (mukul975/Anthropic-Cybersecurity-Skills).

Upstream	mukul975/Anthropic-Cybersecurity-Skills
Skill file	skills/implementing-pci-dss-compliance-controls/SKILL.md
License	Apache-2.0 (skill folder LICENSE)
Author	mukul975
Fetched	2026-09-10

Install

• npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-pci-dss-compliance-controls, or copy the skill folder into ~/.claude/skills/implementing-pci-dss-compliance-controls/.
• Raw file: curl -sL https://raw.githubusercontent.com/mukul975/Anthropic-Cybersecurity-Skills/HEAD/skills/implementing-pci-dss-compliance-controls/SKILL.md

SKILL.md (verbatim)

name: implementing-pci-dss-compliance-controls
description: Implements PCI DSS 4.0.1's 12 requirements across 6 control objectives
  for organizations that store, process, or transmit cardholder data, including the
  customized validation approach, enhanced authentication, and continuous monitoring
  controls introduced by the 51 requirements mandatory since March 2025. Use when
  scoping a cardholder data environment, building PCI DSS 4.0.1 compliance controls,
  or preparing for a PCI assessment.
domain: cybersecurity
subdomain: compliance-governance
tags:
- compliance
- governance
- pci-dss
- payment-security
- cardholder-data
nist_csf:
- GV.PO-01
- PR.DS-01
- PR.AA-01
- DE.CM-01
- ID.RA-01
version: '1.0'
author: mahipal
license: Apache-2.0
mitre_attack:
- T1078
- T1530
- T1685.002

Implementing PCI DSS Compliance Controls

Overview

PCI DSS 4.0.1 establishes 12 requirements across 6 control objectives for organizations that store, process, or transmit cardholder data. With PCI DSS 3.2.1 retiring April 2024 and 51 new requirements becoming mandatory March 31, 2025, this skill covers implementing all requirements including the new customized validation approach, enhanced authentication, and continuous monitoring controls.

When to Use

• When deploying or configuring implementing pci dss compliance controls capabilities in your environment
• When establishing security controls aligned to compliance requirements
• When building or improving security architecture for this domain
• When conducting security assessments that require this implementation

Prerequisites

• Understanding of payment card processing flows and cardholder data environment (CDE)
• Knowledge of network segmentation and security architecture
• Access to cardholder data environment for scoping
• Understanding of PCI compliance validation levels (merchant levels 1-4, service provider levels 1-2)

Core Concepts

12 PCI DSS Requirements by Control Objective

Build and Maintain a Secure Network and Systems

1. Install and maintain network security controls (firewalls, NSCs)
2. Apply secure configurations to all system components

Protect Account Data 3. Protect stored account data (encryption, tokenization, truncation) 4. Protect cardholder data with strong cryptography during transmission

Maintain a Vulnerability Management Program 5. Protect all systems and networks from malicious software 6. Develop and maintain secure systems and software

Implement Strong Access Control Measures 7. Restrict access to system components and cardholder data by business need to know 8. Identify users and authenticate access to system components 9. Restrict physical access to cardholder data

Regularly Monitor and Test Networks 10. Log and monitor all access to system components and cardholder data 11. Test security of systems and networks regularly

Maintain an Information Security Policy 12. Support information security with organizational policies and programs

Key PCI DSS 4.0 Changes

• Customized Approach: Alternative to defined approach, allowing custom control design with objective-based validation
• MFA for all CDE access: Extended beyond admin to all access to cardholder data (Req 8.4.2)
• Targeted Risk Analysis: Organizations perform their own risk analysis for flexible requirements
• Authenticated Vulnerability Scanning: Internal scans must use authenticated scanning (Req 11.3.1.1)
• Anti-phishing mechanisms: Technical controls to detect and protect against phishing (Req 5.4.1)
• Automated log review: Automated mechanisms for review of audit logs (Req 10.4.1.1)

Workflow

Phase 1: Scoping and Assessment (Weeks 1-4)

1. Identify all cardholder data flows (card present, card not present, storage)
2. Define Cardholder Data Environment (CDE) boundaries
3. Validate network segmentation effectiveness
4. Determine compliance validation level
5. Conduct PCI DSS gap assessment against all 12 requirements

Phase 2: Network and System Security (Weeks 5-12)

1. Deploy and configure network security controls (Req 1)
2. Implement network segmentation to minimize CDE scope
3. Harden system configurations using CIS Benchmarks (Req 2)
4. Implement WAF for public-facing web applications (Req 6.4.1)
5. Deploy anti-malware on all in-scope systems (Req 5)

Phase 3: Data Protection (Weeks 13-20)

1. Implement encryption for stored cardholder data (Req 3)
2. Deploy tokenization where possible to reduce scope
3. Enforce TLS 1.2+ for all cardholder data transmission (Req 4)
4. Implement key management procedures
5. Deploy data discovery tools to locate unencrypted cardholder data

Phase 4: Access Controls (Weeks 21-28)

1. Implement RBAC based on business need to know (Req 7)
2. Deploy MFA for all access to CDE (Req 8)
3. Implement unique user IDs for all users
4. Enforce password policies meeting PCI DSS 4.0 requirements
5. Implement physical access controls for CDE facilities (Req 9)

Phase 5: Monitoring and Testing (Weeks 29-36)

1. Deploy centralized logging for all CDE components (Req 10)
2. Implement automated log review mechanisms
3. Conduct internal and external vulnerability scans (Req 11)
4. Perform penetration testing (internal and external)
5. Implement file integrity monitoring (FIM) for critical files

Phase 6: Policy and Governance (Weeks 37-42)

1. Develop comprehensive information security policy (Req 12)
2. Implement security awareness training including anti-phishing
3. Establish incident response plan specific to cardholder data
4. Conduct targeted risk analyses for flexible requirements
5. Document and validate all controls for assessment

Key Artifacts

• CDE Scope Documentation and Network Diagrams
• Self-Assessment Questionnaire (SAQ) or Report on Compliance (ROC)
• Attestation of Compliance (AOC)
• Quarterly ASV Scan Reports
• Annual Penetration Test Report
• Risk Assessment Documentation
• Security Policies and Procedures

Common Pitfalls

• Scope creep due to inadequate network segmentation
• Storing prohibited data (CVV, full track data) after authorization
• Missing the March 2025 deadline for new mandatory requirements
• Treating PCI DSS as annual compliance rather than continuous security
• Not including cloud and container environments in CDE scope

References

• PCI DSS v4.0.1: https://www.pcisecuritystandards.org/document_library/
• PCI SSC Quick Reference Guide
• PCI DSS 4.0 Summary of Changes
• UpGuard PCI DSS 4.0 Guide: https://www.upguard.com/blog/pci-compliance

Other files in this skill

• LICENSE
• assets/template.md
• references/api-reference.md
• references/standards.md
• references/workflows.md
• scripts/agent.py

assets/template.md (verbatim)

Implementing PCI DSS Compliance Controls - Audit Checklist

Organization Information

Field	Value
Organization Name
Assessment Date
Assessor
Standard	PCI DSS v4.0.1

---

Compliance Checklist

1. Requirement 1: Install and maintain network security controls

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

2. Requirement 2: Apply secure configurations to all system components

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

3. Requirement 3: Protect stored account data

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

4. Requirement 4: Protect cardholder data with strong cryptography during transmission

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

5. Requirement 5: Protect all systems and networks from malicious software

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

6. Requirement 6: Develop and maintain secure systems and software

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

7. Requirement 7: Restrict access by business need to know

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

8. Requirement 8: Identify users and authenticate access

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

9. Requirement 9: Restrict physical access to cardholder data

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

10. Requirement 10: Log and monitor all access to system components

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

11. Requirement 11: Test security of systems and networks regularly

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

12. Requirement 12: Support information security with policies and programs

• Policy/procedure documented
• Controls implemented
• Evidence available
• Tested and verified
• Status: Compliant / Partially Compliant / Non-Compliant / N/A
• Evidence: _______________
• Notes: _______________

---

Summary

Status	Count
Compliant
Partially Compliant
Non-Compliant
N/A

Sign-off

Role	Name	Signature	Date
Assessor
Security Manager
Senior Management

references/api-reference.md (verbatim)

API Reference: PCI DSS Compliance Control Audit

Libraries Used

Library	Purpose
requests	API calls to scan engines and cloud services
jinja2	Generate compliance assessment reports
json	Parse control status and evidence data
subprocess	Run network segmentation and encryption checks
csv	Export compliance matrices

Installation

pip install requests jinja2

PCI DSS v4.0 Requirements Map

Requirement	Title	Automated Checks
1	Install and maintain network security controls	Firewall rules, segmentation testing
2	Apply secure configurations	Default credential scan, hardening baselines
3	Protect stored account data	Encryption at rest, key management
4	Protect cardholder data with strong cryptography during transmission	TLS version, cipher suites
5	Protect all systems against malware	AV status, EDR coverage
6	Develop and maintain secure systems	Vulnerability scans, SAST/DAST
7	Restrict access by business need to know	RBAC review, access logs
8	Identify users and authenticate access	MFA status, password policy
9	Restrict physical access to cardholder data	Physical access logs
10	Log and monitor all access	Log aggregation, SIEM alerts
11	Test security of systems regularly	Penetration tests, IDS/IPS
12	Support information security with policies	Policy review dates

Core Compliance Checks

Requirement 2: Default Credentials Check

import requests

DEFAULT_CREDS = [
    ("admin", "admin"), ("admin", "password"), ("root", "root"),
    ("admin", ""), ("user", "user"), ("test", "test"),
]

def check_default_credentials(target_url):
    findings = []
    for username, password in DEFAULT_CREDS:
        try:
            resp = requests.post(
                f"{target_url}/login",
                data={"username": username, "password": password},
                timeout=10,
                allow_redirects=False,
            )
            if resp.status_code in (200, 302):
                findings.append({
                    "target": target_url,
                    "username": username,
                    "requirement": "2.2.2",
                    "severity": "critical",
                })
        except requests.RequestException:
            pass
    return findings

Requirement 4: TLS Configuration Check

import ssl
import socket

def check_tls_config(hostname, port=443):
    findings = []
    context = ssl.create_default_context()
    with socket.create_connection((hostname, port), timeout=10) as sock:
        with context.wrap_socket(sock, server_hostname=hostname) as ssock:
            protocol = ssock.version()
            cipher = ssock.cipher()
            cert = ssock.getpeercert()

            # Check TLS version (must be 1.2+)
            if protocol in ("TLSv1", "TLSv1.1"):
                findings.append({
                    "check": "tls_version",
                    "requirement": "4.2.1",
                    "severity": "high",
                    "detail": f"Weak TLS version: {protocol}",
                })

            # Check cipher strength
            if cipher and cipher[2] < 128:
                findings.append({
                    "check": "cipher_strength",
                    "requirement": "4.2.1",
                    "severity": "high",
                    "detail": f"Weak cipher: {cipher[0]} ({cipher[2]} bits)",
                })

    return {"protocol": protocol, "cipher": cipher[0], "findings": findings}

Requirement 8: MFA and Password Policy

def check_password_policy(identity_provider_url, headers):
    resp = requests.get(
        f"{identity_provider_url}/api/v1/policies/password",
        headers=headers,
        timeout=30,
    )
    policy = resp.json()

    findings = []
    if policy.get("minLength", 0) < 12:
        findings.append({
            "check": "password_length",
            "requirement": "8.3.6",
            "severity": "medium",
            "detail": f"Min password length {policy['minLength']} < 12",
        })
    if not policy.get("requireUppercase"):
        findings.append({
            "check": "password_complexity",
            "requirement": "8.3.6",
            "severity": "low",
            "detail": "Uppercase not required",
        })
    return findings

Requirement 10: Log Monitoring Check

def check_logging_coverage(siem_url, siem_headers):
    """Verify all CDE systems forward logs to SIEM."""
    resp = requests.get(
        f"{siem_url}/api/sources",
        headers=siem_headers,
        timeout=30,
    )
    active_sources = resp.json().get("sources", [])
    return {
        "total_sources": len(active_sources),
        "requirement": "10.2",
        "active": [s for s in active_sources if s.get("status") == "active"],
        "inactive": [s for s in active_sources if s.get("status") != "active"],
    }

Generate Compliance Report

from jinja2 import Template

REPORT_TEMPLATE = """
# PCI DSS v4.0 Compliance Assessment

Generated: {{ timestamp }}
Scope: {{ scope }}

## Summary
- Total Controls: {{ total }}
- Compliant: {{ compliant }}
- Non-Compliant: {{ non_compliant }}
- Compliance Rate: {{ rate }}%

## Findings
{% for finding in findings %}
### {{ finding.requirement }} — {{ finding.check }}
- **Severity**: {{ finding.severity }}
- **Detail**: {{ finding.detail }}
{% endfor %}
"""

def generate_report(findings, scope, timestamp):
    compliant = sum(1 for f in findings if not f.get("findings"))
    template = Template(REPORT_TEMPLATE)
    return template.render(
        timestamp=timestamp,
        scope=scope,
        total=len(findings),
        compliant=compliant,
        non_compliant=len(findings) - compliant,
        rate=round(compliant / len(findings) * 100, 1),
        findings=[f for f in findings if f.get("findings")],
    )

Output Format

{
  "assessment_date": "2025-01-15",
  "pci_dss_version": "4.0",
  "scope": "Cardholder Data Environment",
  "total_requirements": 12,
  "compliant": 9,
  "non_compliant": 3,
  "findings": [
    {
      "requirement": "4.2.1",
      "check": "tls_version",
      "severity": "high",
      "detail": "Payment gateway using TLSv1.1",
      "remediation": "Upgrade to TLS 1.2 or higher"
    }
  ]
}

references/standards.md (verbatim)

Implementing PCI DSS Compliance Controls - Standards Reference

Primary Standard

• Standard: PCI DSS v4.0.1
• Governing Body: PCI Security Standards Council

Key Requirements

• Requirement 1: Install and maintain network security controls
• Requirement 2: Apply secure configurations to all system components
• Requirement 3: Protect stored account data
• Requirement 4: Protect cardholder data with strong cryptography during transmission
• Requirement 5: Protect all systems and networks from malicious software
• Requirement 6: Develop and maintain secure systems and software
• Requirement 7: Restrict access by business need to know
• Requirement 8: Identify users and authenticate access
• Requirement 9: Restrict physical access to cardholder data
• Requirement 10: Log and monitor all access to system components
• Requirement 11: Test security of systems and networks regularly
• Requirement 12: Support information security with policies and programs

Cross-References

• ISO/IEC 27001:2022
• NIST Cybersecurity Framework 2.0
• CIS Controls v8.1
• COBIT 2019

references/workflows.md (verbatim)

Implementing PCI DSS Compliance Controls - Workflows

Workflow 1: Assessment and Planning

Start
  |
  v
[Scope Definition]
  - Define boundaries and objectives
  - Identify stakeholders
  - Gather existing documentation
  |
  v
[Current State Assessment]
  - Review existing controls
  - Identify gaps against requirements
  - Document findings
  |
  v
[Gap Analysis]
  - Compare current vs required state
  - Prioritize gaps by risk
  - Estimate remediation effort
  |
  v
[Remediation Planning]
  - Define action items with owners
  - Set timelines and milestones
  - Allocate resources and budget
  |
  v
End

Workflow 2: Implementation

Start
  |
  v
[Policy and Procedure Development]
  - Draft policies aligned to standard
  - Review with stakeholders
  - Obtain management approval
  |
  v
[Technical Control Deployment]
  - Implement technical controls
  - Configure monitoring and alerting
  - Validate control effectiveness
  |
  v
[Training and Awareness]
  - Train relevant personnel
  - Communicate policy changes
  - Document training completion
  |
  v
[Verification and Testing]
  - Test controls against requirements
  - Document evidence of operation
  - Address deficiencies
  |
  v
End

Workflow 3: Ongoing Compliance

Start
  |
  v
[Continuous Monitoring]
  - Monitor control effectiveness
  - Track compliance metrics
  - Report to management
  |
  v
[Periodic Review]
  - Annual reassessment
  - Update for regulatory changes
  - Incorporate lessons learned
  |
  v
[Audit and Certification]
  - Internal audit programme
  - External audit/assessment
  - Address findings
  |
  v
End

Back to mukul975/Anthropic-Cybersecurity-Skills (817 security skills) or Agent skills.