← All posts

Compliance & Regulation

463 posts on compliance & regulation.

Brazil LGPD AI Incident Reporting: Three Business Days and What You Must Name

ANPD Resolution CD/ANPD nº 15 of April 24, 2024 gives Brazilian controllers three business days from confirming an incident to notify the ANPD and affected data subjects. When the incident involves an LLM or an AI agent, the notification still asks which data categories were compromised and what the likely impacts are, and application logs rarely answer either.

ai-complianceai-governancecomplianceregulationauditforensic-audit
Read post →

Brazil LGPD LLM Requirements: The Obligations That Attach to Prompt Traffic

Sending personal data to a large language model is a processing operation under the LGPD, with a purpose, a legal basis, a recipient and a retention position. This sets out which LGPD obligations attach at the moment a prompt leaves the organisation, covering Article 6 principles, Article 20 automated decisions, Article 46 security measures, and the operator relationship.

ai-complianceai-governancecomplianceregulationllmpolicy-enforcement
Read post →

Azure AI Foundry Compliance: RBAC Scope, Key Auth, and the Evidence Gap

Microsoft states that key-based authentication to a Foundry resource grants full access with no role restrictions. That single sentence decides how much an Azure AI Foundry compliance file can rest on RBAC. This covers the built-in roles, the resource, project and agent scopes, the recent role rename, and the request-level evidence RBAC never produces.

ai-complianceai-governanceidentity-and-authorizationcomplianceauditcloud-security
Read post →

AutoGen Compliance: Model Clients, Untested Endpoints, and Event Logging

AutoGen supports OpenAI, Azure OpenAI, Azure AI Foundry, Anthropic, Ollama, Gemini and Llama API clients, several marked experimental, and the documentation notes that OpenAI-compatible endpoints are usable but untested. An AutoGen compliance file records which client each agent holds, which credential it carries, and what the event logger actually preserves.

ai-complianceai-governanceagentic-aicomplianceauditidentity-and-authorization
Read post →

AWS Bedrock Compliance: Building Evidence Around Model Invocation Logging

Amazon Bedrock model invocation logging is disabled by default and captures only calls made through the bedrock-runtime endpoint. An AWS Bedrock compliance file needs the enablement record, the destination configuration, the identity ARN on each invocation, the 100 KB body threshold, and the customer-side policy decision that sits above all of it.

ai-complianceai-governanceauditcompliancecloud-securitypolicy-enforcement
Read post →

Brazil LGPD AI Risk Assessment: What Article 38 Actually Obliges

LGPD Article 38 lets the national authority require a controller to prepare a data protection impact assessment, and sets a minimum content standard: the types of data collected, the methodology for collection and for securing the information, and the controller analysis of measures, safeguards and risk mitigation mechanisms. For an LLM deployment, two of those three are usually undocumented.

ai-complianceai-governancecomplianceregulationauditpolicy-enforcement
Read post →

Box AI Compliance: Turning Platform-Neutral Model Routing into Evidence

Box takes a platform-neutral approach to AI models and commits to publishing which models are used, to deleting prompt and answer data at the provider once a response returns, and to not training on customer content without explicit approval. A Box AI compliance file turns those vendor commitments into customer-side records covering permissions, model destination, and the request-level policy decision.

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

Amazon Q Compliance After the Closure to New Customers

AWS has closed Amazon Q Business to new customers and points prospective users to Amazon Quick. For organisations already running it, the compliance file now carries a service lifecycle question alongside the usual shared responsibility work: identity through IAM Identity Center, ACL propagation from connected sources, CloudTrail coverage, and the request-level policy decision AWS does not make.

ai-complianceai-governancecomplianceauditidentity-and-authorizationcloud-security
Read post →

Spain's AEPD Logged the First Breach Notification Where an AI Agent Was the Actor

On September 14, 2026 the Spanish data protection authority received a personal data breach notification in which a third party used an AI agent as the instrument of the attack. The AEPD now tells controllers to write AI-executed and AI-assisted attacks explicitly into their Article 32 risk analyses rather than relying on generic malware language.

gdprai-governancecomplianceagentic-airegulationaudit
Read post →

Australia Privacy LLM Requirements: Inputs, Outputs and Evidence

Australia privacy requirements for LLM deployments follow the existing Privacy Act and Australian Privacy Principles. Organisations need a defined purpose, lawful collection, notice, permitted use or disclosure, cross-border analysis, accurate outputs, security controls, access and correction paths, deletion handling, and evidence for each request route.

ai-complianceai-governancecomplianceregulationllmpolicy-enforcement
Read post →

Australia Privacy AI Risk Assessment: An OAIC-Aligned PIA Workflow

An Australia privacy AI risk assessment should begin before product selection and follow the OAIC privacy impact assessment process through data-flow mapping, APP analysis, mitigation, approval, and review. The assessment becomes operational when each privacy risk maps to an owner, runtime control, test, and retained artifact.

ai-complianceai-governancecomplianceregulationauditpolicy-enforcement
Read post →

Atlassian AI Compliance: Turn Rovo Settings into Reviewable Evidence

Atlassian AI compliance starts with the published Rovo data path, then moves into customer-owned evidence. Review model routing, app-level activation, connector permissions, data contribution settings, residency choices, audit logs, and the policy decision on personal or regulated data before it reaches an LLM.

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