← All posts

Compliance & Regulation

463 posts on compliance & regulation.

Due Diligence Is Not Due Care: The AI Compliance Gap That Closes at the Request Layer

Due diligence is the procurement check a deployer runs once when selecting an AI vendor. Due care is the ongoing operational obligation that runs every time the AI system produces a decision. Most enterprises confuse the two. The vendor security questionnaire, the SOC 2 report, and the BAA cover the diligence side. The due care side is the per-decision evidence the regulator reads at audit time. This piece walks through the legal distinction, the regulatory regimes that depend on it, and the request-layer architecture that produces due care evidence on demand.

due-careai-complianceai-governanceaudit-logseu-ai-actliability
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.

llm-loggingauditeu-ai-actcompliancearticle-12audit-trail
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.

auditdecision-recordscomplianceeu-ai-actnist-ai-rmfiso-42001
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.

ai-governanceauditcomplianceeu-ai-actregulation
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.

ai-governanceeu-ai-actiso-42001complianceregulation
Read post →

EU AI Act Article 15: What the Accuracy, Resilience, and Cybersecurity Obligation Requires

Article 15 of the EU AI Act sets the accuracy, resilience, and cybersecurity floor for high-risk AI systems before the August 2, 2026 deadline. The obligation runs end to end across the deployment, from the declared accuracy metric in the technical documentation to the runtime behavior under adversarial pressure. This article walks through the regulation text, the structural gaps in most deployments, and the architectural pattern that satisfies all three properties together.

eu-ai-actai-complianceai-securityregulationinline-enforcement
Read post →

EU AI Act Prohibited Practices: What Article 5 Bans and How Enforcement Catches It

Article 5 of the EU AI Act lists the practices the regulation prohibits outright. Subliminal manipulation, exploitation of vulnerability, social scoring by public authorities, predictive policing based on profiling, untargeted facial scraping, emotion inference in workplaces and schools, biometric categorisation by protected characteristic, and most real-time biometric identification in public spaces. The prohibitions took effect February 2, 2025. The €35 million / 7% penalty tier applies. This article walks through the eight prohibitions and the architecture that catches them at the AI request boundary.

eu-ai-actai-complianceregulationai-governanceinline-enforcement
Read post →

EU AI Act Codes of Practice: What the GPAI Provisions Expect and Where Deployers Sit

The Codes of Practice in the EU AI Act are the operational mechanism that translates the GPAI obligations under Articles 53 and 55 into concrete commitments providers can sign. The Code on General-Purpose AI Models, published by the AI Office, sets out the transparency, copyright, and safety expectations the providers have agreed to. Deployers that build on top of GPAI inherit downstream obligations and a set of expectations the deployer cannot delegate to the provider.

eu-ai-actai-complianceai-governanceregulationllm
Read post →

AI Risk Register Template: What Each Row Has to Capture and Where the Evidence Comes From

An AI risk register is the operational artefact that records the risks the deployer has identified for each AI system, the controls applied, the residual risk, and the evidence that the controls are working. EU AI Act Article 9, NIST AI RMF, ISO 42001, and Fannie Mae LL-2026-04 each expect a register the deployer can produce on demand. This article walks through the columns that hold up across regimes and the runtime evidence each column depends on.

ai-governanceai-complianceeu-ai-actiso-42001audit
Read post →

EU AI Act Article 11: What Technical Documentation Must Show for Your AI System

Article 11 of the EU AI Act requires providers of high-risk AI systems to prepare and keep up-to-date technical documentation before placing the system on the market. The documentation has to demonstrate conformity with the high-risk requirements and be detailed enough that a national authority can assess it. Most engineering teams treat technical documentation as a deliverable rather than a continuously maintained artifact, and that habit fails Article 11 the first time a market surveillance authority asks for the file.

eu-ai-actai-governancecomplianceauditdocumentationregulation
Read post →

AI Vendor Due Diligence Questionnaire: What to Ask Before You Buy

AI vendor due diligence happens at the procurement gate, runs against a standard questionnaire, and produces an attestation file. The questionnaire most teams inherited from cloud SaaS vendors does not cover the questions a regulator will actually ask about AI use. The Fannie Mae LL-2026-04 framework, the EU AI Act, and the NIST AI RMF all expect ongoing due care, not one-time due diligence. This piece walks through the question categories an AI-aware procurement gate has to cover, the answers that have to live in the file, and the runtime evidence that closes the gap between due diligence and due care.

ai-governancevendor-riskcomplianceprocurementdue-diligenceaudit
Read post →

Enterprise AI Governance: What the Operational Layer Actually Has to Produce

Enterprise AI governance gets framed as a policy program. The policies are necessary, but they sit on top of an operational layer that produces evidence, enforces controls, and tracks decisions in real time. This article walks through the four artifacts a real enterprise AI governance program needs at the operational layer: the AI system inventory, the per-decision audit record, the policy enforcement record, and the incident reconstruction artifact. Each is mapped to specific regulatory regimes and to the questions a board will ask.

ai-governanceenterprisecomplianceauditregulationai-security
Read post →