Guides
Every guide to AI Data Breach
Start with the main guides, then go deeper on the parts that apply to you.
Last reviewed against legislation.gov.uk, National Cyber Security Centre and OWASP GenAI Security Project. Sources
Start here
The main guides
What to do
Practical steps for UK organisations: find AI use, restrict data, prepare breach response and brief staff, each tied to NCSC, OWASP and UK GDPR sources.
Read the guide
Timeline
The public AI data exposures and the UK guidance that followed, in date order and sourced, from the March 2023 ChatGPT bug to the 2025 IBM research.
Read the guide
Questions
Sourced answers on what counts as an AI data breach, the 72 hour reporting rule, shadow AI, exposed databases and what UK organisations should do.
Read the guide
About this site
Who publishes this guide to AI data breaches, why it exists and how every statement is sourced and kept current.
Read the guideIn depth
Your product or situation
Shadow AI
How staff use of unapproved AI tools leaks company and personal data, what IBM and Samsung's experience show, and how to find and reduce it.
Read the guide
Exposed databases
What Wiz found in an open DeepSeek database, why it matters for any AI service and the checks UK teams can make on their own AI data stores.
Read the guide
Prompt leaks
How an LLM can disclose personal or confidential data through its outputs, what OWASP and the NCSC advise, and the design choices that limit it.
Read the guide
Reporting
When an AI data breach must be reported under UK GDPR, how the 72 hour clock works, and what to record whether or not you report.
Read the guide
Examples
Three public AI data exposure cases, a library bug, staff uploads and an open database, with what each shows UK organisations about cause and response.
Read the guide
Prevention
Practical controls to stop data leaking through AI tools and pipelines, drawn from NCSC guidance, OWASP and IBM research, in order of priority.
Read the guide
Containment
A practical first-response plan for a suspected AI data breach: stop the exposure, scope the data, preserve evidence, decide on reporting and review.
Read the guide
Suppliers
Questions to ask AI suppliers about data storage, training use, access and incident notification, based on NCSC guidance for UK organisations.
Read the guide
Data protection
What the ICO's AI and data protection guidance says about impact assessments, transparency and lawfulness, and how it links to breach duties.
Read the guide
AI use policy
How to write a short AI use policy that stops sensitive data going into AI tools, using OWASP, NCSC and IBM findings as the basis.
Read the guideHow CyPro can help
Need a hand working through this?
Finding out whether an incident reaches you is one job. Checking your own systems, tightening access and briefing the board are several more. CyPro's responders and consultants can take any of them on.
Incident response
If you may already be compromised, our responders contain it, preserve the evidence, find out what was touched and get you running again safely.
More on cypro.co.uk
24/7 security monitoring
Our SOC analysts watch your systems day and night for the signs of an attack in progress: unexpected processes, new outbound connections, logins that do not fit.
More on cypro.co.uk
Fractional CISO for the board
A senior security lead who advises the board on what to fix first, what to accept and what to tell customers, and owns the decision record.
More on cypro.co.uk
Penetration testing
A focused test of your systems and the controls around them, so you know they hold before an attacker finds out for you.
More on cypro.co.uk
Hardening and segmentation
Our consultants put the controls in place that limit the damage when something is missed: firewall rules, network isolation and tighter admin access.
More on cypro.co.uk
Vulnerability scanning
Find every internet-facing system you run, including the forgotten ones, and see which are still on a vulnerable build.
See the scanning service
Talk to a specialist
Worried this affects you?
If data has leaked through an AI tool or an exposed AI database, the first hours decide how much is lost and what you must report. An incident response team helps you contain it, work out what was exposed and meet your notification duties.