Back to catalog
Static reviewDevelopment

Skill dossier

implementing-pci-dss-compliance-controls

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

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. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/implementing-pci-dss-compliance-controls/SKILL.md:L86]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/implementing-pci-dss-compliance-controls/SKILL.md:L1-L30]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
7
Markdown files
5
scripts
1
references
4
Size
42.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-pci-dss-compliance-controls/assets/template.mdReference4.2 KB
skills/implementing-pci-dss-compliance-controls/LICENSEOther11 KB
skills/implementing-pci-dss-compliance-controls/references/api-reference.mdReference6.3 KB
skills/implementing-pci-dss-compliance-controls/references/standards.mdReference1.1 KB
skills/implementing-pci-dss-compliance-controls/references/workflows.mdReference1.6 KB
skills/implementing-pci-dss-compliance-controls/scripts/agent.pyScript12 KB
skills/implementing-pci-dss-compliance-controls/SKILL.mdInstruction6.4 KB

SKILL.md frontmatter

{
  "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"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Core Concepts

    Source-described action candidate under “Core Concepts”; not verified execution.

  4. 04
    Action

    Install and maintain network security controls (firewalls, NSCs)

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

  5. 05
    Action

    Apply secure configurations to all system components

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

  6. 06
    Action

    Protect stored account data (encryption, tokenization, truncation)

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

Inspect all extracted workflow candidates (49 candidate steps)
  1. 07
    Action

    Protect cardholder data with strong cryptography during transmission

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

  2. 08
    Action

    Protect all systems and networks from malicious software

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

  3. 09
    Action

    Develop and maintain secure systems and software

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

  4. 10
    Action

    Restrict access to system components and cardholder data by business need to know

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

  5. 11
    Action

    Identify users and authenticate access to system components

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

  6. 12
    Action

    Restrict physical access to cardholder data

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

  7. 13
    Action

    Log and monitor all access to system components and cardholder data

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

  8. 14
    Action

    Test security of systems and networks regularly

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

  9. 15
    Action

    Support information security with organizational policies and programs

    Source-described action candidate under “12 PCI DSS Requirements by Control Objective”; not verified execution.

  10. 16
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  11. 17
    Output

    Identify all cardholder data flows (card present, card not present, storage)

    Source-described output candidate under “Phase 1: Scoping and Assessment (Weeks 1-4)”; not verified execution.

  12. 18
    Action

    Define Cardholder Data Environment (CDE) boundaries

    Source-described action candidate under “Phase 1: Scoping and Assessment (Weeks 1-4)”; not verified execution.

  13. 19
    Action

    Validate network segmentation effectiveness

    Source-described action candidate under “Phase 1: Scoping and Assessment (Weeks 1-4)”; not verified execution.

  14. 20
    Action

    Determine compliance validation level

    Source-described action candidate under “Phase 1: Scoping and Assessment (Weeks 1-4)”; not verified execution.

  15. 21
    Action

    Conduct PCI DSS gap assessment against all 12 requirements

    Source-described action candidate under “Phase 1: Scoping and Assessment (Weeks 1-4)”; not verified execution.

  16. 22
    Action

    Deploy and configure network security controls (Req 1)

    Source-described action candidate under “Phase 2: Network and System Security (Weeks 5-12)”; not verified execution.

  17. 23
    Action

    Implement network segmentation to minimize CDE scope

    Source-described action candidate under “Phase 2: Network and System Security (Weeks 5-12)”; not verified execution.

  18. 24
    Action

    Harden system configurations using CIS Benchmarks (Req 2)

    Source-described action candidate under “Phase 2: Network and System Security (Weeks 5-12)”; not verified execution.

  19. 25
    Action

    Implement WAF for public-facing web applications (Req 6.4.1)

    Source-described action candidate under “Phase 2: Network and System Security (Weeks 5-12)”; not verified execution.

  20. 26
    Action

    Deploy anti-malware on all in-scope systems (Req 5)

    Source-described action candidate under “Phase 2: Network and System Security (Weeks 5-12)”; not verified execution.

  21. 27
    Action

    Implement encryption for stored cardholder data (Req 3)

    Source-described action candidate under “Phase 3: Data Protection (Weeks 13-20)”; not verified execution.

  22. 28
    Action

    Deploy tokenization where possible to reduce scope

    Source-described action candidate under “Phase 3: Data Protection (Weeks 13-20)”; not verified execution.

  23. 29
    Action

    Enforce TLS 1.2+ for all cardholder data transmission (Req 4)

    Source-described action candidate under “Phase 3: Data Protection (Weeks 13-20)”; not verified execution.

  24. 30
    Action

    Implement key management procedures

    Source-described action candidate under “Phase 3: Data Protection (Weeks 13-20)”; not verified execution.

  25. 31
    Action

    Deploy data discovery tools to locate unencrypted cardholder data

    Source-described action candidate under “Phase 3: Data Protection (Weeks 13-20)”; not verified execution.

  26. 32
    Action

    Implement RBAC based on business need to know (Req 7)

    Source-described action candidate under “Phase 4: Access Controls (Weeks 21-28)”; not verified execution.

  27. 33
    Action

    Deploy MFA for all access to CDE (Req 8)

    Source-described action candidate under “Phase 4: Access Controls (Weeks 21-28)”; not verified execution.

  28. 34
    Action

    Implement unique user IDs for all users

    Source-described action candidate under “Phase 4: Access Controls (Weeks 21-28)”; not verified execution.

  29. 35
    Action

    Enforce password policies meeting PCI DSS 4.0 requirements

    Source-described action candidate under “Phase 4: Access Controls (Weeks 21-28)”; not verified execution.

  30. 36
    Action

    Implement physical access controls for CDE facilities (Req 9)

    Source-described action candidate under “Phase 4: Access Controls (Weeks 21-28)”; not verified execution.

  31. 37
    Action

    Deploy centralized logging for all CDE components (Req 10)

    Source-described action candidate under “Phase 5: Monitoring and Testing (Weeks 29-36)”; not verified execution.

  32. 38
    Action

    Implement automated log review mechanisms

    Source-described action candidate under “Phase 5: Monitoring and Testing (Weeks 29-36)”; not verified execution.

  33. 39
    Action

    Conduct internal and external vulnerability scans (Req 11)

    Source-described action candidate under “Phase 5: Monitoring and Testing (Weeks 29-36)”; not verified execution.

  34. 40
    Action

    Perform penetration testing (internal and external)

    Source-described action candidate under “Phase 5: Monitoring and Testing (Weeks 29-36)”; not verified execution.

  35. 41
    Action

    Implement file integrity monitoring (FIM) for critical files

    Source-described action candidate under “Phase 5: Monitoring and Testing (Weeks 29-36)”; not verified execution.

  36. 42
    Action

    Develop comprehensive information security policy (Req 12)

    Source-described action candidate under “Phase 6: Policy and Governance (Weeks 37-42)”; not verified execution.

  37. 43
    Action

    Implement security awareness training including anti-phishing

    Source-described action candidate under “Phase 6: Policy and Governance (Weeks 37-42)”; not verified execution.

  38. 44
    Action

    Establish incident response plan specific to cardholder data

    Source-described action candidate under “Phase 6: Policy and Governance (Weeks 37-42)”; not verified execution.

  39. 45
    Action

    Conduct targeted risk analyses for flexible requirements

    Source-described action candidate under “Phase 6: Policy and Governance (Weeks 37-42)”; not verified execution.

  40. 46
    Action

    Document and validate all controls for assessment

    Source-described action candidate under “Phase 6: Policy and Governance (Weeks 37-42)”; not verified execution.

  41. 47
    Action

    Key Artifacts

    Source-described action candidate under “Key Artifacts”; not verified execution.

  42. 48
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  43. 49
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

19 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

7 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

12 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 12 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-pci-dss-compliance-controls/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 7 collected file(s), 5 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/implementing-pci-dss-compliance-controls/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/implementing-pci-dss-compliance-controls
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.