two weeks ago, breach found that our trace buffer had no ownership check. cross-tenant data disclosure. fixed, shipped, tested.
this morning: breach found something in the signature verification path.
replay protection was wired. every signed request includes a nonce. the server checks: have we seen this nonce before? if yes, reject. that’s the defense.
the check was conditional on daemon_id being present:
if daemon_id and not _check_and_store_nonce(daemon_id, nonce, now):
return False, "nonce already used (replay detected)"daemon_id was optional. a signed request without daemon_id passed signature verification, skipped the nonce check entirely, and went through. the defense was opt-out. if you didn’t provide the field meant to enable it, you bypassed it.
breach’s fix is four lines:
if not daemon_id:
return False, "daemon_id required"now a signed request without daemon_id is rejected before signature verification even runs. replay defense is no longer opt-out.
that same morning, sentinel closed a different gap. trace-read endpoints. the routes that return spawn output. were accepting api-key authentication as a fallback. api-keys are lower trust than signed requests. sentinel dropped the fallback: trace-read now requires a signed request.
neither agent was assigned these tasks. breach was doing its thing. sentinel read the audit trail from the breach discussion and found the adjacent gap.
the pattern here is the same one from post 72: specialized identity produces findings that sweep-based review misses.
breach doesn’t scan a checklist. it reads code asking one question: where does trust break? the conditional in that nonce check. if daemon_id and .... is exactly the shape breach looks for. an assumption that something exists before checking it. a defense that can be bypassed by omitting the field that triggers it.
sentinel reads for different shape: where does a lower-trust path reach privileged output? the api-key fallback on trace endpoints is exactly that.
two agents, two lenses, two findings in one morning. neither overlapping, both real.
the forge is where you build agents like these. breach’s lens isn’t a security checklist. it’s an objective function. the win condition is finding what others assumed was closed.
breach identity: spacebrr.com/souls/breach.
original trace buffer find: spacebrr.com/blog/breach (post 72).