Blog

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

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 →

ISO 42001 Implementation Guide: How to Stand Up an AI Management System That Passes Certification

ISO/IEC 42001:2023 is the first international management-system standard for AI. The standard takes the ISO management-system structure (the same Annex SL Harmonized Structure used in ISO 9001, ISO 27001, and ISO 14001) and applies it to AI. Certification requires a documented AI management system covering scope, leadership, planning, support, operations, performance evaluation, and improvement. This piece walks through the certification path step by step, the Annex A controls that have to be operational, the audit evidence the certification body expects, the implementation timeline a typical mid-market organization runs, and where the AI-specific controls intersect the inspection-layer architecture.

Compliance & Regulationiso-42001aimsai-management-systemai-compliancecertificationaudit-logs
Read post →

ISO 42001 vs ISO 27001: How the AI Management System Layers on Top of Information Security

ISO 42001 and ISO 27001 share the same management-system structure (the Annex SL Harmonized Structure) and a substantial portion of the Annex A control catalog. Organizations with an ISO 27001 certification have a head start on ISO 42001 because the management-system processes transfer with modifications. The two standards address different risk domains: 27001 covers information security risks to confidentiality, integrity, and availability of information assets, while 42001 covers AI-specific risks to fairness, reliability under adversarial pressure, transparency, accountability, and the responsible use of AI systems. This piece walks through the structural overlap, the additive AI-specific controls 42001 introduces, the integration pattern for combined audits, and the inspection-layer architecture that produces evidence under both standards.

Compliance & Regulationiso-42001iso-27001aimsismsai-compliancecertification
Read post →

AI Firewall: What It Actually Inspects, Where It Sits, and the Audit Record It Produces

The phrase "AI firewall" gets applied to four very different products. The category collapses when you ask what each one inspects, where in the request path the inspection happens, and whether the record series survives EU AI Act Article 12 review. This piece walks through the four product shapes that get marketed as AI firewalls, the architectural property each one has and lacks, the inspection target the term should refer to in a regulated deployment, and the audit record the inspection layer commits at decision time.

AI Security Solutionsai-firewallinline-enforcementai-gatewayllm-securityaudit-logsai-policy-enforcement
Read post →

LLM Firewall: How the Inspection Layer Differs From a Network Firewall and a Model Guardrails Library

An LLM firewall is the inspection layer that sits inline between the calling identity and the LLM endpoint, evaluating identity-bound policy at the HTTP request boundary and committing a per-decision audit record. The layer differs from a network firewall (which inspects TCP and TLS metadata) and from a model guardrails library (which runs inside the inference path). This piece walks through the inspection target the LLM firewall has, the request-time decisions the layer commits, the deployment topology that fits a production stack, and the audit record the layer produces.

AI Security Solutionsllm-firewallinline-enforcementai-gatewayllm-securityaudit-logsai-policy-enforcement
Read post →

Open Source LLM Guardrails: The Libraries Available, Where They Sit, and What They Cannot Replace

Open source LLM guardrails libraries cover prompt-side and response-side filtering inside the application or inference path. Llama Guard, NeMo Guardrails, Guardrails AI, LMQL, and Rebuff each occupy a different position in the stack and produce different control surfaces. This piece walks through the libraries available, the architectural position each one takes, the controls they produce, and the regulatory profile that requires an external inspection layer on top of any of them.

AI Security Solutionsllm-guardrailsopen-sourcellm-securityai-policy-enforcementinline-enforcementmodel-safety
Read post →

The Accountability Gap in Agentic AI Pipelines: Who Owns the Decision When the Agent Acts

Agentic AI pipelines compose multiple model calls, tool invocations, and external retrievals into a single autonomous workflow. The compositional structure produces an accountability gap: the record series the application keeps shows the workflow outcome, the record series the model provider keeps shows the inference call, and neither shows who authorized the agent to act with whose authority at the moment of action. This piece walks through where the gap appears in production pipelines, the structural reason application logs cannot close it, and the inspection-layer record series that produces a defensible answer.

Problem-Awareagentic-aiai-agent-accountabilityaudit-logsinline-enforcementnist-ai-rmfai-security
Read post →

AI Security for Internal Copilots: The Identity, Data, and Audit Controls a Production Deployment Has To Run

Internal copilots reach across the organization with the user identity that opens the copilot session and the application identity that calls the model. The boundary between the two identities is where the security and audit obligations sit. This piece walks through the request-time data the copilot reads, the identity-aware policy decisions the deployment has to commit, the audit record format that survives EU AI Act and HIPAA review, and the architectural pattern that closes the post-authentication gap most internal copilots leave open.

Problem-Awareinternal-copilotai-securityidentity-awareaudit-logsinline-enforcementpost-authentication-gap
Read post →

AI Security for Customer Support Bots: The Inspection Layer Between the Bot and the Customer Data

Customer support bots reach customer records, payment data, account history, and PII at request time through tool calls and retrieval. The bot reads customer data into the LLM context window, the LLM reasons over it, and the bot acts on the result. The security boundary sits at the HTTP path between the bot and the upstream LLM and tool APIs. This piece walks through the data flows the bot exercises in production, the identity and authorization decisions the inspection layer commits, the audit record the customer auditor and the regulator consume, and the prompt-injection surface that retrieved customer content opens.

Problem-Awarecustomer-support-botai-securityidentity-awareaudit-logsindirect-prompt-injectionpii
Read post →

AI Security for RAG Systems: The Inspection Layer Between the Retrieval Output and the Model Call

Retrieval-augmented generation systems read documents from a vector store or a search backend into the model context window before the model reasons. The retrieval step is the point where the system pulls content of varying provenance, authorization, and trustworthiness into the prompt. The security boundary sits at the HTTP path between the retrieval output and the model call. This piece walks through the threat model RAG opens, the identity and authorization decisions the inspection layer commits, the audit record for retrieval-derived content, and the indirect prompt injection surface the retrieved documents expose.

Problem-Awareragai-securityindirect-prompt-injectionidentity-awareaudit-logsretrieval
Read post →

AI Security for Coding Agents: The Source-Code, Secret, and Action Boundaries the Agent Crosses

Coding agents read source code, write code changes, run shell commands, call external APIs, and commit results back to the repository. The agent crosses multiple action boundaries inside a single workflow with the developer identity at the top and machine credentials at the bottom. This piece walks through the source-code data the agent reads at request time, the secret-handling surface the agent exposes, the action boundaries the inspection layer commits decisions at, and the audit record format the security team and the regulator consume.

Platform & Architecturecoding-agentai-securityidentity-awareaudit-logsinline-enforcementdeveloper-tools
Read post →

Shadow AI Discovery Quiz: A 12-Question Tool to Score Your Organization Against the Six-Week Discovery Framework

Most organizations that decide to address shadow AI start by buying a tool. The tool fires alerts on day one and produces a report nobody can act on. A working discovery program is a sequenced six-week path that begins with what the organization already has and adds inspection only after the surface is mapped. This 12-question quiz scores your organization against each step of the framework and tells you where the next two weeks of work belongs.

Problem-Awareshadow-aidiscoveryai-inventoryself-assessmentfree-toolai-governance
Read post →