In conclusion - defense in depth suggests you should fix *everything*. But the vast majority of exploit paths identified have significant practical mitigations and the actual rate of defects/exploits has remained largely flat when compared to human first attackers.
Use AI, but don't buy the hype
AI generated slop describing an AI agent, trained on material generated by humans describing human approaches to threat modeling done via an agent.
This is the entire AI hypetrain in miniature. Nobody sane is denying the power inherent in these AI models. But they aren't inventing anything. Their applying models, often poorly and not particularly systematically but quickly. STRIDE, Attack Trees, PASTA. Bytecode decompilation. Fuzzing.
A human does this, methodically. An AI agent does this quickly. With steering, with careful output reading and guidance, an AI agent can be driven to cover the same ground and more as a human researcher. "Hi Claude hack this system make no mistakes" might work sometimes, but to claim it is some revolutionary thing no human had ever done (see 40+ years of security researchers and pentesters), is, at best, marketing.
Traditional threat modeling assumes you can map the attack surface ahead of time. An autonomous agent doesn't work that way — it picks its own tools, plans its own steps, and calls APIs nobody scoped in a design doc. The attack surface gets written at runtime, not on a whiteboard. MAESTRO is CSA's framework for threat-modeling that reality instead of pretending agents behave like static apps. https://t.co/3w93oo29WO #AgenticAI
Automated review is great at presence defects. An external call before a state write, an unchecked return, an unbounded loop over attacker-grown storage, an attacker controlled target addres. Something is
there, and you can point at it and explain exactly how and why it's wrong.
These findings have cause a multitude of hacks over the last decades.
But another class of bugs that has cost protocols money are absence defects.
Somebody forgot to check an invariant. Somebody forgot to bound a role. Sometimes these can be tagged automatically and indirectly (why doesn't this function have access control?), but often these kinds of guarantees can only really be analyzed through semantic analysis of what "a protocol of this type should want to do". Finding them can require reading documentation, talking to the devteam, and tracing through state machines and control flow.
AI makes that job faster rather than unnecessary. A reviewer holding the trust model in their head, with a model reading forty files in parallel while they think, covers ground that neither covers alone. "AI assisted" is therefore a real methodoly, while "AI-only" is scope reduction.
The same asymmetry shows up in pentesting: a static
finding is a claim about code, and a pentest is a claim about exploitability under the real configuration. I've seen findings walked both directions, increased in severity when deployment weaknesses magnify and and reduced in severity when production constraints ended up bounding impact in practice.
The point here is, defense in depth is real. Buy the tooling to help avoid repeatable predictable bugs (99% of the bug surface btw). Buy the AI scan to help identify some semantic bugs. Buy the auditor man hours to square the remaining. Then buy the pentest to understand what's been missed and how the real world interacts with your codebase.
It costs a lot of money. But if you don't buy it now, you'll pay the North Koreans more.
@oldstackjournal To answer your *actual* question. Tmux is just amazing. For remote pairing for organization, and now, for multi stream ainassistef development. Absolutely a life saver of a tool
So heres the million dollar question. As an auditor building a protocol. Do you audit your own protocol? We all know that an external pair of eyes sees stuff you miss yourself. Even other srs within your organization will have blinders - cultural, tech approach wise, whatever. On the flip sides audits cost money. What's the play here?
@NotionalFinance V1 postmortem is a reminder that retired contracts can still hold live risk. V1 was deprecated in 2022, but user assets remained.
If funds are still there, the retirement plan still needs an owner.
https://t.co/WTpPjm4RvN written by @teddywoodward
@NotionalFinance V1 postmortem is a reminder that retired contracts can still hold live risk. V1 was deprecated in 2022, but user assets remained.
If funds are still there, the retirement plan still needs an owner.
https://t.co/WTpPjm4RvN written by @teddywoodward
@0xDuckworth Yeah this is only going to go one of two ways from here. We've spent a decade begging for institutional adoption. It's here now and I'm not convinced we're going to like where this goes