Blog

Analysis on enterprise AI governance, inline policy enforcement, agentic AI security, and regulatory compliance.

Taiwan’s Multi-Agent Campaign Puts Agent Identity on the Security Review

Taiwan disclosed a hybrid, agent-assisted campaign against government agencies in August 2026. The incident belongs to conventional intrusion response, but it also gives enterprise security teams a concrete reason to govern the HTTP model calls made by internal agents with identity-bound policy and decision records.

Problem-Awareagentic-aicybersecurityidentity-and-authorizationpolicy-enforcementai-security
Read post →

ISO 42001 Audit Evidence: What an AI Gateway Record Proves for Your AIMS

ISO 42001 certifies an AI management system, and a certification audit tests whether your controls operate and asks for evidence. Most AIMS documentation describes policy for AI use without a record that a given model call was governed. This piece maps AI gateway records onto the ISO 42001 controls an auditor samples, so operational control over AI use produces artifacts instead of assertions.

Compliance & Regulationiso-42001'compliance''ai-audit''evidence''aims'
Read post →

AI Audit Log Retention Requirements: How Long to Keep Model Call Records

Different regimes impose different retention obligations on AI records, and the safe default is the longest applicable period. This piece walks the retention expectations behind EU AI Act record-keeping, SOC 2 observation windows, and financial-sector rules, then shows what a per-decision model call record has to carry to still be useful years after the request it documents.

Compliance & Regulationai-audit'compliance''audit-logs''eu-ai-act''retention'
Read post →

AI Gateway Data Residency: Enforcing Region Policy on Every Model Call

Data residency for AI breaks the moment a prompt leaves your region for a model endpoint in another one, and application code rarely records where the call went. This piece shows how an AI gateway turns residency from a hopeful configuration into an enforced, logged control: identity and data class decide which regional endpoint a call may reach, and every decision is recorded with its destination.

AI Security Solutionsai-gateway'data-residency''ai-security''policy-enforcement''compliance'
Read post →

Indirect Prompt Injection Defense: Containing What the Model Was Told to Do

Indirect prompt injection hides instructions inside content an AI agent reads, a web page, a document, a tool result, and the model acts on them as if they came from you. No request filter reliably stops a model from being fooled. This piece is honest about that limit and shows where the defensible control sits: identity-scoped authorization on what the agent may then do, plus a per-decision record of what it did.

Problem-Awareprompt-injection'agentic-ai''ai-security''authorization''audit-trail'
Read post →

AI Agent Tool Call Authorization: Deciding Per Call, Not Per Session

An AI agent authenticates once and then makes hundreds of tool and model calls, most systems authorize the session and wave the rest through. That is the post-authentication gap. This piece shows what per-call authorization for agents looks like: each tool call checked against the agent identity, its scope, and the parameters it carries, decided inline, and recorded.

Problem-Awareagentic-ai'authorization''ai-agent-identity''ai-security''access-control'
Read post →

How to Log LLM Requests: The Fields a Model Call Record Needs

Logging an LLM request as if it were a generic HTTP call captures a timestamp, a status code, and a shared key, which answers almost none of the questions an incident or an audit asks. This piece defines the fields a model call record actually needs, why application code is the wrong place to write them, and what a per-decision record looks like in practice, with a concrete schema.

Platform & Architecturellm-logging'ai-audit''observability''ai-security''engineering'
Read post →

mTLS for an AI Gateway: Proving Which Service Made the Model Call

A bearer key in front of an AI gateway proves possession of a secret, not the identity of the service that holds it, and a leaked key is indistinguishable from the real caller. Mutual TLS binds each calling service or agent to a certificate the gateway verifies on every connection. This piece shows what mTLS establishes for AI traffic, what it does not, and how it feeds the authorization decision.

Platform & Architecturemtls'ai-gateway''zero-trust''authorization''engineering'
Read post →

AI Gateway for Legal Firms: Keeping Privileged Data Inside Policy

Lawyers paste privileged client material into AI tools to draft and summarize, and a firm carrying a duty of confidentiality usually has no record of which matter that data belonged to or where it went. This piece shows how an AI gateway puts model traffic under matter-aware policy and produces the per-decision record a firm needs to show client data stayed inside its obligations.

Industry Verticalslegal'ai-security''confidentiality''ai-gateway''compliance'
Read post →

AI Gateway for Government Agencies: Identity and Audit for Public-Sector AI

Public-sector AI use carries obligations most agency deployments cannot yet meet: zero-trust access, a defensible record of automated decisions, and evidence for oversight and public-records requests. This piece shows how an AI gateway extends identity-aware access control and per-decision logging to model traffic, so an agency can govern AI use and produce the record its accountability rules assume.

Industry Verticalsgovernment'public-sector''zero-trust''ai-audit''compliance'
Read post →

Non-Human Identity Security When Machines Outnumber People 109 to 1

Non-human identities, service accounts, API keys, workloads, and now AI agents, outnumber humans by more than 100 to 1 in the average enterprise (Palo Alto Networks, 2026). They carry static long-lived credentials, skip MFA, and share keys, which means the audit trail names a credential rather than an actor. This piece explains what an NHI is, why it resists the controls built for people, the specific attribution problem AI agents add on a shared key, and where identity-bound authorization on each AI call fits.

AI Security Solutionsai-securityidentity-and-authorizationagentic-aizero-trustcybersecurityaudit
Read post →

HIPAA-Compliant AI Tools: The Criteria That Decide Whether a Tool Qualifies

A vendor badge that reads "HIPAA compliant" answers one question and stays silent on the two that an OCR review probes. This guide gives healthcare compliance teams the three-part Security Rule test for any AI tool (a signed BAA under 45 CFR 164.502(e), access control under 164.312(a), and audit controls under 164.312(b)), walks the tool categories a covered entity actually assembles, and shows where the residual access-control and audit obligation stays with the covered entity after every BAA is signed.

Industry Verticalshipaahealthcareai-complianceai-securityidentity-and-authorizationauditpolicy-enforcement
Read post →