Blog

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

Bedrock API Gateway: Inspection at the AWS Bedrock Runtime Boundary

A Bedrock API gateway is the inspection point traffic to the AWS Bedrock runtime passes through before it reaches the model. The gateway attaches identity context the application supplies, runs prompt-level classification, evaluates policy, and writes a per-decision audit record. The architecture sits between callers and the InvokeModel, Converse, RetrieveAndGenerate, and agents APIs Bedrock exposes. I walk through the inspection points across each surface, how the gateway interacts with Bedrock Guardrails, and what the deployment trade-offs look like inside AWS networking.

Platform & Architectureai-securityllmpolicy-enforcementinline-enforcementarchitecturecloud-security
Read post →

The Anthropic API Gateway: Where the Inspection Point Sits Between Your Workforce and api.anthropic.com

An Anthropic API gateway is the inspection point HTTP traffic to api.anthropic.com passes through before it reaches Claude. The gateway attaches identity context, classifies prompt content, evaluates policy, and writes a per-decision audit record. The architecture sits between authenticated users or agents and the Anthropic endpoints (messages, batch, files, computer-use beta, prompt caching). I walk through the inspection points across each API surface, how identity attaches on top of static Anthropic API keys, and how policy enforces against Claude-specific patterns like prompt caching and the computer-use tool.

Platform & Architectureai-securityllmpolicy-enforcementinline-enforcementarchitecture
Read post →

The OpenAI API Gateway: Where the Inspection Point Sits Between Your Workforce and api.openai.com

An OpenAI API gateway is the inspection point your traffic to api.openai.com passes through before it reaches the model. The gateway attaches identity context, runs prompt-level classification, evaluates policy, and produces a per-decision audit record. The architecture sits between authenticated users or agents and OpenAI endpoints (chat completions, responses, embeddings, audio, batch, assistants). I walk through what the gateway intercepts, how the API surfaces map to the inspection points, and what the trade-offs are between deploying it as a SaaS-hosted proxy, a VPC-isolated proxy, or a sidecar.

Platform & Architectureai-securityllmpolicy-enforcementinline-enforcementarchitecture
Read post →

The Future of AI Governance: Five Architectural Shifts Already Underway in 2026

The future of AI governance is not a question of which framework will win. The shift is from documentation-based programs to per-decision evidence captured at the AI request boundary. The five concrete moves already underway in 2026 are convergence on the inline enforcement boundary, codification of per-decision audit records, identity-attached AI requests, machine-readable policies, and external certification bodies for AI management systems. Each shift moves the governance work from quarterly committee meetings into the AI request path itself.

Compliance & Regulationai-governanceeu-ai-actiso-42001complianceregulation
Read post →

AI Governance Audit: What an Auditor Asks For and How Architecture Produces It

An AI governance audit asks for system inventory, identity context per AI call, data classification on prompt content, policy state at decision time, and an evidence trail an external party reads. Application-controlled logs collapse under those questions because the system being audited is also the system producing the audit record. The architecture that survives an AI governance audit is a decoupled enforcement layer that produces structured, signed decision records the application never had custody over.

Compliance & Regulationai-governanceauditcomplianceeu-ai-actregulation
Read post →

Shadow AI Detection Software: What the Category Should Actually Detect

Shadow AI detection software is converging into a category, with vendors marketing variants of network monitoring, browser-extension telemetry, and CASB pivots. The detection problem decomposes into four signals: traffic identification, identity correlation, prompt-level classification, and policy state. Software that produces the first signal without the other three solves discovery and leaves the enforcement gap open. I walk through what the four signals look like, why most current detection tools generate the first one only, and what the shift from detection to enforcement requires of the architecture.

Problem-Awareshadow-aiai-securitydata-loss-preventionpolicy-enforcementai-governance
Read post →

The True Cost of a Shadow AI Breach: $670K On Top, 247 Days to Detect, 65% PII Exposure

The IBM Cost of Data Breach Report studied 600 breached organizations and found that one in five experienced breaches linked to shadow AI. Those incidents cost $670,000 more than standard breaches, exposed customer PII in 65% of cases, and took 247 days to detect. The numeric premium is the visible surface. The architectural reason behind it is identity correlation failure, classification blindness, and the absence of policy enforcement at the AI request layer.

Problem-Awareshadow-aiai-securitydata-loss-preventionai-governancecybersecurity
Read post →

AI Decision Records: The Structured Evidence Layer the Compliance Set Reads Across Regimes

AI decision records are the structured evidence layer that captures who acted, what model handled the request, what policy governed it, what data classifications applied, and what the outcome was. The 2026 regulatory set reads decision records as the primary evidence for AI system operation. EU AI Act Article 12, Fannie Mae LL-2026-04, NIST AI RMF Manage, ISO 42001 clause 8.3, and Texas TRAIGA each expect the records at a specific granularity. I walk through what a portable decision record schema looks like, what each regime reads from it, and how the same record satisfies multiple regimes at once.

Compliance & Regulationauditdecision-recordscomplianceeu-ai-actnist-ai-rmfiso-42001
Read post →

LLM Prompt Logging: What an Article 12 Compliant Record Has to Contain

LLM prompt logging records every prompt sent to an LLM, the response the model returned, the identity that initiated the call, the policy that governed the decision, and the data classifications detected. The EU AI Act Article 12 obligation, the NIST AI RMF Manage function, and the Fannie Mae LL-2026-04 disclosure mandate each expect this record at a specific granularity. I walk through what the record contains, where most application logging falls short, and how the architectural pattern that produces a compliant record differs from application-side logging.

Compliance & Regulationllm-loggingauditeu-ai-actcompliancearticle-12audit-trail
Read post →

AI Traffic Inspection: The Layer Where Prompt Content Becomes Visible to the Enterprise Stack

AI traffic inspection is the layer where prompt content becomes visible to the enterprise control stack. Network telemetry sees AI endpoint reachability. CASB sees AI SaaS access. Endpoint DLP sees clipboard events. None of those layers reads the prompt body itself. AI traffic inspection sits at the AI request boundary and reads the structured JSON request and response, which is where the data actually moves. I walk through what the inspection point reads, where the existing telemetry is blind, and how the inspection point produces evidence for the 2026 compliance set.

AI Security Solutionsai-trafficai-securityinspectionenforcementauditai-dlp
Read post →

AI Policy as Code: The Declarative Pattern That Makes Enforcement Auditable

AI policy as code expresses the rules that govern AI usage in a declarative configuration format checked into version control, evaluated at the AI request boundary, and versioned per decision in the audit record. The pattern differs from policy as documents at three points: machine-readable expression that the gate evaluates directly, version control that ties each decision to the policy in effect at the moment, and code review that captures the change history. I walk through what the policy actually contains, how the gate evaluates it, and how the audit record references it.

Platform & Architectureai-policypolicy-as-codeai-securityenforcementengineeringcompliance
Read post →

Agentic AI Enterprise Deployment: The Identity and Audit Surface That Has to Be in Place First

Agentic AI in enterprise environments adds an autonomy layer to the LLM stack that the rest of the controls were not designed for. Agents authenticate at the start of a session, but the actions they take across the session can run for hours, target many endpoints, and execute many tool calls. The identity, authorization, and audit surface that has to be in place before an agentic deployment goes to production is broader than the surface a non-agentic LLM deployment needs. I walk through the surface, where most deployments are exposed, and what the 2026 regulatory set expects from agentic AI in regulated environments.

Problem-Awareagentic-aiai-securityenterpriseidentityauditenforcement
Read post →