research
Start or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
Validate control implementation against framework requirements
> /plugin marketplace add GRCEngClub/claude-grc-engineeringHow it fires
How this command gets triggered: by you, by Claude, or both.
/validate-controlContext preview
What this command does when you run it.
Validate control implementation against framework requirements
description: Validate control implementation against framework requirements
Tests and validates that a control is properly implemented and effective.
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:
# 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
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
Start or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
Query AWS for compliance-relevant configuration across IAM, S3, CloudTrail, EBS, and emit findings conforming to the v1 contract.
Install the frdocx-to-froscal-ssp Python pipeline and verify its dependencies. Idempotent.
Retrieve a single AWS Secrets Manager secret value to stdout or a 0600-permission file. Opt-in retrieval mode — never writes to the findings cache.
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.