Blog

The thinking behind AI security review.

Threat models, governance evidence, and the decisions that hold up under scrutiny. Written for security architects and the committees they report to.

Newsletter

New posts in your inbox,
when they publish.

Threat modeling, governance evidence, and what AI Committees actually need — written for security architects and AI governance leads. No cadence promises.

No spam. Unsubscribe anytime.

Technical8 min

Reviewing Windsurf (now Devin Desktop) — the CVE that bypassed its own deny-list

A critical path-traversal flaw worked even with auto-execution off and the vulnerable tool explicitly deny-listed. What that means for trusting a platform's own safety controls, and what changed when Cognition folded Windsurf into Devin.

Technical9 min

Reviewing Claude Code and the Claude Agent SDK — permissions, sandboxing, and bypass mode

Distinct from a Claude procurement review: this is Claude Code as a coding agent, its layered permission model, six-plus disclosed CVEs, and the containment guidance Anthropic pairs with its own "YOLO mode" warning.

Technical7 min

Reviewing Databricks Mosaic AI Agent Framework — the gap Databricks names in its own framework

No disclosed CVE here — the real finding is Databricks' own AI Security Framework v3.0 naming a confused-deputy problem: Unity Catalog governs data at rest, but an agent inherits whatever its tools can reach.

Technical11 min

Vector and embedding weaknesses — OWASP LLM08:2025 explained

OWASP LLM08:2025 — embedding-space attacks that recover source text from vectors and poison the retrieval space itself.

Technical8 min

Reviewing Google's Agent Development Kit — the CI workflow that trusted the wrong identity

A path-traversal CVE, a Black Hat-disclosed unauthenticated dev assistant, and a GitHub Action that let anyone with issue-comment access trigger privileged code execution. Three separate ADK findings, one shared root cause.

Technical5 min

Reviewing Amazon Q Developer — the MCP auto-execution CVE

CVE-2026-12957 let a single file in a cloned repository run arbitrary MCP server code and steal AWS credentials, with no prompt and no consent. What a review has to check before enabling IDE-integrated agents.

Technical8 min

Reviewing UiPath Agentic Automation — what the AI Trust Layer certifies, and what it doesn't

ISO 42001 and AIUC-1 certification, zero third-party data retention, and centralized real-time policy evaluation are real. What still depends on how an individual agent's access is actually configured.

Reference11 min

Unbounded consumption in LLM applications — OWASP LLM Top 10 explained

OWASP reframed model-DoS as Unbounded Consumption, covering all uncontrolled resource drains. What reviews must now check.

Vendor review10 min

Fyxer AI security review — full inbox access is the highest-risk AI category

Security review framework for Fyxer AI: OAuth scopes, email content exposure, unidentified LLM provider, and what procurement must verify.

Vendor review10 min

Granola AI security review — meeting notes under the microscope

What a security team should assess before approving Granola: audio processing, sub-processor chain, PII exposure, and eight evidence gaps to close.

Vendor review10 min

Claude AI security review — what a procurement team should assess

A security architect's framework for reviewing Claude before enterprise deployment: data handling, model governance, output safety, and evidence gaps.

Technical6 min

Reviewing Microsoft Copilot Studio agents — three 2026 CVEs and the DLP gap they share

A patched prompt-injection vulnerability still exfiltrated data — because the exfiltration path ran through a legitimate, trusted action that DLP never questioned. What that teaches a review.