Indirect prompt injection
An attack in which malicious instructions are embedded inside content an agent processes as data, such as a webpage, a document, a ticket, or a third-party chatbot's response, rather than delivered directly by the agent's own user. The agent's user need not know the attack exists, and the attacker need not have any relationship with the agent's user or operator. Named directly in the Model AI Governance Framework for Agentic AI (IMDA v1.5, p.40) as the risk surfaced inside the Google x Singapore Government sandbox.
Defined in 5 GAGE programs, which carry 14 distinct definitions of it. The wording above is taught in Certified Agentic AI Governance Professional (CAAGP).
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
An attack in which malicious instructions are embedded inside content an agent processes as data, such as a webpage, a document, a ticket, or a third-party chatbot's response, rather than delivered directly by the agent's own user. The agent's user need not know the attack exists, and the attacker need not have any relationship with the agent's user or operator. Named directly in the Model AI Governance Framework for Agentic AI (IMDA v1.5, p.40) as the risk surfaced inside the Google x Singapore Government sandbox.
An attack in which the adversary hides instructions inside content the AI later reads on someone else's behalf (a web page, email, document, image, or other format the AI processes), so an innocent user triggers the attack by doing normal work (Greshake et al., 2023). As AI tools process more content types (images, PDFs, audio), the potential carrier formats for indirect injection expand accordingly.
Prompt injection in which the malicious instruction is hidden inside external content the system ingests (a document, email, web page, or ticket), so the system follows a command the attacker never typed into the conversation. The failure most teams forget because the instruction does not arrive through the chat box.
A form of prompt injection where the attacker plants adversarial instructions inside content (a document, webpage, email, ticket) that an AI system is expected to retrieve and process later, on behalf of a different, legitimate user, without the attacker ever interacting with the AI system directly.
A prompt injection attack where the malicious instruction is hidden inside content the AI system retrieves on the user's behalf, such as a webpage or document, without the user ever seeing or typing it.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- Evaluating AI Outputs for Accuracy · Practical AI Workflow Design and Prompt Engineering, Certified AI Practitioner: Workplace Foundations
- ROI and Security Mastery Checks · Assessment and Continuous Learning, Certified AI Practitioner: Workplace Foundations
- Prompt Injection and Jailbreak Defense · AI Security Fundamentals, Certified AI Practitioner: Workplace Foundations
- The Safety Components · The Agent, Deconstructed, Certified Agentic AI Governance Professional (CAAGP)
- The Whole Framework, Worked · The Agent, Deconstructed, Certified Agentic AI Governance Professional (CAAGP)
- Protocol-Layer Threats · Technical Controls and Threat Modeling, Certified Agentic AI Governance Professional (CAAGP)
- Build the Test Environment Before You Trust a Single Score · Testing and Red-Teaming, Certified Agentic AI Governance Professional (CAAGP)
- Red Teaming an Agent Starts With Its Use Case, Not a Generic Checklist · Testing and Red-Teaming, Certified Agentic AI Governance Professional (CAAGP)
- Testing What You Did Not Build · Testing and Red-Teaming, Certified Agentic AI Governance Professional (CAAGP)
- Attacks on the Collective · Multi-Agent Governance, Certified Agentic AI Governance Professional (CAAGP)
Where it shows up at work
A definition is where Indirect prompt injection starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Understands prompt injection, data poisoning, model theft, insecure integrations and excessive agent privileges, and the controls that reduce each.
2 lessons on this page teach it as a primary outcome.
Designs tests for factuality, robustness, fairness, safety and abuse resistance with rubrics, baselines and thresholds, and says what a score misses.
2 lessons on this page teach it as a primary outcome.
Tiers vendors by use and impact, requests evidence instead of promises, tests in the customer's context, and plans monitoring and exit.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- Chief Technology Officer, AI engineering editionneeds it at depth
- AI Security Architectneeds it at depth · 8 open postings this week
- AI Governance Engineerneeds it at depth · 7 open postings this week
- AI Evaluation Specialistneeds it at depth · 6 open postings this week
- Chief Information Security Officer, AI security focusneeds it at depth
- Cybersecurity Risk Analystneeds working knowledge
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: OWASP Top 10 for LLM Applications; Google SAIF; NIST AI RMF MEASURE 2; NIST AI RMF MEASURE 1 and 2.
One interview question about it
What are the security failure modes specific to AI systems, and which conventional control covers none of them?
Asked of candidates for ai security fundamentals. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- Cybersecurity and IT carries it as a claim to back up: Threat modeling and control design transfer; the AI-specific threats are new.
- A computer science or software engineering degree carries it as a claim to back up: Security fundamentals are a course you took, not yet a control you ran.
- A cybersecurity or information assurance degree carries it as work you can show: Security fundamentals are your coursework and your labs.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.