/requirement
Deep dive on specific PCI DSS requirement
$ npx -y skills add GRCEngClub/claude-grc-engineering --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/requirement
Context preview
What this command does when you run it.
Deep dive on specific PCI DSS requirement
Command definition
requirement.mddescription: Deep dive on specific PCI DSS requirement
PCI DSS Requirement Details
Provides detailed guidance on specific PCI DSS v4.0.1 requirements.
Arguments
- `$1` - Requirement number (required: 1-12 or specific like 3.4.2)
- `$2` - Focus area (optional: controls, testing, evidence)
Requirements Overview
| Req | Title | Key Focus | |-----|-------|-----------| | 1 | Network Security Controls | Firewalls, network segmentation | | 2 | Secure Configurations | Hardening, defaults, inventory | | 3 | Protect Stored Data | Encryption, retention, PAN masking | | 4 | Cryptography in Transit | TLS, secure transmission | | 5 | Malware Protection | Anti-malware, updates | | 6 | Secure Development | SDLC, vulnerabilities, patches | | 7 | Access Restriction | Need-to-know, least privilege | | 8 | User Authentication | Passwords, MFA, accounts | | 9 | Physical Security | Facility access, media | | 10 | Logging and Monitoring | Audit trails, log review | | 11 | Security Testing | Scans, pen tests, IDS | | 12 | Security Policies | Policies, awareness, incidents |
Sub-requirement Format
Requirements follow pattern: `X.Y.Z`
- X = Major requirement (1-12)
- Y = Section
- Z = Specific control
- Additional: .1, .2 for sub-controls
Example
/pci-dss:requirement 3 /pci-dss:requirement 8.4.2 testing /pci-dss:requirement 6.4.3 evidence
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 commands on trust-center.
- /research
Start or resume an academic research project โ idea through literature, methodology, writing, feedback, and publishing
Open command - /collect
Query AWS for compliance-relevant configuration across IAM, S3, CloudTrail, EBS, and emit findings conforming to the v1 contract.
Open command - /setup
Install the frdocx-to-froscal-ssp Python pipeline and verify its dependencies. Idempotent.
Open command - /status
Check the deployment status of the trust center.
Open command - /scan
Run testssl.sh against one or more HTTPS endpoints and emit v1 Findings mapped to SOC 2, NIST 800-53, PCI DSS 4.0.1, ISO 27001, and SCF controls.
Open command - /compliance-posture
Serve a localhost compliance posture dashboard from monitor-continuous JSON
Open command

