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.

Regulation10 min

Building an EU AI Act system inventory

The EU AI Act requires knowing every AI system you deploy and its tier. Here's how to build that inventory when AI hides in SaaS and vendor products.

Technical11 min

Data poisoning in RAG knowledge bases

RAG knowledge base poisoning inserts malicious content not to corrupt the index, but to influence model outputs when poisoned documents are retrieved.

Technical12 min

Mapping the agentic AI attack surface

Five layers of the agentic AI attack surface — prompt channel, tool surface, memory, orchestration boundary, output channel — mapped with controls.

Technical12 min

Prompt injection, explained for security reviewers

What prompt injection actually is, how its variants work, how it differs from SQL injection, and which controls reduce the risk in practice.

Reference12 min

The AI security review checklist, by lifecycle gate

A lifecycle-gate checklist for AI security reviews: intake through production, with gate-specific questions and evidence needs.

Reference10 min

The AI section your vendor security questionnaire is missing

The AI vendor risk assessment questionnaire your procurement process is missing — model governance, re-assessment triggers, incident notification.

Governance11 min

Writing an AI governance committee charter

A committee without a charter is a meeting with a name. Authority, composition, quorum, decision types, and escalation paths defined.

Technical11 min

MCP security — the four attack surfaces of a Model Context Protocol server

MCP servers expose tools, resources, and prompts — each an attack surface. Defines the four surfaces and review questions for each.

Reference12 min

ISO 42001, explained for security teams

ISO 42001 explained for security teams: what the AI management system standard requires, how it differs from 27001, and what auditors expect.

Technical10 min

RAG security — the three boundaries that matter

RAG adds three security boundaries between user and model: data, retrieval, and context. Each has distinct failure modes a standard LLM review misses.

Regulation11 min

EU AI Act risk tiers, explained for engineers

Four risk tiers determine your EU AI Act obligations. How to classify your system and what each tier demands.

Technical11 min

Agentic AI security — the surfaces deterministic software does not have

Agentic AI security covers four surfaces deterministic software lacks: hijackable reasoning, tool manifests, persistent memory, drifting goals.