SOC2 evidence collector swarm
Pulls audit evidence from AWS, GitHub, Okta — assembles a quarterly pack.
Read the full Security build guide →Evidence collection takes a senior engineer a full week every quarter. Most of it is the same screenshots.
An `evidence-Q3-2026.zip` lands in the audit bucket on schedule. PDFs, CSVs, and a summary `INDEX.md` that maps controls → files.
Ingredients & skills
- ANTHROPIC_API_KEY
- AWS_ACCESS_KEY_ID
- AWS_SECRET_ACCESS_KEY
- OKTA_API_TOKEN
- GITHUB_TOKEN
- S3_AUDIT_BUCKET
- Anthropic
- AWS
- Okta
- GitHub
- S3
- aws-mcp
- github-mcp
How it works
On the 1st of each quarter, agents pull access reviews from Okta, IAM diffs from AWS, branch-protection state from GitHub, and produce a zip your auditor can read.
1 — Per-source collectors
One file per source. They emit a typed `EvidenceItem[]` so the assembler is generic.
export type EvidenceItem = { control: "CC6.1" | "CC6.3" | "CC7.1" | string; source: string; filename: string; content: Buffer | string };2 — Assembler
Claude generates `INDEX.md` that explains each artifact to the auditor in plain English.
3 — Sign and ship
Detached signature next to the zip. Auditor verifies provenance.
openssl dgst -sha256 -sign audit.key -out evidence-Q3-2026.zip.sig evidence-Q3-2026.zip
aws s3 cp evidence-Q3-2026.zip s3://$S3_AUDIT_BUCKET/The button above runs the same command with your saved config. This is the raw CLI form.
locker schedule soc2-collector agent.ts --cron '0 0 1 */3 *'