Overview
Part of the DCRH doc set — see 00_START_HERE.md.
What it is
DCRH (Defending Code Reference Harness) is Anthropic's open-source reference implementation for autonomous vulnerability discovery and remediation with Claude — packaged learnings from partnering with security teams at several organizations (the "Glasswing" work). It is a crash-testing crew for source code: recon agents map the attack surface, isolated find agents craft malformed input until a memory-safety-instrumented build crashes reproducibly, a fresh-container grade agent re-verifies the crash without seeing the finder's reasoning, a judge checks for duplicates, a report agent writes the exploitability analysis, and a patch agent drafts a fix that a grading loop tries hard to disprove before trusting it. A parallel detection & response track applies the same verification-first discipline to log corpora instead of source.
Key concepts
- Threat vs. vulnerability — a threat is an architectural property ("attacker achieves
RCE via untrusted media parsing"); a vulnerability is one concrete instance of it.
/threat-modelproduces threats, which is why a zero-bug threat-model run is the skill working correctly, not failing. - Execution-verified vs. static —
/vuln-scanreads source only (nothing built or run);vuln-pipelineactually crashes an ASAN binary, so its findings are execution-verified rather than plausible-looking source review. - Two halves, different trust levels — interactive skills (read/write files only) need no sandbox; the autonomous pipelines execute target code and must run inside gVisor.
- Minimal cross-container information flow — the design pattern that makes grading trustworthy: find → grade crosses only PoC bytes, never the finder's reasoning; the D&R hunt → grade crossing is only the incident submission.
Two halves
- Interactive skills (
.claude/skills/):/quickstart,/threat-model,/vuln-scan,/triage,/patch,/dnr-hunt,/dnr-respond,/customize(+ contributor-only/verify). - Autonomous pipelines:
harness/(vuln-pipeline, ~4,381 LOC) anddnr_harness/(dnr-pipeline, ~876 LOC), both driven throughbin/vp-sandboxed.
Where to go next
- Non-technical:
architecture.htmlin Simple mode. - Technical depth: design/HLD.md then design/LLD.md.
- Module-by-module: architecture.html's Module Flow section or modules/README.md.
- Data flow diagrams: data-flow.html.
- Real code-graph numbers:
Defending Code Harness Vault/DCRH/DCRH — Graph Intelligence Findings.md.
Related: 00_START_HERE.md.