research
Start or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
Serve a localhost compliance posture dashboard from monitor-continuous JSON
> /plugin marketplace add GRCEngClub/claude-grc-engineeringHow it fires
How this command gets triggered: by you, by Claude, or both.
/compliance-postureContext preview
What this command does when you run it.
Serve a localhost compliance posture dashboard from monitor-continuous JSON
description: Serve a localhost compliance posture dashboard from monitor-continuous JSON
Serves a local HTML dashboard from saved `/grc-engineer:monitor-continuous` JSON output.
Implementation: [`scripts/serve.js`](../scripts/serve.js).
/dashboard:compliance-posture --data=<path> [--port=8787]
Local script form:
node plugins/dashboards/compliance-posture/scripts/serve.js \ --data=grc-data/dashboard/monitor-continuous \ --port=8787
comma-separated paths.
Generate dashboard input with:
node plugins/grc-engineer/scripts/monitor-continuous.js SOC2,NIST-800-53 \ --output=grc-data/dashboard/monitor-continuous/$(date +%Y%m%dT%H%M%S).json \ --no-exit-code
The dashboard reads the saved JSON manifests and computes latest state, trends, and deltas at view time. It does not require Claude to retain historical state.
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.