Skip to content
Security
Command

/validate-control

Validate control implementation against framework requirements

From plugin
trust-center
367139 skills139 commands1 MCP
Install
$ npx -y skills add GRCEngClub/claude-grc-engineering --agent claude-code

How 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/validate-control

Context preview

What this command does when you run it.

Validate control implementation against framework requirements

Command definition

validate-control.md
description: Validate control implementation against framework requirements

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

# 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
Ships withtrust-center

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.

Get the whole plugin, auto-invoked
Stats
367
Stars
0
Views
82
Forks
Active
Maintenance
JavaScript
Language
1d ago
Last commit
7mo ago
Created

Repo: GRCEngClub/claude-grc-engineering