Process Optimization: Operate DCRH (Scan → Triage → Remediate)

docs / process / process-optimization

← all docs

Process Optimization: Operate DCRH (Scan → Triage → Remediate)

Analysis of the process documented in process-operate-dcrh.md, using the current-state / waste / future-state / impact framework.

1. Current state

Step Who Typical wait/handoff
Threat model Security analyst None — self-contained, read-only
Scan (static or pipeline) Analyst or engineer Handoff into Triage; pipeline path also waits on sandbox setup if not already done
Triage Security analyst Handoff to Security engineer for patching
Patch Security engineer Handoff to target's engineering owner for review/merge
Act on verdict Target's engineering owner Often the longest wait — competes with the owning team's own roadmap

The process as documented is already fairly lean (5 steps, matching DCRH's own detect → verify → report → patch shape) — the waste below is mostly about operational friction around the steps, not the steps themselves.

2. Waste identified

3. Future state (recommendations)

  1. Stand up a persistent sandbox host (or a small pool) rather than re-running setup_sandbox.sh per invocation. Low effort, removes the largest recurring wait for any team running more than one scan.
  2. Make the small-first-wave step a hard gate in tooling, not just documentation — e.g. a thin wrapper script that refuses --runs > 5 unless a prior smaller run's result.json files exist for the same target. Medium effort (a bin/ wrapper script, not a harness code change).
  3. Track --no-reattack patches distinctly — tag them in PatchVerdict output or a simple checklist so "fast iteration" fixes can't silently become "shipped" fixes without someone consciously accepting the lower verification bar. Low effort.
  4. Add a lightweight shared queue for triage→patch and patch→review handoffs — even a checked-in QUEUE.md per target, or a project-tracker integration if the team already has one, closes the "living only as files on disk" gap without requiring new infrastructure. Low effort, medium impact for teams working multiple targets in parallel.
  5. Prefer hand-written focus_areas in config.yaml for stable targets, reserving --auto-focus for first scans or after a target's attack surface changes materially. Zero engineering effort — a documentation/practice change, already technically supported.
  6. Add a scheduled-run wrapper (cron, or the team's existing CI) around bin/vp-sandboxed run <target> --auto-focus --stream for targets under active development, feeding results into the existing /triage --auto cross-run aggregation. Medium effort, directly enables the repo's own recommended "incorporate scans into your SDLC" adoption path.

4. Estimated impact

Change Time saved per cycle Effort to implement
Persistent sandbox host Removes ~5–15 min setup per scan session (image build + gVisor checks) Low
Enforced small-first-wave gate Avoids re-running a mis-calibrated large batch (potentially hours + token spend) Medium
--no-reattack tagging Prevents shipping under-verified fixes (risk reduction, not time) Low
Shared triage/patch queue Reduces status-chasing between analyst/engineer/owner Low–Medium
Stable-target focus_areas Skips a recon agent invocation per run (minutes + tokens) Zero (practice only)
Scheduled scans Converts ad hoc scanning into steady-state coverage — not a per-cycle time save, but closes the "we only scan when someone remembers" gap Medium

5. Implementation plan

  1. This week: Adopt the practice changes with zero engineering cost — hand-written focus_areas for stable targets, explicit --no-reattack tagging discipline in patch PR descriptions.
  2. This sprint: Stand up the persistent sandbox host; write the small-first-wave gate wrapper script.
  3. Next sprint: Evaluate whether the team's existing project tracker can host the triage→patch→review queue, or whether a simple QUEUE.md convention is sufficient given current scan volume.
  4. Ongoing: Once scan cadence stabilizes, add the scheduled-run wrapper and fold its output into the same triage/patch loop.

Related: process-operate-dcrh.md · runbooks/.