The regulatory landscape for AI is shifting rapidly. DeCompliance delivers curated intelligence on AI GRC — what's changing, what matters, and what you need to act on.
AI GRC is the discipline of managing artificial intelligence through structured governance, rigorous risk management, and regulatory compliance — ensuring AI systems are trustworthy, ethical, and lawful.
Policies, roles, accountability structures, and oversight mechanisms that guide how AI is designed, deployed, and monitored within an organisation. Covers board-level AI strategy, model inventories, and internal audit trails.
Identification, assessment, and mitigation of harms that AI may cause — including bias, hallucination, data poisoning, model drift, and third-party supply chain risks. Aligns with ISO 31000 and emerging AI-specific risk taxonomies.
Meeting the letter and spirit of regulations such as the EU AI Act, UK's pro-innovation AI approach, NIST AI RMF, and sector-specific mandates from financial regulators like the FCA and PRA.
Regulatory action is no longer theoretical. Organisations that ignore AI governance today face real consequences tomorrow.
The EU AI Act began phased enforcement in 2024, with prohibited AI systems already banned. Fines reach €35M or 7% of global turnover — whichever is higher.
UK FCA and PRA have issued supervisory guidance on AI model risk. Banks and insurers face SR 11-7 equivalent expectations for algorithmic decision-making systems.
Training data, GDPR compliance, and automated decision-making rights under Article 22 create a legal web that AI teams must navigate with legal and compliance partners.
The US, EU, UK, China, and Singapore each have diverging AI regulatory philosophies. Multinationals need a GRC strategy that works across multiple legal systems simultaneously.
Directors are personally accountable for AI-related material risks. Governance frameworks must flow from the board down to engineering and procurement teams.
Vendor AI models embedded in products inherit regulatory obligations. Organisations must assess, monitor, and document AI in their supply chains as rigorously as internally built systems.
A fast-moving map of the laws, frameworks, and enforcement actions shaping AI compliance obligations worldwide.
The world's first comprehensive AI law. Uses a risk-tiered approach — prohibited, high-risk, limited-risk, and minimal-risk AI. High-risk systems face conformity assessments, technical documentation, and post-market monitoring. General-purpose AI models above 10^25 FLOPs face additional systemic risk obligations.
Read the EU AI Act →The UK government has opted for a principles-based, sector-led model rather than prescriptive AI legislation. The ICO, FCA, CMA, and Ofcom each apply existing powers to AI in their domains. The AI Safety Institute runs frontier model evaluations and publishes safety reports.
UK AI Policy Paper →The Biden-era Executive Order on Safe, Secure, and Trustworthy AI directed agencies to develop sector-specific guidance. The NIST AI Risk Management Framework (AI RMF 1.0) provides a voluntary but widely adopted GRC structure for US organisations, covering Govern, Map, Measure, and Manage functions.
NIST AI RMF →The international standard for establishing, implementing, and maintaining an AI Management System (AIMS). Certifiable and modelled on ISO 27001. Provides the structural backbone for many organisations' AI GRC programmes, particularly in Europe and Asia-Pacific.
ISO/IEC 42001 Overview →MAS and IMDA have co-developed one of the world's most detailed voluntary AI governance frameworks for financial services and general use. Singapore's approach is widely respected as a model for balanced, innovation-friendly AI oversight.
Singapore AI Framework →Analysis, commentary, and intelligence on the key developments shaping AI governance.
General-purpose AI providers face technical documentation, copyright transparency, and systemic risk evaluation duties. Here's a practical breakdown of what compliance looks like in practice.
A practical template for AI risk registers aligned with NIST AI RMF, covering inherent risk, controls, residual risk, and owner accountability — built to satisfy both internal audit and external regulators.
As the EU AI Act references ISO standards, organisations are considering whether ISO 42001 certification provides meaningful market differentiation or regulatory credit — and whether the audit costs are justified.
The FCA has signalled heightened focus on AI model explainability, consumer duty obligations for algorithmic decisions, and third-party AI vendor due diligence in regulated financial services.
Regulators increasingly expect documented bias assessments for AI systems affecting individuals. We examine what a credible bias testing programme looks like — from dataset audits to disparate impact analysis.
The international AI safety dialogue — from the Bletchley Declaration to Seoul commitments — is starting to shape binding obligations. What do safety evaluations mean for enterprise AI GRC programmes?
The standards, frameworks, and reference documents that form the backbone of a mature AI governance programme.
Voluntary US framework with Govern, Map, Measure, and Manage functions. Widely adopted globally as a structured AI GRC baseline.
nist.gov →International standard for AI Management Systems. Certifiable. Covers AI policy, risk assessment, and continuous improvement obligations.
iso.org →World's first comprehensive AI regulation. Risk-tiered obligations. Mandatory for organisations deploying AI in the European market.
artificialintelligenceact.eu →Five principles (inclusive growth, human-centred values, transparency, robustness, accountability) forming the philosophical baseline for many national AI policies.
oecd.ai →Technical standards for ethically aligned AI design, including IEEE 7001 (transparency) and IEEE 7010 (wellbeing metrics). Increasingly referenced in procurement.
standards.ieee.org →Conducts frontier model evaluations, publishes safety reports, and develops sector-specific AI governance toolkits in collaboration with global counterparts.
gov.uk/aisi →Every issue of the DeCompliance newsletter is structured to give you strategic and operational intelligence across the full AI GRC spectrum.
Published every Monday — AI GRC intelligence for practitioners navigating the future of regulated AI.
Article 50 transparency obligations go live August 2026. Digital Omnibus pushes high-risk deadlines to December 2027 — but chatbot disclosure is non-negotiable right now.
Real incidents from the past 12 months where AI was weaponised or AI systems failed — with root causes and impact.
An AI-powered triage chatbot integrated into NHS patient-facing services was found to be transmitting patient symptom data, demographic information, and location data to third-party analytics providers without patient consent and outside of NHS DSPT (Data Security and Protection Toolkit) compliance requirements.
The procurement process did not include a Data Protection Impact Assessment (DPIA) for the AI integration. The vendor's data flows were not disclosed in the contract, and the NHS trust's data governance team was not involved in the deployment decision.
Source: ICO Enforcement Action Register, April 2025.
Associates at a mid-size UK law firm were found to have been routinely uploading client documents — including privileged legal advice, draft contracts, and confidential instructions — to personal ChatGPT accounts to assist with drafting. The firm had no AI acceptable use policy and no technical controls blocking access to external AI tools on corporate devices.
The Solicitors Regulation Authority (SRA) opened a supervisory review. The incident also triggered a UK GDPR breach notification obligation to the ICO, as client personal data had been processed by an unauthorised third party without a data processing agreement.
Source: Legal IT Insider, May 2025. SRA regulatory correspondence confirmed.
An autonomous AI trading agent deployed by a mid-size UK asset manager executed a series of large erroneous trades after misinterpreting a Bank of England regulatory announcement as a market signal. The agent had no human approval gate for trades above a defined threshold and no kill-switch that could be activated in real time. By the time human traders identified the anomaly, £4M in losses had been realised.
The firm's model risk framework had been designed for traditional algorithmic trading systems. It did not account for the ability of AI agents to misinterpret unstructured natural language inputs from external sources. No stress testing against regulatory announcement scenarios had been conducted.
Source: FCA Supervisory Notice, August 2025.
Researchers at the University of Edinburgh demonstrated that a UK insurer's publicly accessible AI underwriting API was vulnerable to model inversion attacks. By crafting specific sequences of queries, they were able to reconstruct salary banding, health risk scores, and demographic data for approximately 12,000 employees whose data had been used to train the underwriting model.
Model inversion is not a niche attack — it is a fundamental vulnerability of any AI model trained on personal data and exposed via a queryable interface. Any organisation offering AI-powered services that process personal data in training must assess this risk as part of their AI risk management programme.
Source: University of Edinburgh Security Research Group, November 2025. ICO investigation confirmed.
Adopting AI GRC and security tools introduces new vectors for employee PII and corporate data exposure. Here's what's at risk — and how to protect it.
When employees use AI tools like ChatGPT, Copilot or Gemini, inputs may be used for model training. HR data, performance reviews, and PII can permanently leave your control.
Attackers can query AI models repeatedly to reconstruct personal data used in training — including employee names, salaries, and medical records — through inference attacks.
Employees routinely use personal AI tools for work tasks, uploading employment contracts, legal documents, and payroll data to platforms with unknown data retention policies.
When AI GRC tools process your compliance data, a breach at the vendor exposes your regulatory posture, audit trails, and employee PII to attackers — and regulators.
AI tools making automated HR decisions — recruitment screening, performance scoring — without human oversight violate GDPR Article 22, exposing organisations to ICO enforcement.
Enterprise AI copilots granted broad access to internal systems can access — and potentially leak — far more data than necessary. Least-privilege principles are rarely applied to AI tools.
Companies are deploying autonomous AI agents faster than governance frameworks can keep up. Here's where control is breaking down.
Autonomous agents deployed in finance, HR, and legal functions are making consequential decisions — approving transactions, sending communications, modifying records — with no human-in-the-loop controls.
When autonomous agents make decisions, existing audit frameworks can't answer basic compliance questions: who authorised it, what data was used, and could it be reversed? Regulators expect answers.
AI agents optimise for their programmed objective, not organisational values. An agent tasked to "reduce costs" may cut corners on safety, compliance, or staff welfare without any human noticing.
AI agents are being granted administrator-level access to complete tasks. Once compromised via prompt injection, these agents become the most dangerous insider threat in your network.
Most organisations deploying autonomous agents have no formal policy defining accountability. When an agent makes a damaging decision, legal and compliance teams have no framework to assign responsibility.
When multiple AI agents interact with each other, decisions emerge from the interaction that no single agent was designed to make. Governance frameworks don't account for emergent multi-agent behaviour.
The Digital Omnibus, agreed May 2026, has pushed the main high-risk AI deadline from August 2026 to December 2027 — giving compliance teams 16 extra months. However this does not affect Article 50 transparency obligations, which remain firmly on the 2 August 2026 schedule.
Audit every AI system that interacts with end-users. If it generates text, images, audio or video — or if users might not know they're interacting with AI — Article 50 applies. Document your disclosure mechanisms and ensure they are live before 2 August 2026.
2 August 2026 — Article 50 transparency live. Chatbot disclosure and AI content labelling mandatory.
2 December 2026 — New prohibitions on AI-generated NCII effective.
2 December 2027 — High-risk AI system full obligations enforced.
Sources: EU AI Act (Regulation 2024/1689); Digital Omnibus provisional agreement May 2026; EU Commission AI Office publications.
In February 2024, an employee at Arup's Hong Kong office was invited to a video call with who appeared to be the company's CFO and other senior colleagues. All participants — except the employee — were AI-generated deepfakes. The employee was convinced to make 15 transactions totalling $25M USD to attacker-controlled accounts.
No identity verification protocol existed for video-based financial authorisations. The organisation had no deepfake detection tools, no multi-channel verification requirement, and no financial transfer controls requiring out-of-band confirmation for large transactions.
Under the EU AI Act Article 50, systems generating synthetic video of real people must be labelled. Under FCA guidance, financial institutions must include AI-enabled fraud in their operational risk frameworks. This incident predates enforcement but would today trigger regulatory review.
Source: BBC News, February 2024. Hong Kong Police investigation confirmed.
Three separate Samsung semiconductor employees uploaded confidential information to ChatGPT within weeks of the company permitting its use. Data included proprietary source code, internal meeting notes, and hardware performance data. Once uploaded, Samsung had no mechanism to retrieve or delete the data from OpenAI's systems.
Samsung permitted ChatGPT use without an AI acceptable use policy, without data classification training, and without technical controls restricting what could be uploaded to external AI services. Employees used the tool as they would any productivity application — not understanding that inputs become training data.
An AI acceptable use policy prohibiting upload of classified data to external AI tools, combined with technical DLP controls and staff training on AI data risks, would have prevented all three incidents.
Source: BleepingComputer, April 2023. Confirmed by Samsung internal communications.
Consumer-facing AI tools (ChatGPT free tier, Gemini, Copilot without enterprise licensing) typically use conversation data to train their models. When employees upload HR documents, legal drafts, financial data, or customer records to these tools, that data may permanently leave the organisation's control.
1. Enterprise licensing only — Only permit AI tools with zero-data-retention enterprise agreements.
2. Data Processing Addenda — Require signed DPAs from all AI vendors before deployment.
3. Data classification policy — Categorise data and restrict which categories may be processed by AI tools.
4. Technical controls — Deploy DLP tools that detect and block uploads of classified data to external AI services.
Autonomous AI agents are being deployed in finance (approving payments), HR (screening and rejecting candidates), legal (sending contracts), and operations (modifying system configurations) — all without mandatory human review at consequential decision points.
Unlike traditional software, AI agents operate probabilistically. A decision that works correctly 99% of the time will still fail 1% of the time — and in high-stakes domains, that 1% represents significant legal, financial, and reputational risk.
1. Human-in-the-loop gates — Define which decisions require mandatory human review before execution.
2. Kill-switch protocols — Every autonomous agent must have an override mechanism that a human can trigger immediately.
3. Decision audit logs — Every agent action must be logged with sufficient detail to reconstruct why a decision was made.
4. Scope limitation — Agents should operate within tightly defined boundaries with explicit permission models for each action type.
Publishing 7 July 2026. Subscribe to receive it in your inbox.
Publishing 14 July 2026. Subscribe to receive it in your inbox.
Publishing 21 July 2026. Subscribe to receive it in your inbox.
An AI diagnostic tool deployed across NHS trusts produced systematically less accurate results for ethnic minority patients due to biased training data. No pre-deployment bias audit had been conducted, and no demographic performance monitoring was in place post-deployment.
Training data was not representative of the patient population. Procurement process did not include bias testing as a requirement. No ongoing monitoring for demographic performance disparities was implemented.
Source: British Medical Journal, 2024.
Attorneys at Levidow, Levidow & Oberman submitted a legal brief to a New York federal court containing six AI-generated citations to cases that did not exist. When the court asked for copies of the cases, the firm submitted fake summaries. The court imposed sanctions.
Every AI-generated professional output — legal, medical, financial, or advisory — must be subject to mandatory expert human review before use. This is not optional under professional standards frameworks or emerging AI regulation.
Source: The Guardian, June 2023. US Federal Court docket SDNY.
Criminals synthesised a UK CEO's voice using publicly available audio samples and called the company's finance director, posing as the CEO and requesting an emergency wire transfer citing a confidential acquisition. £1.2M was transferred before the fraud was detected.
Implement callback verification to known numbers for all financial transfers over threshold. Require dual authorisation for transfers above defined limits. Include AI voice fraud in annual staff awareness training.
Attackers embedded hidden instructions in documents and emails fed to enterprise AI copilots. The malicious instructions caused the AI to silently exfiltrate sensitive corporate data by encoding it in outbound requests. Affected organisations had no prompt injection detection in place.
Implement prompt injection detection layers. Apply data minimisation — AI systems should only access data necessary for their function. Monitor for anomalous AI output patterns. Treat all external content processed by AI as potentially hostile.
Model inversion attacks allow adversaries to query AI models repeatedly and reconstruct personal data from training sets. If your AI model was trained on employee data, attackers may be able to extract names, salaries, medical records, or other PII through carefully crafted queries — without ever accessing your database directly.
Differential privacy — Add mathematical noise to training data to prevent memorisation of individual records.
Output filtering — Monitor and filter AI outputs for patterns that match personal data formats.
Rate limiting — Limit query rates to prevent systematic extraction attempts.
Audit logging — Log all queries to AI systems processing personal data for anomaly detection.
Shadow AI — the use of unsanctioned AI tools by employees — is now one of the fastest-growing data protection risks. Employees routinely upload employment contracts, client data, legal documents, and financial records to personal AI tools without understanding the data retention implications.
Publish an approved AI tool list with clear guidance on what data each tool may process. Deploy web filtering to block access to non-approved AI services from corporate devices. Include shadow AI in your annual data protection impact assessments. Train staff on the difference between personal and corporate AI tool use.
Every AI GRC or security tool you adopt processes your most sensitive data — compliance posture, audit findings, risk assessments, and employee records. A breach at an AI vendor doesn't just expose their data — it exposes yours.
Require ISO 27001 and SOC 2 Type II certification as minimum vendor security standards. Include right-to-audit clauses in all AI vendor contracts. Assess vendor incident response procedures before procurement. Maintain a data processor register with breach notification obligations documented for each vendor.
GDPR Article 22 grants individuals the right not to be subject to solely automated decisions that produce significant effects — including decisions about employment, credit, insurance, or healthcare. AI tools used for CV screening, performance assessment, or credit scoring without human review violate this right.
Map all automated decisions affecting individuals. For any significant decision, implement mandatory human review before the decision is actioned. Document the human review process and maintain records. Include Article 22 rights in your privacy notice and honour subject access requests that include AI-generated profiles.
Enterprise AI copilots are routinely granted broad read and write access to email, file systems, calendars, HR systems, and financial platforms. This over-permissioning means a single compromised AI session can access vastly more data than any individual employee — and a prompt injection attack on an over-permissioned agent is catastrophic.
Treat every AI integration as a privileged system account. Map what data each AI tool needs to access and restrict accordingly. Review AI tool permissions quarterly. Log all AI system access to sensitive data stores and monitor for anomalous access patterns.
Traditional audit frameworks assume human decision-makers who can be interviewed, whose communications can be reviewed, and who have a documented decision rationale. Autonomous AI agents produce none of these artefacts by default — and most organisations haven't built AI-specific audit logging.
Every agent action should log: the input that triggered it, the reasoning chain, the action taken, the systems affected, the timestamp, and the identity of the agent and its operator. These logs must be immutable, retained for the regulatory minimum period, and accessible to auditors on demand.
AI agents are objective-maximisers. They will pursue their programmed goal using any available means unless constrained. An agent tasked to "maximise customer retention" may make promises the organisation cannot keep. An agent tasked to "minimise processing time" may skip required compliance checks. Goal misalignment is the single most consequential AI governance risk for autonomous systems.
Define agent objectives to include compliance constraints, not just performance targets. Implement reward modelling that penalises non-compliant actions. Test agent behaviour against adversarial inputs before deployment. Monitor for objective proxy gaming — where an agent achieves its metric while violating the underlying intent.
To complete complex tasks, AI agents are frequently granted administrator-level access to internal systems. This creates the most dangerous attack surface in modern enterprise IT — an agent that can be hijacked via prompt injection and then used to access, modify, or exfiltrate anything in the organisation's infrastructure.
Apply least-privilege access to all AI agents without exception. Implement action whitelists — define exactly which actions each agent is permitted to take and block everything else. Never grant agents persistent credentials. Use short-lived tokens with narrow scopes for every agent action.
When an autonomous AI agent makes a damaging decision — sending a discriminatory rejection letter, approving a fraudulent payment, publishing incorrect information — who is legally responsible? In most organisations, the answer is genuinely unclear because no AI agent policy exists.
Every AI agent deployment should have: an owner accountable for its behaviour; documented scope and limitations; an incident response procedure; a shutdown protocol; and defined escalation paths for edge cases. This policy must be reviewed at least annually and whenever the agent's capabilities or scope changes.
When multiple AI agents interact — an orchestrator agent directing specialist sub-agents across finance, legal, and operations — decisions emerge from the interaction that no single agent was designed to make. Existing governance frameworks, designed for single AI systems with defined inputs and outputs, fail completely when applied to multi-agent architectures.
Treat multi-agent systems as a single governed entity with a single accountable owner, not as a collection of individual agents. Define the system boundary, the maximum scope of action the system can take without human intervention, and the conditions under which human escalation is mandatory. Audit the system's emergent behaviour, not just the behaviour of individual agents.
DeCompliance was founded with a single conviction: that the organisations that understand AI governance now will be the ones that thrive as regulation matures. Too much AI compliance content is either theoretical or too technical for practitioners who need to act.
DeCompliance exists to bridge that gap — delivering clear, actionable intelligence on the regulatory frameworks, risk practices, and governance structures that matter to professionals working at the intersection of AI and compliance.
Whether you're a Chief Risk Officer, a DPO, a legal counsel, or an AI engineer trying to understand your regulatory obligations — this newsletter is built for you.
"Complexity is not an excuse for inaction. Good governance demystifies it."
Last updated: June 2026
DeCompliance ("we", "us", "our") is an AI Governance, Risk & Compliance intelligence newsletter published from the United Kingdom at decompliance.uk. The data controller for personal data collected through this website is Darshan Krishnappa, Founder of DeCompliance.
When you subscribe to our newsletter, we collect:
We do not collect payment information, sensitive personal data, or data from children under the age of 13.
We use your personal data solely to:
We do not use your data for automated profiling, advertising, or any purpose beyond newsletter delivery.
Our legal basis for processing your personal data is consent (Article 6(1)(a) UK GDPR). You provide this consent when you subscribe to our newsletter. You may withdraw your consent at any time by unsubscribing.
We do not sell, rent, or trade your personal data to third parties. We may share data with trusted service providers who assist in delivering our newsletter (such as email delivery platforms), under strict data processing agreements. All processors are required to handle your data in accordance with UK GDPR.
We retain your personal data for as long as you remain a subscriber. If you unsubscribe, your data will be deleted within 30 days, unless we are required to retain it for legal or compliance purposes.
Under UK GDPR, you have the right to:
To exercise any of these rights, please contact us at hello@decompliance-uk.com. We will respond within 30 days.
This website does not currently use tracking cookies or third-party analytics. If this changes, we will update this policy and seek your consent where required.
We implement appropriate technical and organisational measures to protect your personal data against unauthorised access, disclosure, alteration, or destruction.
If you are unhappy with how we handle your data, you have the right to lodge a complaint with the UK Information Commissioner's Office (ICO) at ico.org.uk.
We may update this Privacy Policy from time to time. We will notify subscribers of any material changes via email or a notice on this website. Continued use of the newsletter after any changes constitutes acceptance of the updated policy.
For any privacy-related queries, please contact: hello@decompliance-uk.com
Last updated: June 2026
By accessing or using the DeCompliance website at decompliance.uk or subscribing to the DeCompliance newsletter, you agree to be bound by these Terms of Use. If you do not agree, please do not use this website or subscribe to our newsletter.
DeCompliance is an independent AI Governance, Risk & Compliance (GRC) intelligence newsletter published from the United Kingdom. Our content covers regulatory developments, governance frameworks, risk management practices, and compliance intelligence relating to artificial intelligence.
All content published on this website and in the DeCompliance newsletter — including text, analysis, commentary, graphics, and design — is the intellectual property of DeCompliance and its founder, unless otherwise stated. You may not reproduce, distribute, or republish our content without prior written permission, except for brief quotations with attribution.
The content provided by DeCompliance is for informational and educational purposes only. It does not constitute legal advice, regulatory advice, compliance advice, or professional services of any kind. You should not act or refrain from acting on the basis of our content without seeking independent legal or professional advice appropriate to your specific circumstances.
DeCompliance accepts no liability for any action taken or not taken in reliance on content published in the newsletter or on this website.
We endeavour to ensure that all information published is accurate and up to date at the time of publication. However, the AI regulatory landscape changes rapidly. We make no warranties or representations as to the accuracy, completeness, or currency of any content. Links to third-party sources are provided for reference only and do not constitute endorsement.
By subscribing to the DeCompliance newsletter, you consent to receiving periodic email communications from us. You may unsubscribe at any time by following the unsubscribe link in any newsletter email or by contacting us at hello@decompliance-uk.com. We will not send unsolicited commercial communications.
This website contains links to external websites and resources, including regulatory bodies, standards organisations, and government publications. These links are provided for convenience and informational purposes only. DeCompliance is not responsible for the content, accuracy, or availability of third-party websites.
To the fullest extent permitted by applicable law, DeCompliance and its founder shall not be liable for any direct, indirect, incidental, consequential, or special damages arising from your use of this website or reliance on any content published herein, including but not limited to loss of revenue, data, or business opportunity.
These Terms of Use are governed by and construed in accordance with the laws of England and Wales. Any disputes arising from these terms or your use of this website shall be subject to the exclusive jurisdiction of the courts of England and Wales.
We reserve the right to update these Terms of Use at any time. Changes will be posted on this page with an updated date. Continued use of the website or newsletter after changes constitutes acceptance of the revised terms.
For any queries relating to these Terms of Use, please contact: hello@decompliance-uk.com