← All posts

Compliance & Regulation

463 posts on compliance & regulation.

SEC AI Washing: Build Evidence Before You Make the Claim

SEC AI washing enforcement turns a broad communications problem into a specific evidence test. Investment advisers and public companies should inventory every AI statement, identify the system and data behind it, route claims through legal and technical review, preserve dated substantiation, and monitor production changes that make approved language stale.

ai-governanceai-complianceregulationauditai-securitycompliance
Read post →

NIST Cyber AI Profile: Three Focus Areas and Evidence

The preliminary NIST Cyber AI Profile applies Cybersecurity Framework 2.0 to three connected jobs: securing AI systems, using AI in cyber defense, and resisting AI-enabled attacks. Security leaders should turn the profile into a current-state record, a target profile, named control owners, and evidence for each claimed outcome while keeping technical overlays and AI risk governance in their proper roles.

nistai-securityai-governancecybersecurityai-complianceaudit
Read post →

AI Sovereignty: The Eight Control Planes Behind a Model Request

AI sovereignty reaches beyond the region that hosts an LLM. The European Commission framework covers eight objectives across strategy; jurisdiction; data and AI; operations; supply chain; technology; security and compliance; and sustainability. Following one authenticated model request through those layers separates controls that can be enforced at the HTTP boundary from questions that require provider, procurement, operational and infrastructure evidence.

ai-governanceai-complianceai-securitypolicy-enforcementarchitecture
Read post →

OECD AI Principles: What the 2024 Revision Requires as Evidence

The OECD AI Principles were amended in May 2024 to address general-purpose and generative AI, information integrity, foreseeable misuse, privacy and intellectual property, lifecycle safety, system override, and environmental sustainability. This guide maps those additions to the records, evaluations, incident procedures, and request-level evidence an organization needs, while clearly separating HTTP enforcement evidence from fairness, provenance, environmental, and enterprise-accountability work.

ai-governanceai-compliancepolicy-enforcementauditarchitecture
Read post →

Australia Privacy AI Incident Reporting: Evidence for the NDB Decision

Australia’s Notifiable Data Breaches scheme applies when an AI incident involves unauthorised access, disclosure, or loss of personal information and serious harm is likely. The operational challenge is preserving enough request-level evidence to assess the event, support remedial action, and explain the notification decision.

ai-complianceai-governancecomplianceregulationauditforensic-audit
Read post →

ISO/IEC 23894: What the AI Risk Management Standard Asks You to Produce

ISO/IEC 23894:2023 adapts the ISO 31000 risk management process to AI systems. It is guidance rather than a certifiable standard, which changes how it gets used: teams reach for it to structure risk identification and to feed the risk clauses of ISO/IEC 42001, which is certifiable. This walks the standard structure, the AI-specific risk sources it names, how it relates to 42001 and the NIST AI RMF, and which of its monitoring and record requirements a runtime control produces evidence for.

iso-42001ai-governancecompliancerisk-managementauditregulation
Read post →

Internal Auditor AI Risk Checklist: Authorize the Engagement and Sample

This internal auditor AI risk checklist turns a planned assurance engagement into an authorized sampling memo. It fixes the independence statement, audit population, sample logic, control tests, evidence custody, and escalation criteria before fieldwork begins, while keeping recurring AI risk reporting in a separate process.

auditforensic-auditai-governancenist-ai-rmfpolicy-enforcement
Read post →

General Counsel AI Risk Checklist: The Legal Approval Gate

This General Counsel AI risk checklist defines a legal approval gate for a specific AI use and material change. It covers product and public claims, contractual risk allocation, privilege, regulatory posture, litigation holds, exceptions, and a signed legal disposition while keeping recurring executive reporting in a separate process.

ai-governanceai-compliancecomplianceauditnist-ai-rmfpolicy-enforcement
Read post →

CTO AI Risk Checklist for Release and Material Change Gates

This CTO AI risk checklist defines eight checks for a pre-release or material-change engineering gate. It ends in a signed go/no-go readiness record that binds the release to model routes, connectors, data classes, tested failure behavior, rollback evidence and unresolved technical exceptions. Executive reporting stays outside this gate.

ai-governanceai-securityai-complianceauditnist-ai-rmfarchitecture
Read post →

CIO AI Risk Checklist for Accepting, Renewing and Retiring Services

This CIO AI risk checklist turns AI portfolio governance into eight authorization decisions for service scope, ownership, route and data review, acceptance testing, signed approval, renewal, time-limited exceptions and retirement. The final artifact is a signed CIO service-acceptance record tied to evidence, while dashboard design and recurring executive reporting stay in their separate operating process.

ai-governanceai-securityai-complianceauditnist-ai-rmfarchitecture
Read post →

ISO/IEC 23894 AI Audit Evidence at the Request Boundary

An ISO/IEC 23894-aligned evidence packet should let a reviewer trace one AI risk from assessment to treatment, test, approval and later monitoring. This example supplies an artifact index, owners, dates and a retrieval walkthrough for a support summarizer. It distinguishes request-level decision records from model evaluation and business approvals, and it avoids treating illustrative artifacts as ISO-mandated forms.

ai-complianceai-governanceauditpolicy-enforcementidentity-and-authorization
Read post →

ISO/IEC 23894 AI Controls Mapping

An AI controls mapping is a chain of decisions, not a list of products. This example starts with one support summarizer and maps four different risk scenarios to a control, accountable owner, test, evidence and residual-risk decision. It distinguishes an organization's selected controls from the customizable ISO/IEC 23894 risk-management guidance and marks where a request gateway has no coverage.

ai-complianceai-governanceauditpolicy-enforcementidentity-and-authorization
Read post →