Blog

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

Connecticut SB 2 AI Audit Evidence: What the Attorney General Asks For Now That SB 5 Passed Instead

Senate Bill 2 passed the Connecticut Senate on 14 May 2025 and died in the House, the second session running. The law that actually arrived is Substitute Senate Bill 5, signed as Public Act 26-15 on 2 June 2026, alongside amendments to the Connecticut Data Privacy Act that took effect 1 July 2026 with profiling impact assessments from 1 August 2026. This walks the evidence artifacts a Connecticut review requests and names which system produces each one.

Compliance & Regulationcomplianceai-governanceregulationauditai-security
Read post →

COBIT AI Compliance Checklist: Ten Items That Move an AI Process Past Capability Level 1

A working checklist for teams whose AI programme is being graded against COBIT 2019, the ISACA framework of 40 governance and management objectives that a 2025 white paper extended across the AI lifecycle. Each item names the objective, the concrete action, and the evidence artifact it produces, because COBIT grades process capability on documented work products. Ordered the way an internal audit walkthrough moves: identity and classification first, then risk, then change control, then assurance.

Compliance & Regulationcomplianceai-governanceauditregulationai-security
Read post →

Connecticut SB 2 AI Controls Mapping: Public Act 26-15 and the Amended CTDPA at the Request Boundary

Connecticut SB 2 died in the House twice. The obligations arrived through Substitute SB 5, signed as Public Act 26-15 on 2 June 2026, and through Connecticut Data Privacy Act amendments effective 1 July 2026 that removed the word solely from the automated decision opt-out. This maps each live Connecticut AI obligation onto the technical control that enforces it at the request boundary, the enforcement point where it fires, and the evidence artifact it produces for the Attorney General.

Compliance & Regulationcomplianceai-governanceregulationpolicy-enforcementai-security
Read post →

Connecticut SB 2 AI Compliance Checklist: Ten Items Before the October 2026 Deadline

A working checklist for organizations running AI over Connecticut consumer or employee data. Senate Bill 2 died in the House twice, so the live obligations sit in Public Act 26-15, signed 2 June 2026 with provisions from 1 October 2026, and in Connecticut Data Privacy Act amendments effective 1 July 2026 whose profiling impact assessment duty attached on 1 August 2026. Each item names the obligation, the concrete action, and the evidence it produces.

Compliance & Regulationcomplianceai-governanceregulationauditai-security
Read post →

CSA AICM AI Controls Mapping: 18 Domains and Four Owners Against One HTTPS Request

The CSA AI Controls Matrix, released 10 July 2025, holds 243 control objectives across 18 security domains, each tagged with an owner drawn from the cloud provider, model provider, orchestrated service provider, and application provider. This maps the domains that bite when a prompt leaves your network onto the technical control that enforces each one at the AI request boundary, the enforcement point where it fires, and the evidence artifact a STAR for AI assessment reads.

Compliance & Regulationcomplianceai-governancepolicy-enforcementcloud-securityai-security
Read post →

CSA AICM AI Audit Evidence: What a STAR for AI Assessment Asks You to Produce

The Cloud Security Alliance released the AI Controls Matrix on 10 July 2025 with 243 control objectives across 18 security domains, analyzed by control type, ownership, architectural layer, AI lifecycle stage, and threat category. STAR for AI assessments run against it. This walks the evidence artifacts an AICM assessment requests when a prompt carrying regulated data leaves your network, names the domain each artifact answers, and identifies which party in the shared-responsibility split has to produce it.

Compliance & Regulationcomplianceai-governanceauditcloud-securityai-security
Read post →

CSA CCM AI Audit Evidence: Running 197 Cloud Controls Against AI Traffic

The Cloud Controls Matrix holds 197 control objectives across 17 domains and maps to roughly 40 standards, which is why so many enterprises already run their cloud assurance against it. AI traffic lands inside that scope without a single new control, because a prompt is an outbound API call carrying regulated data. This walks the CCM domains an AI deployment touches, the evidence each one asks for, and where existing CCM answers stop being true.

Compliance & Regulationcomplianceai-governanceauditcloud-securityai-security
Read post →

CSA AICM AI Compliance Checklist: Ten Items Before a STAR for AI Self-Assessment

A working checklist for organizations preparing against the Cloud Security Alliance AI Controls Matrix, released 10 July 2025 with 243 control objectives across 18 security domains and an ownership dimension splitting each one between cloud, model, orchestration, and application providers. Each item names the domain, the concrete action, and the evidence it produces, so the list works as preparation for a STAR for AI Level 1 self-assessment rather than a reading exercise.

Compliance & Regulationcomplianceai-governanceauditcloud-securityai-security
Read post →

CSA CCM AI Controls Mapping: 17 Cloud Domains Against One Outbound Model Call

The Cloud Controls Matrix governs cloud consumption through 197 control objectives across 17 domains, and a prompt sent to a hosted model is cloud consumption. This maps the CCM domains that bite when AI traffic leaves your network onto the technical control that enforces each one, the point in the request path where it fires, and the evidence artifact a CSA STAR assessor reads. It also names the four domains whose existing answers stop being true the moment a model endpoint enters scope.

Compliance & Regulationcomplianceai-governancepolicy-enforcementcloud-securityai-security
Read post →

CSA CCM AI Compliance Checklist: Ten Items Before Your CAIQ Covers AI Traffic

A working checklist for teams whose Cloud Controls Matrix answers predate their first model endpoint. CCM v4 holds 197 control objectives across 17 domains and maps to roughly 40 standards, and the Consensus Assessments Initiative Questionnaire turns those into more than 250 answerable questions. Each item below names the CCM domain, the action to take at the AI request boundary, and the artifact it produces, so the list works as preparation for a STAR self-assessment rather than a reading exercise.

Compliance & Regulationcomplianceai-governanceauditcloud-securityai-security
Read post →

EU Cyber Resilience Act AI Compliance Checklist: Ten Items Before 11 September 2026

Article 14 reporting duties under Regulation (EU) 2024/2847 started on 11 September 2026, more than a year before the essential requirements apply on 11 December 2027, and they cover products already on the market. This checklist walks ten actions for a product with digital elements that calls a hosted model: the Annex I point each one answers, the work involved at the AI request boundary, and the artifact it produces for a 24-hour early warning, a notified body, or a market surveillance authority.

Compliance & Regulationcomplianceregulationai-governanceauditai-security
Read post →

EU Cyber Resilience Act AI Audit Evidence: What the 24-Hour Clock Asks You to Produce

Reporting duties under the EU Cyber Resilience Act start on 11 September 2026, ahead of full application on 11 December 2027. From that date a manufacturer has 24 hours to send an early warning to ENISA and its CSIRT coordinator once it has reasonable certainty of an actively exploited vulnerability or a severe incident. This walks the Annex I requirements that an embedded LLM call touches, and the specific artifacts an assessor, a notified body, or a 24-hour report asks you to produce.

Compliance & Regulationcomplianceregulationai-governanceauditai-security
Read post →