← All posts

Compliance & Regulation

463 posts on compliance & regulation.

EU AI Act Article 19: What the Six-Month Log Retention Rule Requires

Article 19 of the EU AI Act tells deployers of high-risk AI systems what to put in the automatically generated logs Article 12 requires, and how long to keep them. The retention floor is six months. The content has to support traceability for risk monitoring and post-market surveillance. The August 2, 2026 deadline applies. Most application logging stacks miss the identity, classification, and policy-state fields the Article 19 reading actually calls for.

eu-ai-actarticle-19complianceaudithigh-risk-airetention
Read post →

AI System Cards: What Goes Inside, Which Regulators Expect Them, and Where the Operational Evidence Comes From

An AI system card documents the AI system as deployed: the intended use, the operating environment, the human oversight mechanisms, the policies in effect, the audit-trail format, and the decommissioning plan. System cards extend the model-card concept from a model artifact (Mitchell et al., 2018) to a deployed-system artifact. Regulators expect system cards under EU AI Act Article 11 technical documentation, ISO 42001 Clause 7.5 documented information, NIST AI RMF MAP function, and Fannie Mae LL-2026-04 Pillar 1 inventory. This walkthrough covers the eight fields a system card needs, where the operational evidence comes from, and how the per-decision audit log feeds the card.

ai-system-cardeu-ai-actdocumentationai-governancecomplianceaudit-evidence
Read post →

The AI Governance Alliance: What the WEF Working Groups Have Shipped and Where Their Recommendations Land in Your Architecture

The AI Governance Alliance is the World Economic Forum initiative coordinated through three working groups: Safe Systems and Technologies, Responsible Applications and Transformation, and Resilient Governance and Regulation. Its outputs land in three places: model-level safety research, enterprise deployment patterns, and regulator-facing guidance for cross-border AI rules. The Alliance has shipped published frameworks since 2024 that map directly to NIST AI RMF MANAGE function, EU AI Act Article 13 transparency requirements, and the OECD AI principles. This walkthrough covers which Alliance outputs are operational, which are still aspirational, and where the recommendations need an enforcement layer.

ai-governancewefai-governance-alliancecomplianceframeworksglobal-governance
Read post →

AI Transparency Disclosure: What EU AI Act Article 13 Requires from Providers and What Deployers Owe Their Users

AI transparency disclosure obligations come from three layers. EU AI Act Article 13 requires high-risk AI system providers to deliver instructions of use, system characteristics, capabilities, limitations, and the means for human oversight to deployers. Article 26 extends the obligation: deployers have to inform natural persons that they are subject to an AI system. The horizontal transparency obligations under Articles 50 through 53 cover labelling synthetic content, disclosing AI interactions, and watermarking generated media. Each layer has a different recipient, a different artifact, and a different timing. This walkthrough covers the three layers and the audit-record fields that prove the disclosures actually fired.

ai-transparencyeu-ai-actarticle-13disclosurecomplianceai-governance
Read post →

DORA Third-Party AI Risk: How EU Banks Have to Treat LLM Vendors Under the ICT Critical-Provider Regime

Under the Digital Operational Resilience Act, EU financial entities have to maintain a register of all ICT third-party service providers including LLM vendors, classify which ones support critical or important functions, run pre-contract diligence on those, and meet specific contract content rules under Article 30. The European Supervisory Authorities can designate certain LLM vendors as Critical ICT Third-Party Providers under the CTPP regime, with direct supervisory powers. The Jan 17, 2025 enforcement date is in the rear-view; the question now is whether your AI usage shows up correctly in the register and whether your audit evidence survives an ESA review.

dorathird-party-riskfinancial-servicescomplianceeu-regulationai-governance
Read post →

AI audit log retention: how long EU AI Act, HIPAA, and DORA expect you to keep per-decision records

AI audit log retention is governed by four overlapping regimes that produce different minimum windows on the same record. The EU AI Act Article 12 expects logs across the deployment lifecycle for high-risk systems, with Article 19 fixing a 10-year period for the records the conformity-assessment file references. HIPAA 45 CFR 164.530(j) fixes six years from creation or last effective date. DORA Article 19 fixes a minimum of five years for ICT-related incident records, with longer windows where the supervisor requests them. The retention schedule has to be set to the longest applicable window per record and the storage tiering, tamper-evidence and GDPR deletion handling have to be designed against that window.

ai-audit-logseu-ai-acthipaadoralog-retentioncompliance
Read post →

AI compliance reporting automation: turning per-decision audit records into board-ready evidence

AI compliance reporting automation turns the per-decision audit records the inspection layer writes into three artifacts the auditor, the control owner, and the board each consume. The raw log substrate covers EU AI Act Article 12 and DORA Article 19. The per-control evidence summary covers SOC 2 TSC and NIST AI RMF MEASURE. The board KPI rolls up to a single page. The three-layer stack is the automation target.

ai-complianceaudit-automationeu-ai-actnist-ai-rmfsoc-2evidence-pack
Read post →

GDPR AI DPIA: When Article 35 Requires an Assessment

A GDPR AI DPIA starts with the processing operation, not the presence of a model. This guide applies Article 35's likely-high-risk threshold, the nine WP248 rev.01 screening criteria, and EDPB Opinion 28/2024 to practical AI deployments. It also covers controller and processor roles, the minimum assessment record, Article 27 FRIA coordination, review triggers, and the limited but useful evidence available at an authenticated HTTP AI gateway.

gdprdpiaarticle-35privacyai-complianceedpb
Read post →

PCI DSS 4.0 AI Controls: Where an LLM Deployment Touches the Cardholder Data Environment

PCI DSS 4.0 does not name AI systems in its 12 requirements. It does describe the cardholder data environment and the controls that apply to systems that store, process, or transmit cardholder data. An LLM deployment that touches cardholder data joins the CDE. This piece walks through the PCI DSS 4.0 requirements that apply to LLM deployments, the cardholder-data flow patterns that pull the LLM into scope, and the audit evidence a QSA accepts for the AI-specific controls at the gateway boundary.

pci-dsscompliancecardholder-dataai-securityllm-dlpai-gateway
Read post →

SOC 2 AI Controls Mapping: Which Trust Services Criteria a Policy Gateway Actually Evidences

SOC 2 auditors are asking about AI systems this year. The Trust Services Criteria did not change, but the scope of the audit expanded to cover AI request handling, model access controls, and AI-produced data. This piece maps CC6, CC7, and PI trust services categories to the inspection-layer controls that produce SOC 2 evidence for AI systems on a per-decision basis.

soc2ai-compliancetrust-services-criteriaauditai-governance
Read post →

SOC 2 AI Controls: Which Trust Services Criteria a Policy Gateway Actually Evidences

SOC 2 does not have an AI-specific control category, but every AI deployment inside a Type II audit surfaces control gaps under the same five Trust Services Criteria. The auditor questions center on who accessed the model, what data flowed through it, whether policy enforcement is deterministic, and whether the audit trail is tamper-evident. Application-controlled logs fail the CC7 evidence bar. The fix is architectural.

soc-2complianceai-governanceauditai-securitytrust-services
Read post →