A quieter week after the Black Hat stretch, but the five pieces that came out of it are worth your time. All five circle the same territory: what AI can and can't actually do in security, and who ends up owning the outcome when it falls short.
Triaging AI scanner output costs 400x more than running the scan
Here's the number from Contrast Security's AppSec Overflow 2026 report that should reframe every "AI will solve your security backlog" pitch you hear this year: scanning a 2-million-line codebase with an AI-powered tool costs roughly $315 in tokens. Triaging what that scan finds costs $128,000. The scanning was never the expensive part.
The report draws on runtime telemetry from hundreds of thousands of production applications — not theoretical exposure, but what's actually being reached and exploited in live systems. A few data points worth internalizing:
The average application absorbs 11,382 attacks a month. 87.8% are automated probes — noise. The number that actually matters is the 0.4%, an average of 42 viable attacks per month per application, where Contrast confirmed the exploit reached and triggered real vulnerable code. Teams are closing 3.4 vulnerabilities per application per month against an average of 22 rated high or critical. Mean time to remediate a critical vulnerability: 92 days. Mean time to exploit: effectively same-day for a growing share of CVEs.
The AI scanner reliability findings are the most useful part for teams evaluating these tools. Three different AI scanners analyzing the identical codebase agreed on only 5% of findings. A single scanner rerun three times against unchanged code reproduced just 17% of its own prior results. That's not a calibration issue — it's a fundamental reliability problem for any team trying to build a repeatable process around these tools.
One claim worth a caveat: the report opens by citing Anthropic's Claude Mythos model reportedly discovering thousands of previously unknown zero-day vulnerabilities in production testing. Contrast's own report flags the limitation — Anthropic hasn't disclosed the time, accuracy, and human effort behind the analysis. Treat that specific claim as unverified, even as the broader trend it illustrates is real.
Read more
Cisco's Amy Chang: a model's "passport" doesn't tell you where it actually came from
Amy Chang, EVP and Chief Product Officer at Cisco, makes a point that gets at a real gap in how most organizations think about AI supply chain risk: a model card or declared provenance tells you what a vendor says about a model, not what actually went into it. The training data, the fine-tuning process, the intermediate checkpoints — none of that is independently verifiable from the outside. As AI models become infrastructure, the question of what's actually in them starts to matter the way software bill of materials questions started to matter for open-source packages. The tooling to answer it doesn't really exist yet.
Read more
AI can find your vulnerabilities. It still can't own what happens next.
The conversation with GuidePoint Security's Victor Wieczorek covers the same territory as several Black Hat sessions but with more precision. AI is genuinely good at finding needles in haystacks — that's not the bottleneck. The bottleneck is everything downstream: understanding what a finding means in context, deciding what to do about it, and owning the professional judgment that a client can actually act on. No model carries that obligation. The Glasswing stat that runs through this piece is worth remembering: fewer than 1% of the vulnerabilities AI discovered in that program ever got patched. Finding the bug was never the hard part.
Read more
$360,000 a petabyte and 105 days to get out: Microsoft's new math for university storage
Microsoft capped Education tenant storage this year and turned on overage pricing worth roughly $360,000 per petabyte per year once quotas are exceeded. Universities holding two or three petabytes — common at large research institutions — are looking at bills in the hundreds of thousands to over a million dollars annually for storage they never budgeted for. The exit problem is equally sharp: Microsoft throttles data egress at 400GB per hour, tenant-wide, meaning moving one petabyte out takes approximately 105 days. For institutions just realizing the size of the problem, the December 2026 renewal deadline is already close.
Arcitecta's Mediaflux Connect 365 is the platform announced around this story — the piece covers both the cost math and the data management approach behind moving out intelligently rather than just fast.
Read more
The bug that's been breaking software for 40 years is now breaking your AI agents too
Integer overflow — the category of bug where a value exceeds what a data type can hold and wraps around to an unexpected result — has been causing security vulnerabilities since the 1980s. It's behind buffer overflows, memory corruption, and a long list of CVEs across decades of software. The same class of bug now shows up in AI agent tool calls and API interactions, where numeric inputs passed to or from an agent can overflow in ways the agent doesn't detect or handle. The post makes the case that this isn't a new threat category — it's a familiar one arriving in a new execution context, and most teams building agentic systems aren't thinking about it yet.
Read more
The through-line this week: AI is genuinely expanding what's possible in security tooling, and the costs and failure modes that come with it are starting to get documented with real numbers. $315 to scan, $128,000 to triage. 5% agreement across three scanners. Fewer than 1% of discovered vulnerabilities patched. Those aren't arguments against using AI in security — they're arguments for being precise about what it's actually doing and who owns the judgment call when it's done.
See you next Friday.
Developer Weekly Briefing is published every Friday on Coder Legion. Written by Tom Smith.