Blog

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

LLM gateway vs LLM router: what each component does and why the enforcement layer sits in only one of them

The LLM gateway and the LLM router occupy different layers in an AI stack even when a vendor bundles them under one label. The gateway is the identity-aware policy enforcement point that sits between authenticated users and any LLM. The router is the traffic-shaping component that decides which model handles a given request. Confusing the two produces predictable failure modes at audit time. This piece walks through the two components, the fields each layer records, and how the policy decision at the gateway constrains what the router is allowed to route to.

Platform & Architecturellm-gatewayllm-routerai-architectureai-policy-enforcementai-control-plane
Read post →

Tennessee's AI therapist-impersonation ban is now in force: the enforcement problem for healthcare chatbot deployers

Tennessee SB 1580 took effect July 1, 2026 and prohibits AI systems from presenting themselves as licensed mental-health professionals. Digital-health, EAP, and payer platforms running patient-facing conversational AI now face a concrete evidence problem: proving the model never claimed licensure across millions of conversation turns. Tennessee Attorney General enforcement applies. This piece walks through the statute, the enforcement architecture (response-side policy plus per-decision audit logs), and how the same controls extend to the 2026 state chatbot wave landing in Utah, California, and New York.

Industry Verticalshealthcare-aicomplianceregulationchatbotauditstate-ai-laws
Read post →

The EU AI Act high-risk deadline just moved to December 2027. Here is what still hits on August 2, 2026

The EU Council gave final approval to the Digital Omnibus on AI on June 29, 2026, deferring standalone Annex III high-risk obligations from August 2, 2026 to December 2, 2027. Embedded high-risk systems slide to August 2, 2028. Article 50 transparency obligations still apply on August 2, 2026, and the grace period for AI-content labeling was cut from six to three months, landing on December 2, 2026. A new prohibition on non-consensual intimate imagery generation applies from December 2026. The workstreams a policy gateway supports keep their 2026 deadlines.

Compliance & Regulationeu-ai-actcomplianceregulationai-governanceomnibusaudit
Read post →

Agent-to-Agent TLS: Mutual Authentication Between AI Agents in a Multi-Agent Workflow

A multi-agent workflow chains AI agents where each agent calls the next over an HTTP transport. The security posture of the chain depends on the mutual authentication between the agents at each hop. This piece walks through the mTLS pattern for agent-to-agent authentication, the certificate lifecycle, and the inspection-layer architecture that binds every agent-to-agent call to a verified identity pair.

Platform & Architectureagent-to-agentmtlsai-agent-securitymulti-agentai-engineering
Read post →

AI Audit Log Immutability: Object Lock, WORM Storage, and the Storage-Layer Contract a Regulator Accepts

The reconstruction test a regulator applies during an AI audit assumes the log record has not been rewritten. The assumption fails when the log lives in a storage layer that permits modification by the same operator who runs the AI application. This piece walks through the immutability contract at the storage layer, S3 Object Lock and Azure Blob immutability policies as implementations, and the audit-record shape that verifies immutability by construction.

Platform & Architectureai-audit-logsimmutabilityobject-lockcomplianceai-engineering
Read post →

AI Red Teaming Workflow: The Test-Fix-Prove Loop for Enterprise AI Deployments

AI red teaming discovers vulnerabilities in prompt handling, tool-call authorization, and response classification. The finding is one artifact. The fix is another. The evidence that the fix works is a third. This piece walks through a red-teaming workflow that produces all three artifacts inside the enterprise control boundary, and the inspection-layer architecture that turns findings into policy the enforcement layer executes.

Platform & Architecturered-teamingai-securitypenetration-testingai-engineeringai-governance
Read post →

LLM Response Schema Validation: When JSON Mode Is Not Enough

JSON mode and structured output constrain the LLM to produce valid JSON, but the JSON can still contain values that violate business policy, personal data that violates data-classification policy, or tool-call arguments that violate authorization scope. This piece walks through what JSON mode covers, the semantic-validation gap it leaves, and the inspection-layer architecture that runs schema validation and semantic validation on the same response path.

Platform & Architecturellm-engineeringjson-schemaai-engineeringstructured-outputai-security
Read post →

Anthropic vs OpenAI Enterprise Controls: Where the Provider Stops and the Enforcement Layer Starts

Anthropic Claude Enterprise and OpenAI ChatGPT Enterprise both publish enterprise control surfaces: SSO integration, audit log APIs, admin consoles, data residency options. This piece compares the two on the controls that actually determine compliance posture, and identifies the enforcement gap that neither provider closes at the request layer.

Comparisons & Alternativesanthropicopenaicomparisonenterprise-controlsai-security
Read post →

AI Agent OAuth Consent: The Permission Screen Users Never Read and the Blast Radius It Grants

An AI agent that authenticates to a SaaS application via OAuth requests a consent scope from the user. The scope grants the agent standing authorization to call APIs on the user behalf. Users grant scopes they do not read, and the standing authorization outlasts the interaction that produced it. This piece walks through the OAuth consent mechanism, the blast radius it creates, and the inspection-layer controls that constrain the scope after grant.

Platform & Architectureoauthai-agent-securityconsentnon-human-identityai-engineering
Read post →

AI Gateway Cache Invalidation: When a Cached Prompt Response Becomes a Data Leak

AI gateways cache prompt responses to cut cost and latency. The cache lookup uses a hash of the prompt as the key, which means two callers with different authorization scopes can hit the same cache entry. This piece walks through the failure mode, the identity-scoped cache-key patterns that avoid it, and the inspection-layer architecture that makes cache lookup safe.

Platform & Architectureai-gatewaycachingai-engineeringdata-leakai-security
Read post →

SOC 2 AI Controls Mapping: Which Trust Services Criteria a Policy Gateway Actually Evidences

SOC 2 auditors are asking about AI systems this year. The Trust Services Criteria did not change, but the scope of the audit expanded to cover AI request handling, model access controls, and AI-produced data. This piece maps CC6, CC7, and PI trust services categories to the inspection-layer controls that produce SOC 2 evidence for AI systems on a per-decision basis.

Compliance & Regulationsoc2ai-compliancetrust-services-criteriaauditai-governance
Read post →

MCP Server Authentication: Identity Binding at the Model Context Protocol Boundary

The Model Context Protocol lets an LLM client discover and call tools exposed by an MCP server. Authentication at the MCP boundary determines which identity issues the tool calls, which policy applies, and which record ends up in the audit log. This piece walks through the OAuth 2.1 authorization flow the MCP spec adopted, the pitfalls in shared-secret patterns, and the inspection-layer architecture that binds every MCP tool call to a verified identity.

Platform & Architecturemcpauthenticationoauthai-agent-securityai-engineering
Read post →