← All posts

Compliance & Regulation

463 posts on compliance & regulation.

FTC AI Enforcement: What Operation AI Comply Puts on Notice

FTC AI enforcement under Operation AI Comply targeted claims about legal services, consumer reviews, and automated business opportunities. The cases show a practical rule for enterprise AI claims: preserve evidence for the promised capability, the test method, the deployed version, and the review path before marketing or procurement repeats the claim. This guide turns the FTC examples into a claim-to-evidence control.

ai-governanceai-complianceai-securityauditpolicy-enforcementregulation
Read post →

EU AI Act Digital Omnibus: The New High-Risk AI Timeline

Regulation (EU) 2026/1744, the Digital Omnibus on AI, changed when key high-risk AI provisions apply. Annex III systems now move to December 2, 2027, while product-linked Annex I systems move to August 2, 2028. The amendment does not pause the entire EU AI Act. Enterprise teams need a classification register that separates system category and operator role from the applicable article and date, with an owner and technical evidence.

ai-governanceai-securityeu-ai-actpolicy-enforcementregulationrisk-management
Read post →

America's AI Action Plan: Federal Signals for Enterprise AI Security

America's AI Action Plan is a federal policy agenda built around innovation, infrastructure, and international security. It directs agencies toward procurement changes, AI security guidance, incident-response work, and full-stack export programs. Enterprise teams should track those outputs without mistaking the plan for a private-sector compliance rule. This guide turns the federal actions into a review register with owners, triggers, and evidence.

ai-governanceai-securitycybersecuritynistpolicy-enforcementregulation
Read post →

OWASP AI Exchange: Build a Threat-to-Control Ownership Map

The OWASP AI Exchange is a broad, living body of knowledge for AI security and privacy. Security teams get value from it by scoping one deployed system, selecting relevant threats, assigning controls to the components that can enforce them, and retaining test evidence. This guide turns the Exchange into a practical threat-to-control ownership map without mistaking one gateway for complete AI security coverage.

owaspai-securitythreat-modelingai-governancepolicy-enforcementarchitecture
Read post →

Grok Acceptable Use Policy: What Enterprise Teams Must Enforce

The Grok acceptable use policy applies to consumers, developers, and businesses using the service. Its current rules prohibit harmful and illegal activity, service abuse, safeguard circumvention, unauthorized actions, and high-stakes automated decisions. Enterprise customers should translate those provider rules into identity-bound controls on routed API requests, while keeping human review, application actions, and direct consumer use under their proper owners.

acceptable-useai-policygrokai-governancepolicy-enforcementaudit
Read post →

Is Read AI HIPAA Compliant? A Product and BAA Guide

Read AI says it meets HIPAA technical safeguard requirements and makes a Business Associate Agreement available to healthcare and human services teams on request. That supports a HIPAA-regulated deployment only after the organization confirms the agreement, workspace, enabled features, meeting-data routes, retention settings, permissions, and operating evidence. This guide turns the vendor claim into a reviewable approval decision.

hipaaai-complianceai-securityhealthcareauditdata-protection
Read post →

EU AI Act for HR: Annex III Point 4 and the December 2027 Deadline

The current EU AI Act places recruitment, promotion, termination, task allocation, and worker-monitoring systems in Annex III point 4, subject to the Article 6(3) exception. Regulation (EU) 2026/1744 moved the main Chapter III high-risk duties for these systems to 2 December 2027. This guide separates the duties already in force from later high-risk controls. It also covers deployer notices, logging and retention, impact assessments, and explanation rights.

eu-ai-acthrrecruitmenthigh-risk-aicompliancearticle-12
Read post →

Risk Manager AI Risk Checklist for Acceptance Decisions

This risk manager AI risk checklist turns one AI use into a documented acceptance, treatment, or rejection decision. It fixes the context of use, tolerance, owner, treatment, measures, production evidence, and change triggers before risk enters the register. Recurring reporting remains a separate process.

ai-governanceai-compliancenist-ai-rmfauditpolicy-enforcementcompliance
Read post →

Procurement Lead AI Risk Checklist for Contract Award

This procurement lead AI risk checklist turns an AI supplier selection into a signed contract-award and service-acceptance decision. It fixes the use boundary, maps required evidence to scored artifacts and contract commitments, tests evidence delivery and change notice, assigns the operating handoff, verifies exit portability, and records conditions before purchase.

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

Databricks AI Security Framework: Turn DASF Risks Into Control Tests

The Databricks AI Security Framework gives security teams a component-based risk catalog for AI systems. A useful implementation turns each applicable DASF risk into an owned control and a test on the real request path, with evidence that shows the result. This article explains that workflow and identifies the narrow HTTP enforcement slice that DeepInspect can cover.

ai-securityai-governanceai-complianceagentic-aipolicy-enforcementarchitecture
Read post →

G7 Hiroshima AI Process: Turn the Voluntary Code Into Evidence

The G7 Hiroshima AI Process produced international guiding principles and a voluntary code of conduct for organizations developing advanced AI systems. Its 11 actions cover lifecycle risk, incident handling, transparency, governance, security, provenance, standards, and data protections. Implementation requires several evidence owners, with HTTP request records supporting only the routed-use slice.

ai-governanceai-complianceregulationauditpolicy-enforcement
Read post →

CISA AI Guidance Needs a Lifecycle Release Record

CISA AI guidance organizes secure AI system development across design, development, deployment, and operation. Teams should turn those phases into one release record containing the threat model, asset and supplier evidence, deployment approval, monitoring plan, and named control owners while keeping model, infrastructure, and HTTP request controls assigned to the systems that can enforce them.

ai-securityai-governancecybersecuritydevsecopsauditarchitecture
Read post →