← All posts

Compliance & Regulation

463 posts on compliance & regulation.

Utah AI Disclosure Evidence: SB 226 Complaint File

Utah SB 149 created the Artificial Intelligence Policy Act in 2024, and SB 226 moved the consumer-protection rules into Chapter 75 in 2025. This guide builds an audit-evidence package around the current disclosure triggers, high-risk regulated-service rule, safe harbor, consumer-protection liability and Division enforcement. It separates statutory proof from useful HTTP operating evidence and keeps notice delivery with the application.

complianceregulationai-complianceai-governanceauditforensic-audit
Read post →

Korea AI Basic Act AI Controls Mapping: Operator Duties Against One HTTPS Request

South Korea''s AI Basic Act places its obligations on the operator rather than the model, which means most of them resolve to a technical control in the request path. This maps the high-impact duties, the generative AI transparency duties, and the inspection-response duty onto the enforcement point that satisfies each one, names the evidence produced, and marks the two duties that sit outside the AI request boundary and require organisational work instead.

complianceai-governancepolicy-enforcementregulationai-security
Read post →

CCPA CPRA AI Controls Mapping: California ADMT Obligations to Enforcement Points

California finalized its ADMT, risk assessment and cybersecurity audit regulations on 23 September 2025, effective 1 January 2026, with ADMT-specific requirements beginning January 1, 2027. This maps the CCPA and CPRA duties that apply when personal information reaches a model, from pre-use notice through opt-out, access, and appeal, to the control and evidence each requires.

complianceai-governanceregulationpolicy-enforcementai-security
Read post →

SOX AI Controls Mapping for the Authenticated LLM Path

This SOX AI controls mapping assigns each request-layer requirement a control point, accountable owner, repeatable test, retained artifact, and stated boundary. It connects identity, access enforcement, information flow, audit records, integrity, retention, and incident support to authenticated HTTP model traffic without assigning programme-wide obligations to a single gateway.

ai-complianceai-governancesoxfinancial-reportingauditinternal-controls
Read post →

SOX AI Audit Evidence for Model Requests and Decisions

SOX AI audit evidence starts with a complete population of authenticated model requests, then binds reviewer-selected samples to identity, destination, policy, and decision. It also covers response handling, integrity, and retention. This guide separates evidence an HTTP policy gateway can produce from programme and legal records, plus endpoint and operational records that stay outside that boundary.

ai-complianceai-governancesoxfinancial-reportingauditinternal-controls
Read post →

EU Data Act AI Compliance Checklist for Cloud and Model Switching

An EU Data Act AI compliance checklist covers the parts of Regulation (EU) 2023/2854 that reach an AI deployment: the switching obligations in Chapter VI, the international governmental access safeguards in Article 32, the contractual transparency duty in Article 28, and the connected-product data rules in Chapter II. Each check has an owner, a pass condition, evidence fields, and a boundary line.

ai-complianceai-governanceeu-data-actregulationpolicy-enforcementarchitecture
Read post →

NIS2 AI Controls Mapping for the Authenticated LLM Request Path

This NIS2 AI controls mapping takes the ten measures in Article 21(2) of Directive (EU) 2022/2555 and assigns each one a control point, an owner, a repeatable test, a retained artifact, and a stated boundary on the authenticated path from a user or agent to an LLM. It marks where an HTTP enforcement point contributes directly and where identity, endpoint, continuity and reporting teams stay accountable.

ai-complianceai-governancenis2architecturepolicy-enforcementregulation
Read post →

NIS2 AI Audit Evidence That Survives a 72 Hour Notification

NIS2 AI audit evidence has two customers: a competent authority testing Article 21 measures, and a CSIRT reading an incident notification written against the clocks in Article 23(4). This guide builds one evidence package that serves both, covering population definition, sample binding, integrity, retention, and the boundary where an AI gateway stops contributing.

ai-complianceauditnis2regulationai-governancezero-trust
Read post →

NIS2 AI Compliance Checklist for Authenticated LLM Traffic

A NIS2 AI compliance checklist has to grade the ten measures in Article 21(2) against the AI request path, not against a generic security policy. This guide gives each check an owner, a pass condition, an evidence field, and a boundary line, then keeps the 24 hour, 72 hour, and one month reporting clocks from Article 23 attached to the systems that can actually meet them.

ai-complianceai-governancenis2regulationpolicy-enforcementaudit
Read post →

CCPA CPRA AI Compliance Checklist: Ten ADMT Controls Before January 2027

A working checklist for businesses running AI over California consumer data before ADMT-specific requirements begin January 1, 2027. Each item names the duty, the concrete action, and the evidence it produces, so the list functions as an audit-readiness pass rather than a statement of intent. Ordered the way a CPPA review moves: scope and identity first, then notice and opt-out, then access, appeal and security.

complianceai-governanceregulationauditai-security
Read post →

CCPA CPRA AI Audit Evidence: What the CPPA Expects Once the ADMT Rules Bite

California finalized its automated decisionmaking technology rules on 23 September 2025. The regulations took effect on 1 January 2026, ADMT obligations attach from 1 April 2027, and the first risk assessments go to the California Privacy Protection Agency by 1 April 2028. This walks the specific evidence a CCPA review asks for when a prompt carrying personal information reaches a model, from pre-use notice through opt-out and appeal, and names which system each artifact has to come from.

complianceai-governanceregulationauditai-security
Read post →

California AI Law in 2026: Which Statutes Bind an Enterprise Deployer, and When

A compliance owner tracking California AI law in 2026 has five statutes to sort: SB 1001 bot disclosure, AB 2013 training-data transparency, SB 942 (delayed to August 2, 2026 by AB 853), the CPPA automated-decisionmaking rules under the CCPA, and SB 53 frontier-model safety. This piece separates the obligations that bind you as a deployer from the ones that bind model developers, with effective dates and the primary sources for each.

compliancecalifornia-ai-lawregulationautomated-decision-makingaudit-trail
Read post →