Agent skill

Test Cardholder Data Segmentation

by cyberful in cyberful/cyberful

Test whether every segmentation and scope-reduction control isolates the cardholder data environment from claimed out-of-scope systems and differing security levels.

AGPL-3.0Auto-check passedLegal & Compliance

Install Test Cardholder Data Segmentation

skills CLI
$ npx skills add cyberful/cyberful --skill test-cardholder-data-segmentation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cyberful/cyberful test-cardholder-data-segmentation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyberful/builtin/skills/test-cardholder-data-segmentation .claude/skills/test-cardholder-data-segmentation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-cardholder-data-segmentation
GitHub stars
135
Token cost
~928 tokens
SKILL.md length
338 words
Files
5 (incl. references, assets)
Skills in repo
85
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Test whether every segmentation and scope-reduction control isolates the cardholder data environment from claimed out-of-scope systems and differing security levels.

  • 11.4.6 segmentation validation after scoping
  • SKILL.md covers Establish the tested claims, Exercise each unique isolation…, Interpret and route outcomes and Authoritative anchors
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Control changes

What it does

Test Cardholder Data Segmentation is an agent skill from cyberful/cyberful. Test whether every segmentation and scope-reduction control isolates the cardholder data environment from claimed out-of-scope systems and differing security levels. Use for PCI DSS 11.4.5 or 11.4.6 segmentation validation after scoping or control changes.

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `agents/openai.yaml`, `assets/segmentation-test-matrix.schema.json` and `assets/segmentation-test-matrix.template.json`).

It sits in Legal & Compliance, covering Healthcare and finance regulation. The repository describes itself as: Cyberful is an open-source AI Red Team for discovering, exploiting, verifying, and remediating vulnerabilities. The licence is AGPL-3.0.

When your agent uses it

  • 11.4.6 segmentation validation after scoping
  • Control changes

Example prompts

  • “/test-cardholder-data-segmentation”

What it can do on your machine

Read from SKILL.md and the folder at commit ec598a6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs-prv.pcisecuritystandards.org
    • pcisecuritystandards.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test Cardholder Data Segmentation loads about 928 tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 338 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~928
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 338 words, ~928 tokens.

Download SKILL.mdSave it as .claude/skills/test-cardholder-data-segmentation/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
test-cardholder-data-segmentation
description
Test whether every segmentation and scope-reduction control isolates the cardholder data environment from claimed out-of-scope systems and differing security levels. Use for PCI DSS 11.4.5 or 11.4.6 segmentation validation after scoping or control changes.
metadata.domain
payment-security
metadata.subdomain
cde-segmentation
metadata.triggers
test cardholder data segmentation, pci dss segmentation test, validate cde isolation, pci dss 11.4.5 testing, service provider segmentation testing, scope…
metadata.tags
pci-dss, cde, segmentation, isolation, scope-reduction, network-boundary

Test Cardholder Data Segmentation

Test the claim that an out-of-scope component cannot communicate with or impact the security of the CDE even if that component is compromised. A diagram, denied ping, firewall rule, or absence of an observed route is not sufficient by itself.

Establish the tested claims

Read references/segmentation-test-method.md. Begin with the CDE trace, every environment claimed out of scope, every segmentation method in use, differing security levels, third-party and administrative paths, and changes since the last validation.

Use assets/segmentation-test-matrix.template.json under assets/segmentation-test-matrix.schema.json. Each case must name its authorized source vantage, protected destination or capability, isolation method, expected denial invariant, protocol family, evidence, and sampling rationale.

Exercise each unique isolation mechanism

Test from representative out-of-scope networks and systems toward the CDE, not only from the CDE outward. Include permitted intermediaries, shared control planes, identity and management services, name resolution, proxies, load balancers, routing, wireless, remote access, cloud security groups, service meshes, Kubernetes policies, virtualization boundaries, and failover paths where they participate in isolation.

Change one dimension at a time. Distinguish no route, active rejection, application denial, authenticated administrative reach, and an inconclusive timeout. Confirm that alternate protocols, addressing forms, ports, paths, identities, and asynchronous mechanisms do not bypass the intended control.

Use only authorized, bounded Cyberful network and application tools. In Code Audit, inspect policy and construct loopback or disposable-lab cases; do not contact an external target. Do not expand scope or increase effects merely because the test is labeled PCI DSS.

Interpret and route outcomes

If an out-of-scope system reaches or can impact the CDE, preserve the shortest supported path and notify the engagement owner because the PCI DSS scope claim may change. Do not access account data to prove reachability. Route application authorization gaps to test-authorization-boundaries, network enumeration to operate-network-recon, and updated boundaries back to trace-cardholder-data-environment.

Record supported isolation, contradicted isolation, untested mechanism, and evidence gap separately. A technical result supports assessment evidence but does not itself issue a PCI DSS compliance verdict.

Authoritative anchors

© cyberful, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references, assets) in cyberful/builtin/skills/test-cardholder-data-segmentation of cyberful/cyberful.

  • SKILL.md
  • agents/openai.yaml
  • assets/segmentation-test-matrix.schema.json
  • assets/segmentation-test-matrix.template.json
  • references/segmentation-test-method.md

Open the folder on GitHubat commit ec598a6

Compare with similar skills

Test Cardholder Data Segmentation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Cardholder Data Segmentation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Cardholder Data Segmentation this skillcyberful/cyberful135—~928Automated safety check: PassAGPL-3.0
Security Compliancesangrokjung/claude-forge8522 repos~7.2kAutomated safety check: PassMIT
Performing Access Recertification With Saviyntmukul975/Anthropic-Cybersecurity-Skills34k—~2.8kAutomated safety check: PassApache-2.0
Implementing Delinea Secret Server For Pammukul975/Anthropic-Cybersecurity-Skills34k—~4.3kAutomated safety check: PassApache-2.0
Implementing Hashicorp Vault Dynamic Secretsmukul975/Anthropic-Cybersecurity-Skills34k—~5.2kAutomated safety check: PassApache-2.0
Building Identity Governance Lifecycle Processmukul975/Anthropic-Cybersecurity-Skills34k—~7.3kAutomated safety check: PassApache-2.0

Similar skills

  • Security Compliance

    sangrokjung/claude-forge

    Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and…

    852 GitHub starsUsed in 2 repos~7.2k tokens
    Legal & ComplianceAuto-check passed
  • Performing Access Recertification With Saviynt

    mukul975/Anthropic-Cybersecurity-Skills

    Configure and execute access recertification campaigns in Saviynt Enterprise Identity Cloud to validate user entitlements, revoke excessive access, and maintain compliance with SOX, SOC 2, and HIPAA.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed
  • Implementing Delinea Secret Server For Pam

    mukul975/Anthropic-Cybersecurity-Skills

    Implements Delinea Secret Server for privileged access management, covering secret vault configuration, role-based access policies, automated password rotation, session recording, and Active…

    34k GitHub stars~4.3k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed
  • Implementing Hashicorp Vault Dynamic Secrets

    mukul975/Anthropic-Cybersecurity-Skills

    Configures HashiCorp Vault dynamic secrets engines for database credentials, AWS IAM keys, and PKI certificates, with automatic generation, lease management, and rotation to eliminate static secrets…

    34k GitHub stars~5.2k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed
  • Building Identity Governance Lifecycle Process

    mukul975/Anthropic-Cybersecurity-Skills

    Design identity governance and lifecycle (IGA) programs on platforms like SailPoint, Saviynt, or Entra ID Governance, covering joiner-mover-leaver (JML) automation, role mining, access requests…

    34k GitHub stars~7.3k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed
  • Performing Access Review And Certification

    mukul975/Anthropic-Cybersecurity-Skills

    Designs and runs access review and certification campaigns-scoping, reviewer selection, risk-based prioritization, micro-certification, and remediation tracking-to verify user access matches job…

    34k GitHub stars~1.6k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

More from cyberful/cyberful

All 85 skills in this repo
  • Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.

    135 GitHub stars~649 tokensUpdated 1 mo ago
    Auto-check passed
  • Audit Kubernetes admission and policy-as-code enforcement against local workload manifests, exception paths, namespace scope, and deployment evidence.

    135 GitHub stars~610 tokensUpdated 1 mo ago
    Auto-check passed
  • Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.

    135 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check passed
  • Operate Content Discovery

    cyberful/cyberful

    Design and interpret advanced content discovery with ffuf and complementary web fuzzers.

    135 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Operate Network Recon

    cyberful/cyberful

    Build a high-fidelity network and service inventory using Nmap, Masscan, packet capture, DNS, and protocol-specific follow-up.

    135 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Operate Sast Toolchain

    cyberful/cyberful

    Operate Semgrep and source-oriented static analysis as a hypothesis, coverage, and regression system during advanced code audits.

    135 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Test Cardholder Data Segmentation

What does Test Cardholder Data Segmentation do?

Test whether every segmentation and scope-reduction control isolates the cardholder data environment from claimed out-of-scope systems and differing security levels. Test Cardholder Data Segmentation is an agent skill from cyberful/cyberful. Test whether every segmentation and scope-reduction control isolates the cardholder data environment from claimed out-of-scope systems and differing security levels.

When should I use Test Cardholder Data Segmentation?

Test Cardholder Data Segmentation fits situations like: 11.4.6 segmentation validation after scoping; control changes.

How do I install Test Cardholder Data Segmentation in Claude Code?

Run `npx skills add cyberful/cyberful --skill test-cardholder-data-segmentation -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/test-cardholder-data-segmentation in cyberful/cyberful) into .claude/skills/test-cardholder-data-segmentation in your project. Claude Code loads it when a task matches its description.

How do I install Test Cardholder Data Segmentation in Codex?

Run `npx skills add cyberful/cyberful --skill test-cardholder-data-segmentation -a codex`. Or copy the skill folder (cyberful/builtin/skills/test-cardholder-data-segmentation in cyberful/cyberful) into .agents/skills/test-cardholder-data-segmentation in your project. Codex loads it when a task matches its description.

Can I use Test Cardholder Data Segmentation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cyberful/cyberful --skill test-cardholder-data-segmentation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-cardholder-data-segmentation, .gemini/skills/test-cardholder-data-segmentation, .github/skills/test-cardholder-data-segmentation and .opencode/skills/test-cardholder-data-segmentation in your project.

What does Test Cardholder Data Segmentation need to run?

SKILL.md names no scripts, command-line tools or credentials: Test Cardholder Data Segmentation is instructions for the agent only.

Does Test Cardholder Data Segmentation access the network?

SKILL.md names 2 domains. As links in the text: docs-prv.pcisecuritystandards.org and pcisecuritystandards.org. This is read from the text; nothing was executed.

Is Test Cardholder Data Segmentation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Test Cardholder Data Segmentation use?

Test Cardholder Data Segmentation is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Cardholder Data Segmentation use?

About 928 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 555 tokens, read only when the agent opens those files.

What are the alternatives to Test Cardholder Data Segmentation?

Skills that share tags, products or a category with Test Cardholder Data Segmentation: Security Compliance (sangrokjung/claude-forge, 852 stars), Performing Access Recertification With Saviynt (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Implementing Delinea Secret Server For Pam (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Implementing Hashicorp Vault Dynamic Secrets (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Cardholder Data Segmentation?

cyberful (a GitHub organization) maintains it in cyberful/cyberful, which has 135 GitHub stars. The repository holds 85 skills in this directory. The repository was last updated on August 24, 2026.

Source: cyberful/cyberful on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.