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.

Worked example12 min

A worked example: AI Risk Disposition for a Copilot Studio procurement agent

A full worked example: every disposition section filled in for a Copilot Studio procurement agent. Decision, controls, residual risk, sign-off.

Technical11 min

Threat modeling an MCP server — the parts AppSec tools miss

MCP servers have four attack surfaces: transport, tool surface, context injection, auth boundary. AppSec tools model one. The full threat model.

Regulation13 min

EU AI Act Article 9 risk management — what evidence is required

Article 9 requires a risk management system for high-risk AI. Six requirements translated into evidence artifacts auditors will request.

Reference14 min

OWASP Agentic Top 10 mapped to required controls

OWASP Agentic Top 10 threats mapped to controls, lifecycle gates, and evidence -- a working checklist for your AI Committee, not just a list.

Foundations11 min

What an AI Risk Disposition actually contains

AI Committees approve systems they can't defend later. The Decision Memo fixes this -- section by section, with real examples.

Governance11 min

What an agentic AI audit trail must capture

Auditing an agentic system post-incident requires what the model decided and why — not just what happened. Most implementations miss the reasoning trace.

Technical13 min

LLM red-teaming for a security review

Red-teaming an LLM is not pentesting it. Covers goal hijacking, jailbreaking, indirect injection, and exfiltration chains — with documentation guidance.

Foundations10 min

Five mistakes that make an AI security review undefensible

Five structural mistakes that make an AI security review indefensible. Found in nearly every review regardless of threat coverage.

Governance10 min

The security terms an AI vendor contract needs

Standard contracts miss AI-specific terms: model-change notice, training restrictions, incident notification, re-assessment rights. The clause language.

Governance11 min

Preparing for an ISO 42001 internal audit

What an ISO 42001 internal audit must cover, what evidence auditors want, and the gaps that appear most in first-time preparations.

Reference10 min

MCP Server Security Review Checklist (2025)

Structured checklist for MCP server review: transport, authentication, tool manifest, context injection surface, dependencies, and evidence requirements.

Technical10 min

Context-window risks in RAG and how to bound them

The context window is where queries and retrieved documents meet the model. Anything inside influences outputs. How to bound what gets in.