From poam-automation
Import scanner findings, enrich with NIST controls, and generate VDR outputs
How this command is triggered — by the user, by Claude, or both
Slash command
/poam-automation:collectThe summary Claude sees in its command listing — used to decide when to auto-load this command
# POA&M Automation — Collect Runs the full collection pipeline: import scanner findings into the POA&M, enrich with NIST 800-53 mappings, and generate FedRAMP 20x VDR outputs with live CISA KEV and EPSS enrichment. ## Import Scanner Findings ## Enrich with NIST 800-53 Controls ## Generate FedRAMP 20x VDR Produces `vdr_YYYYMMDD.xlsx` and `vdr_YYYYMMDD.json`. The JSON is schema-conformant and ready for API serving. ## Generate Product VDR For software vendors publishing per-release vulnerability disclosures to customers. ## Export for Assessor Submission ## JSON Output The...
Runs the full collection pipeline: import scanner findings into the POA&M, enrich with NIST 800-53 mappings, and generate FedRAMP 20x VDR outputs with live CISA KEV and EPSS enrichment.
python3 grc_tool.py convert --input <scanner_export> --scanner <nessus|tenable|qualys|wiz|generic> --output master_poam.xlsx
python3 grc_tool.py enrich --poam master_poam.xlsx
Produces vdr_YYYYMMDD.xlsx and vdr_YYYYMMDD.json. The JSON is schema-conformant and ready for API serving.
python3 grc_tool.py vdr --poam master_poam.xlsx --baseline <low|moderate|high>
For software vendors publishing per-release vulnerability disclosures to customers.
python3 grc_tool.py product-vdr --input vulns.csv --product "<name>" --version "<version>"
python3 grc_tool.py export --poam master_poam.xlsx --output fedramp_submission.xlsx
The vdr command produces a vdr_YYYYMMDD.json file that conforms to the GRC Engineering finding schema. Each active vulnerability maps to an evaluation object with:
control_framework: FedRAMP-20xcontrol_id: Tracking ID (POA&M ID)status: fail (active) or skipped (accepted)severity: mapped from N-rating (N5=critical, N4=high, N3=medium, N2=low, N1=info)message: weakness name and CVEremediation: overall remediation plan with EPSS and KEV context/collectScans GitHub repositories in a specified scope for SCF compliance controls like branch protection, secret scanning, and Dependabot, emitting JSON findings per repository.
/collectScans AWS for compliance issues across IAM, S3, CloudTrail, EBS; emits JSON findings with SCF checks and severities.
/collectScans GCP project for compliance configs in IAM, Cloud Storage, audit logs, KMS, Compute; emits JSON findings to cache and stdout summary.
/collectScans Okta org for authentication policies, MFA enrollment, password policy, session settings, admin users, and logs. Emits schema-conformant security findings.
/collectCollects URLs, text notes, or file paths into PARA-classified knowledge storage. Use --search "query" to find existing collections.
7plugins reuse this command
First indexed Jul 10, 2026
Showing the 6 earliest of 7 plugins
npx claudepluginhub mrcodechef/claude-grc-engineering --plugin poam-automation