Skip to content

SCOUT v2.7.0 — Phase 2C+ close-out + scenario C sealed

Choose a tag to compare

@R00T-Kim R00T-Kim released this 20 Apr 04:47

Phase 2C+ close-out release. Pivot 2026-04-19 roadmap's detection-strengthening insert is merged (LATTE backward slicing, LARA pattern-based source identification, sink coverage expansion, finding-diversity release gate), with a follow-up ascii_strings wire-through fix that resurrected the inert LARA axis. The compliance-led track ships its Phase 3'.1 suite: four per-standard mappings (CRA Annex I / FDA Section 524B / ISO/SAE 21434 / UN R155) and the new compliance_report pipeline stage.

Reviewer-lane Official Measurement (14/14, Codex LATTE-on, 2026-04-20 13:33 KST)

Gate Threshold Result Verdict
1 Detection recall ≥ 0.40 0.1429 (identical to baseline) FAIL
2 Evidence tier variation ≥ 2 nonzero TP tiers 1 FAIL
3 Finding diversity < 0.5 1.000 (14/14 on single synthesis finding id) FAIL
4 Dedicated rerun ≥ 1/N success 14/14 PASS
5 Pair corpus size ≥ 10 7 FAIL

scripts/release_gate.shRELEASE_GOVERNANCE=FAIL. score_pair_corpus.py --pairs benchmarks/pair-eval/pairs.json{"pairs": 7, "recall": 0.14285714, "fpr": 0.14285714}.

Scenario C Sealing

The 2C+ workstream (LARA source expansion 0 → 21-86 hits/run, LATTE slicing opt-in, sink coverage 28 → 51+, diversity gate enforcement) did not move Gate 1 or Gate 3 because findings.py's primary-finding selection always routes vulnerability evidence through the single synthesis-stage id aiedge.findings.web.exec_sink_overlap. Per the pivot document's scenario C, option D is adopted: Phase 2D' is deferred and SCOUT fully pivots to the compliance-led identity.

Gate-by-gate remediation paths (root cause / required work / track / timeline) are fixed in docs/v2.7.0_release_plan.md "Gate Diagnosis Matrix":

  • Gate 1 recall — external track (detection-engine redesign, 6-12mo+)
  • Gate 2 tier variation — external track (P-code engine robustness)
  • Gate 3 diversity — Phase 3' research track (Option C evidence-level metric redefinition)
  • Gate 4 rerunDONE (becomes the operational backbone for Phase 3'.2 CRA Audit SaaS job queue)
  • Gate 5 corpusv2.7.1 scope (2C+.4 vendor-extraction expansion, 1-2 weeks)

What's New

  • LATTE backward slicing (Phase 2C+.1) — opt-in via AIEDGE_LATTE_SLICING=1, 32 tests
  • LARA URI/CGI/config-key source identification (Phase 2C+.2) — 50 patterns, with ascii_strings wire-through fix on D-Link httpd (0 → 10-33 matches per firmware)
  • Sink coverage 28 → 51+ (Phase 2C+.3) — full CWE taxonomy (78/22/426/732/377/250/269/454)
  • Finding diversity gate (Phase 2C+.5) — PAIR_EVAL_DIVERSITY release sub-gate + pair-eval timeout diagnostic
  • Compliance mapping suite (Phase 3'.1 B-1~B-4) — four standards + compliance_report stage (43rd pipeline stage)
  • Reviewer-lane instrumentation scripts — sequential launcher, watcher handoff, codex/claude LATTE-on launchers

Next Steps (v2.7.1)

  • 2C+.4 Vendor extraction chain expansion (DIR-859 / RT-AC68U / WRT1900ACS / DIR-878 + 1) → corpus 7 → 10+, Gate 5 resolved
  • 3'.1 step B-5 release tag bundling
  • Phase 3'.2 CRA Audit SaaS v0.0 internal alpha kickoff (see wiki/projects/scout-cra-audit-saas-scope.md)

Full changelog: CHANGELOG.md

🤖 Release prepared with Claude Code