Guides
Every guide to AI prompt attacks
Start with the main guides, then go deeper on the parts that apply to you.
Last reviewed against NCSC (UK), OWASP Gen AI Security Project and UK Government (DSIT). Sources
Start here
The main guides
Am I exposed?
A checklist for UK organisations: which AI tools read outside content, hold private data or can act, and so could be manipulated by prompt injection.
Read the guide
Reduce the risk
The NCSC's four areas of advice for prompt injection, with practical limits on privileges, approvals and logging for UK organisations.
Read the guide
Timeline
Dated events on prompt injection, from NCSC guidance and the OWASP ranking to EchoLeak, the lethal trifecta and OpenAI's browser warning.
Read the guide
Questions
Sourced answers on prompt injection: what it is, whether it can be fixed, what indirect injection means and what UK organisations should limit.
Read the guide
About this site
Who runs AI Prompt Attacks, why CyPro Consulting Ltd built it and how its account of prompt injection is checked against its sources.
Read the guideIn depth
Your product or situation
What it is
Prompt injection explained: how crafted input changes an AI model's behaviour, why it differs from SQL injection and what the NCSC advises.
Read the guide
Indirect injection
How instructions hidden in emails, web pages and documents can steer an AI tool, with OWASP's example scenarios and what to limit.
Read the guide
Lethal trifecta
Simon Willison's lethal trifecta explained: private data, untrusted content and external communication, and how to break the combination.
Read the guide
EchoLeak
What EchoLeak (CVE-2025-32711) was, how a crafted email could leak data from Copilot, what Microsoft said and what it teaches UK organisations.
Read the guide
AI browsers
OpenAI says prompt injection in AI browsers is unlikely to be fully solved. What that means for UK organisations that let agents browse and act.
Read the guide
Ask suppliers
A buyer's list of questions on prompt injection for AI suppliers, drawn from NCSC and OWASP advice, for UK procurement and security leads.
Read the guide
Monitoring
What to log and watch for when AI tools may be attacked through prompt injection, based on NCSC and OWASP advice for UK security teams.
Read the guideHow CyPro can help
Need a hand with any of this?
Patching is one job. Keeping a vulnerable system safe until it is patched, and proving it, is several more. CyPro's consultants, testers and SOC analysts can take any of them off your plate.
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
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
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
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
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
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
Know your exposure
Not sure you are protected?
Prompt injection cannot be patched away, so the useful question is how far a manipulated tool could reach. Testing your AI-connected systems the way an attacker would shows where the limits on data and actions need tightening.