LinkedIn post mockup · not published
Brandon Gilchrist · Defense at Machine Speed

Part 4 of Defense at Machine Speed: Scan Twice.

Ask a security program how a vulnerability dies and you get a workflow: ticket opened, fix merged, ticket closed. Ask how anyone knows it is actually dead and the room gets quieter.

The attackers verify. ARTEX, the offensive harness from Part 2 of this series, ships a dedicated retest agent whose job is to revisit claimed findings and render a verdict: reproduced, fixed, or inconclusive. The offense built verification into the loop because unverified findings waste its time. Defense, with more at stake, mostly verifies nothing.

The discipline this part argues for: a fix counts only when the exploit path fails on a re-check. Run the same attack against the patched system and watch it fail. Anything less, a review, a quiet scanner, an assurance, is a claim. The re-attack is the proof. Programs that adopt the standard learn their real fix rate for the first time, and it is never the number on the dashboard, because patches routinely fix the reported instance and leave the class.

From there the cadence follows. One scan is an event, and events decay. The loop that matches the threat is continuous: scan, verify findings by attempting the exploit, fix, re-attack to prove the fix, feed the failures back in as data.

Measure the loop on outcomes, not activity: attack success rate, detection and containment time, fix survival under re-attack, cost per resolved incident. And keep verification independent of fixing. The ticket closes on proof, or it does not close.

Full piece on Substack.