Blog

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

Prompt Injection vs Jailbreak: Where the Two Attack Classes Diverge and What the Inspection Layer Enforces

Prompt injection and jailbreaking are distinct attack classes that public discussion often conflates. Jailbreaking targets the model provider safety training to produce content the provider intended to suppress. Prompt injection targets the application context boundary to override the application instructions or exfiltrate organization data. The defenses sit at different architectural layers. This piece walks through the distinction, where each defense layer fires, and the inspection-layer pattern that addresses both.

Problem-Awareprompt-injectionllm-securityai-securityinline-enforcementmodel-guardrailsaudit
Read post →

Prompt Injection Test Cases: The Twelve Patterns Your Red Team Has To Run

Prompt injection test cases for production AI deployments cluster into twelve patterns the red team has to exercise: instruction-override, role-reversal, encoded payloads, indirect injection through retrieved content, tool-output injection, multi-turn persuasion, authority impersonation, output-formatting hijack, translation pivot, long-context dilution, system-prompt extraction, and authorization-bypass. This piece walks through each pattern, the payload structure, the expected inspection-layer verdict, and the audit record the test should produce.

Problem-Awareprompt-injectionllm-securityai-securityinline-enforcementred-teamaudit
Read post →

Prompt Injection Examples: 12 Real Patterns From Production Incidents and the Inspection Layer Response

Prompt injection examples that surface in production AI systems follow a small number of repeatable patterns. The patterns appear across customer support agents, RAG pipelines, agentic browsers, and code-assist tools. Each pattern has a control point at the request boundary where an inspection layer can produce a deterministic signal the policy can act on. This piece walks through twelve patterns from production incident response, the injection text that triggers each, the inspection-layer response that holds up, and the audit record that supports the post-incident review.

Problem-Awareprompt-injectionllm-securityai-securityinline-enforcementaudit-logsowasp
Read post →

AI Security Vendor Evaluation Criteria: The Twelve Questions That Distinguish Real Enforcement from Marketing

AI security vendor evaluation criteria for 2026 cluster around twelve concrete questions tied to EU AI Act Article 12, Fannie Mae LL-2026-04, and NIST AI RMF Manage 4 obligations. Each question maps to an architectural property a real enforcement layer either has or does not. This piece walks through the twelve questions in the order a regulated buyer should ask them, the answer pattern that indicates the vendor sits at the request boundary, and the failure modes that distinguish marketing copy from production architecture.

Comparisons & Alternativesai-securityvendor-evaluationprocurementeu-ai-actaudit-logscompliance
Read post →

AI Policy Enforcement: Where the Decision Happens and the Record That Survives Review

AI policy enforcement has to operate at a specific layer in the request path to produce a record that survives an EU AI Act Article 12 review. Most stacks place the enforcement inside the application that makes the AI call, which fails the traceability test. This piece walks through where the enforcement has to sit, the properties the layer must carry (deterministic, identity-aware, fail-closed, sub-50ms), the record series the layer commits, and the regulatory framing that makes the placement non-optional.

AI Security Solutionsai-policy-enforcementai-gatewayinline-enforcementeu-ai-actaudit-logsai-security
Read post →

AI Governance Maturity Model: The Five Stages and Where Most Enterprises Actually Sit

AI governance maturity models tend to read as aspirational ladders that everyone climbs eventually. The version that matches what regulators ask for in 2026 has five concrete stages defined by the per-decision evidence the deployer can produce at each level. This piece walks through the five stages, where each stage sits against EU AI Act Article 12 and Fannie Mae LL-2026-04 obligations, and the architectural control that moves an organization to the next stage.

Compliance & Regulationai-governanceai-governance-maturity-modelcomplianceeu-ai-actrisk-managementaudit
Read post →

AI Governance Failure: What the Headline Incidents Have in Common and Where the Architecture Fails

AI governance failures cluster around the same architectural defects in incident after incident: identity unbound at the request layer, audit logs written by the application under audit, shadow AI traffic outside the inspection boundary, and vendor AI usage the deployer never sees. This piece walks through the recurring failure pattern, the recent incident record, and the architectural control that closes each defect before the next breach gets reported.

Compliance & Regulationai-governanceai-governance-failureincident-responsecomplianceshadow-aiaudit
Read post →

AI Governance Challenges: The Seven Failures That Show Up in the First Regulator Review

AI governance challenges show up in a specific order during the first EU AI Act, NIST AI RMF, and Fannie Mae LL-2026-04 review. The seven failure modes cluster around identity binding, per-decision audit, shadow AI exposure, vendor AI usage, policy version drift, model registry gaps, and disclosure obligations. This piece walks each failure mode through the regulatory question that surfaces it and the architectural control that closes it.

Compliance & Regulationai-governanceai-governance-challengescomplianceeu-ai-actrisk-managementaudit
Read post →

AI Governance Tools: What the Category Has To Cover and Where Most Products Stop

The AI governance tools category bundles four very different product shapes: model registries, policy authoring platforms, posture and inventory scanners, and runtime enforcement layers. Each shape covers a different obligation under the EU AI Act, NIST AI RMF, ISO 42001, and Fannie Mae LL-2026-04. This piece walks through what each shape does, where each one stops, and the runtime gap most buyers discover after the procurement decision.

Compliance & Regulationai-governanceai-governance-toolscomplianceeu-ai-actnist-ai-rmfiso-42001
Read post →

AI DLP: Why Traditional Data Loss Prevention Misses the LLM Request Path and What Replaces It

Traditional DLP sits at the network edge or endpoint and inspects files and email. AI DLP has to sit at the HTTP request layer between authenticated users or agents and the LLM endpoint, because the prompt is the data and the prompt is inside an encrypted POST body the network DLP never sees. This piece walks through where each DLP layer terminates inspection, the regulatory framing under EU AI Act Article 12 and HIPAA, and the inspection architecture that produces a defensible record.

AI Security Solutionsai-dlpllm-dlpdata-loss-preventionai-securityinline-enforcementeu-ai-act
Read post →

AI Control Plane: What Sits at the Request Boundary and What an Auditor Reviews

The phrase "AI control plane" gets applied to four different layers in the stack. Each layer has a different inspection target, a different enforcement timing, and a different audit record. This piece walks through what an AI control plane has to do at the HTTP boundary between authenticated users or agents and the LLM, where most candidate products fall short of EU AI Act Article 12 review, and the record series the inspection layer commits at decision time.

AI Security Solutionsai-control-planeai-gatewayinline-enforcementai-policy-enforcementaudit-logseu-ai-act
Read post →

AI Agent Supply Chain Attacks: How the Request Boundary Becomes the Failing Surface

AI agent supply chain attacks compromise the agent at one of three points: the model artifact, the tool the agent calls, or the runtime input the agent processes. The HTTP request boundary between the authenticated agent and the LLM endpoint sits underneath all three failure modes. This piece walks through the attack patterns reported in 2025 and 2026, the architectural defects that enable each one, and the inspection-layer control that closes the runtime side of the supply chain risk.

Problem-Awareai-agent-securitysupply-chainagentic-aiprompt-injectioninline-enforcementai-security
Read post →