← All posts

AI Security Solutions

110 posts on ai security solutions.

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-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-control-planeai-gatewayinline-enforcementai-policy-enforcementaudit-logseu-ai-act
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-policy-enforcementai-gatewayinline-enforcementeu-ai-actaudit-logsai-security
Read post →

Zero Trust Applied to AI Systems: The Per-Request Identity, Policy, and Audit Boundary

Zero-trust architecture replaces the perimeter assumption with per-request verification of identity, device, and policy. Applied to AI systems, the same principle moves the verification to the AI request boundary: who is making the call, what classification the request carries, what policy version evaluates the call, and what audit record the layer commits. This piece walks through the four zero-trust principles and how each one maps to a concrete decision the AI request path has to commit on every call.

zero-trustai-securityidentity-awareaudit-logsinline-enforcementpolicy-enforcement
Read post →

AI Agents vs RPA: How the Security Model Changes When the Bot Reasons Before It Acts

RPA bots execute deterministic scripts under a service account. AI agents read context, plan multi-step actions, and call tools whose return values shape the next step. The security model that worked for RPA (network segmentation, credential vaulting, scheduled execution) breaks when the bot reasons before it acts. This piece walks through the four architectural differences between RPA and AI agents, the new attack surfaces the reasoning step introduces, the identity-aware enforcement the deployment owes, and the audit record format that survives a regulator review.

ai-agentsrpaagent-securityidentity-awareaudit-logsagentic-ai
Read post →

AI Gateway: The Architectural Component That Sits Between Calling Identities and LLM Endpoints

An AI gateway is the architectural component that sits between calling identities (users, agents, services) and LLM endpoints, terminates the AI provider TLS, evaluates identity-bound policy, applies a pass, redact, or block decision, commits a per-decision audit record, and forwards the request. The category covers four distinct shapes today: developer-tooling proxies, enterprise observability gateways, identity-aware enforcement gateways, and inference-side guardrails libraries. Only one of the four produces the audit record EU AI Act Article 12 reviewers accept.

ai-gatewayinline-enforcementai-policy-enforcementllm-securityaudit-logsai-control-plane
Read post →

LLM Proxy: The Architectural Pattern, the Operational Modes, and the Audit Record Each Mode Produces

An LLM proxy is a process that sits on the HTTP path between calling identities and LLM provider endpoints. The proxy can operate in three modes: pass-through observability, policy enforcement, or vendor multiplexing. The choice of mode decides what the audit record contains and whether the record satisfies regulatory expectations. A pass-through proxy logs the call. A policy enforcement proxy commits identity, classification, and policy state. A multiplexing proxy unifies the API across vendors. Regulated deployments typically need the enforcement mode.

llm-proxyai-gatewayinline-enforcementai-securityaudit-logsai-policy-enforcement
Read post →

Identity-Aware AI Gateway: Why Per-User, Per-Role Policy Has to Live at the Request Boundary

An identity-aware AI gateway attaches the enterprise IdP identity to each AI request, evaluates per-user and per-role policy at the request boundary, and commits the audit record with identity context bound at decision time. The architecture differs from generic gateways that operate on application credentials only. The EU AI Act Article 19 identity-of-natural-persons requirement, the NIST agent identity framework, and the post-authentication gap each push the gateway to attach identity at the request rather than the session.

ai-gatewayidentityinline-enforcementai-policy-enforcementaudit-logscompliance
Read post →

Fail-Closed AI Gateway: Why the Default Has to Be Deny in Regulated Environments

A fail-closed AI gateway defaults to block when the policy decision is unreachable, when the classification result is uncertain, or when the gateway itself loses upstream connectivity. The opposite (fail-open) defaults to pass, which trades the regulatory record for availability. For high-risk AI under EU AI Act Article 12, DORA Article 19, and Fannie Mae LL-2026-04, the regulatory posture only holds under a fail-closed default. The architectural cost is operational investment in availability; the regulatory cost of fail-open is the loss of the contemporaneous record at exactly the moment a regulator would ask for it.

ai-gatewayfail-closedai-policy-enforcementinline-enforcementcomplianceaudit
Read post →

LLM DLP: The Inspection Point Where Prompt Content Becomes Sensitive Data

LLM DLP is the inspection layer that catches PII, PHI, source code, and customer data inside the prompt body before it reaches an LLM endpoint. Network DLP, endpoint DLP, and email DLP each terminate inspection before the prompt is in scope. This piece walks through where each traditional layer stops, why the LLM request path slips through, the regulatory framing under EU AI Act Article 12 and HIPAA, and the architectural placement that produces a defensible per-request record.

llm-dlpai-dlpdata-loss-preventionai-securityinline-enforcement
Read post →

AI Data Classification: The Categories the Audit Record Has to Carry at the LLM Request Boundary

AI data classification is the layer that labels prompt content before policy evaluates and before the audit record commits. Deterministic categories for PII, PHI, source code, customer data, and free-form sensitive labels supply the field the EU AI Act Article 19 record expects on every decision. This piece walks through the categories, the placement where the classifier runs, the regulatory framing, and how the labels feed identity-bound policy at the request boundary.

ai-data-classificationllm-dlpai-securitydata-governanceeu-ai-act
Read post →

Prompt-Level DLP: Inspection at the Field Where the User Says What They Mean

Prompt-level DLP runs inspection at the prompt body sent to an LLM endpoint, not at file boundaries or network egress. The prompt is the data, and the prompt sits inside an encrypted POST body to a SaaS destination. This piece walks through where prompt-level DLP sits, the classifier categories it has to recognize, how the redaction decision feeds the model, and the regulatory framing under EU AI Act Article 12 and HIPAA.

prompt-level-dlpllm-dlpai-dlpai-securityinline-enforcement
Read post →