Stats
Actions
Tags
From grc-auditor
Validate control implementation against framework requirements
How this command is triggered — by the user, by Claude, or both
Slash command
/grc-auditor:validate-controlThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Validate Control Tests and validates that a control is properly implemented and effective. ## Arguments - `$1` - Control ID (required, e.g., CC6.1, A.9.1.1, AC-2) - `$2` - Framework (optional, defaults to auto-detect) ## Instructions 1. Identify the control requirements from the framework 2. Design test procedures to validate the control 3. Execute or guide testing activities 4. Document findings with: - Control objective - Test procedures performed - Results (Pass/Fail/Partial) - Evidence references - Exceptions noted ## Examples
Tests and validates that a control is properly implemented and effective.
$1 - Control ID (required, e.g., CC6.1, A.9.1.1, AC-2)$2 - Framework (optional, defaults to auto-detect)# SOC 2 control validation
/grc-auditor:validate-control CC6.1 SOC2
# PCI-DSS requirement validation
/grc-auditor:validate-control 8.4.2 PCIDSS
# ISO 27001 control validation
/grc-auditor:validate-control A.9.1.1 ISO27001
# NIST 800-53 control validation (auto-detect)
/grc-auditor:validate-control AC-2
7plugins reuse this command
First indexed Apr 26, 2026
Showing the 6 earliest of 7 plugins
npx claudepluginhub vantainc/claude-grc-engineering --plugin grc-auditor/validate-controlValidates a control ID (e.g., CC6.1, AC-2) against frameworks like SOC2, PCI-DSS, ISO27001, or NIST by identifying requirements, designing/executing tests, and documenting results with pass/fail status, evidence, and exceptions.