Sakana's orchestration model just beat frontier AI on cybersecurity benchmarks

Sakana's orchestration model just beat frontier AI on cybersecurity benchmarks

Good morning πŸ‘‹ A model that's mostly plumbing just out-scored the models everyone's watching. Sakana wired existing AIs into a tighter loop and beat the frontier at its own cybersecurity benchmarks.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


πŸ”­ THE ONE THING

πŸ›‘οΈ Sakana's orchestration model just beat frontier AI on cybersecurity benchmarks

Sakana AI released Fugu-Cyber on July 20, an update to its orchestration model that scored 86.9% on CyberGym and 72.1% on CTI-REALM, edging out GPT-5.5-Cyber (85.6% CyberGym) and Claude's Mythos Preview (83.1% CyberGym). Sakana's framing is blunt about why: "a highly capable API with strong cyber reasoning is... not the entire solution," so rather than chase a bigger base model they wired existing ones into a tighter agent loop and beat the frontier at its own benchmarks. Worth watching, not worth crowning. These are first-party numbers, on tasks built for exactly this kind of tool-calling harness, and nobody outside Sakana has rerun them yet. For builders the signal is real either way: a well-tuned orchestration layer can now out-benchmark the frontier models feeding it.


🧠 MODELS & RELEASES


πŸ”¬ RESEARCH HIGHLIGHTS


πŸ› οΈ TRY THIS

Distill reasoning into a small model for your own security triage, instead of paying for a frontier one

1. Pull a batch of your own security tickets or alerts that have a verdict but no written reasoning behind it, most incident logs never captured the "why."

2. Run the self-distilled reasoning pass AWS describes for Nova fine-tuning: have the model reconstruct the reasoning trace after the fact, then fine-tune on what it produced. Exploring self-distilled reasoning for SFT with Amazon Nova

3. Test the fine-tune against a held-out slice of your own incidents, not a public benchmark. Sakana's benchmark parity claim is exactly the kind of thing you shouldn't take on faith for your own data.

4. If the model needs to actually act (open a ticket, escalate, kick off mitigation), wire it through an orchestration layer rather than hand-rolling it. AWS's new walkthrough builds a supply-chain risk agent on Quick + NeMo Agent Toolkit; the pattern maps cleanly onto security triage. Build specialized agent workflows with Amazon Quick and NVIDIA NeMo Agent Toolkit

Prompt: Here is a resolved security incident with no recorded reasoning: [paste ticket]. Write the step-by-step reasoning an analyst would have used to reach this resolution, then output it as a training example pairing the original alert with that reasoning trace.

Worth a look


πŸ”— QUICK LINKS


That's the stack for today.

Pradeep Perugu

Get inovAIte in your inbox.