読書リサーチレーダー投資フレームワーク
ログイン / 新規登録
← 読解に戻る
ニューストピック · AI漏洞验证瓶颈重大3 分で読めるDisconfirmAI 編集部

AI Security Agents from Four Labs Converge on a Common Design: Discoverers Cannot Confirm Their Own Findings

Anthropic, OpenAI, Cloudflare, and Google each released AI security scanning agents in 2026, yet their architectures converged significantly: one agent identifies vulnerabilities while a separate, independent agent attempts to disprove them, with only surviving findings proceeding to patching. This design is an engineering response to the noise problem in AI scanning—Google reports true-positive rates below 7%, and Snyk found that 49.7% of pure LLM review findings disappeared on the next run.

2026-10-31 01:34 GMT+8

AI code security scanning faces a quantifiable reliability crisis. The Google security team publicly stated that crude AI code scanning produces hallucinated vulnerabilities, with true-positive rates under 7%—meaning a scanner that is wrong 93% of the time imposes higher costs on reviewers than it saves. Snyk’s own VulnBench tests further confirmed the ubiquity of the issue: 49.7% of findings from pure LLM reviews vanished on the next run, indicating that single model outputs are far from stable.

Facing the same problem, Anthropic, OpenAI, Cloudflare, and Google each released AI security scanning agents in 2026, converging on nearly identical designs: one agent responsible for finding vulnerabilities, another independent agent responsible for disproving them, with only findings that withstand rebuttal entering the patching phase. Cloudflare states this rule most plainly in its README: the verifier is never the agent that found the bug. Anthropic, OpenAI, and Google each described similar validation steps, requiring independent questioning before any finding reaches a report.

This convergence is not coincidental but an engineering response to the noise problem. The core principle is separation of duties: the agent reporting a finding never holds the power of confirmation. This aligns with peer-review logic in human security audits—the author cannot review their own work. In the context of AI agents, this means two independent model calls (or even two different models) must reach a consistent conclusion about the same finding before proceeding. Cloudflare also adopted a more specific practice: using different models for discovery and triage, allowing models to check each other.

ログイン / 新規登録
読書リサーチレーダー投資フレームワーク

The differences among the four tools lie in the depth of verification and the operating environment. Anthropic’s Claude Security plugin runs within a Claude Code session, requiring no additional API keys; scans count against the user’s existing plan quota, outputting Markdown reports and SARIF files, with patches generated as .patch files but not automatically committed. OpenAI’s Codex Security offers a CLI and SDK, supporting deep-mode parallel discovery, and can import GitHub scanning alerts, but while the client is open source (Apache-2.0), the backend scanner still requires OpenAI access. Cloudflare’s Audit Skill is MIT-licensed and model-agnostic, requiring a coding agent that supports parallel sub-agents, ideally needing an OS-level sandbox with no external network—without a sandbox, findings remain in a needs_validation state rather than being executed. Google’s Mantis is the most aggressive: it attempts to reproduce each vulnerability in a sandbox, from static exploit sketches to unit tests or mock servers, and includes an adversarial loop in the patching phase that specifically attacks its own fixes.

Cloudflare’s publicly shared internal data reveals a notable leverage point: improving reconnaissance context (i.e., allowing the agent to fully understand architecture, trust boundaries, and input surfaces first) reduced the first-round rejection rate from 40% to 11%. This indicates that the upstream bottleneck for finding quality is not insufficiently strict verification, but insufficient initial understanding. Of 20,799 raw candidate findings, approximately 12,057 passed validation, resulting in 7,245 actionable findings sent to engineering teams.

The transferable lesson from this convergence pattern is: for any workflow relying on AI agent outputs where noise is a core constraint, the most reliable architectural improvement is not making the same agent more cautious, but introducing structural adversarial verification. Separating discovery from confirmation is the lowest-cost method for quality enhancement, and investment in context during the reconnaissance phase may have a greater impact on the final signal-to-noise ratio than the strictness of the verification stage.

Boundaries to retain: All performance figures above are self-reported by the respective companies, lacking independent third-party replication. Cloudflare’s 40%→11% improvement is based on its internal 128 codebases and may not apply to external projects. Google’s 7% true-positive rate is a description by its security team of its own scanning experience, not a standardized benchmark test result. This architectural convergence itself is a publicly verifiable fact—all four tools’ repositories and documentation demonstrate the same multi-agent verification pattern—but the actual effectiveness of each tool still requires independent evaluation.

ソース

  • marktechpost.comMarkTechPost↗
トピック

AI漏洞验证瓶颈

【背景】2026年,随着Anthropic Project Glasswing及各大实验室AI安全代理的普及,代码漏洞发现速度呈指数级增长,但“验证瓶颈”成为新危机:AI生成的海量候选漏洞远超人类或自动化系统的复核能力。

6 ステップ2 件更新日 2026-11-07 05:13

経緯

  1. 2026-04-07Anthropic启动Project Glasswing,向12家主要技术合作伙伴提供Claude Mythos Preview模型用于自主漏洞研究。labs.cloudsecurityalliance.org ↗
  2. 2026-05-22CSA报告指出,Glasswing已披露1596个开源漏洞,但仅97个被确认修补,凸显修复能力滞后于发现速度。labs.cloudsecurityalliance.org ↗
  3. 2026-08-11Security Affairs报道“验证债务”问题,调查显示仅20.3%的团队能处理单次评估产生的500+ AI生成漏洞候选项。securityaffairs.com ↗

未解決の問題

  • 双代理“独立证伪”架构能否将误报率降低至可接受水平,从而减轻维护者负担?
  • 开源社区是否有足够的资金和人力基础设施来消化AI生成的海量高置信度漏洞报告?
  • 形式化验证或神经符号方法是否能在不牺牲速度的前提下解决业务逻辑层面的验证难题?

このスレッド内の他の記事

  • Comcast CISO Says AI Discovery of Vulnerabilities Makes Validation the New Bottleneck2026-10-23
トピック全文を読む →
リサーチを続ける →