Walk me through the OWASP Top 10 for LLM applications. Which risks would you check first in a RAG chatbot?
AI security · Intermediate 3
Short answer
The 2025 list covers prompt injection, sensitive information disclosure, supply chain, data and model poisoning, improper output handling, excessive agency, system prompt leakage, vector and embedding weaknesses, misinformation, and unbounded consumption. For a RAG chatbot I would check prompt injection, data disclosure through retrieval, vector store access control, output handling and cost limits first.
Deeper answer
The list is a shared vocabulary, not a full test plan. Map each item to your design. In a RAG chatbot: indirect prompt injection arrives inside retrieved documents; sensitive information leaks when retrieval ignores the user's permissions; vector and embedding weaknesses include a shared index without per-user filters; improper output handling means rendering model output as HTML or running it as code without checks; system prompt leakage matters if secrets or rules live in the prompt; unbounded consumption is long inputs or loops that run up the bill.
For each risk, write the control and a test: injected documents in the test set, permission tests per user, output encoding, rate and token limits. Re-check after every major change.
What a strong answer covers
- Names most of the ten risks correctly
- Picks risks relevant to RAG
- Explains improper output handling
- Ties each risk to a control and a test
Answer it out loud in the mock interview about 2 min
Follow-ups to expect
- What does improper output handling look like in practice?
- Why is system prompt leakage a problem only if the design is already weak?
Common mistakes
- Reciting the list without linking risks to the actual system
- Treating prompt injection as the only LLM risk
Learn it
Threats to LLM apps: the OWASP Top 10
- Attackers now use LLMs to write phishing emails. What changes for defenders, and what still works?
- What is attack success rate in AI red teaming, and what are its limits as a metric?
- Threat model an LLM chatbot for a retail bank that can answer questions and show a customer's recent transactions.
- What is the CIA triad, and how would you use it to judge a security problem?
- What is data poisoning, and how would you protect a model you train or fine-tune from it?
- As a security engineer, how would you protect a company's finance team from deepfake voice or video calls from the 'CEO'?
- You find code that builds a SQL query by joining strings with user input. What is the risk and how do you fix it?
- What is the difference between hashing and encryption, and which do you use for passwords?
- An employee's laptop shows signs of malware at 11 pm. Walk me through your incident response.
- Explain least privilege. How would you apply it to a new team's cloud and app access?
- Your SOC wants an LLM copilot to summarise alerts and suggest actions. What are the risks and how do you manage them?
- What is tool poisoning in MCP or agent tools, and how do you defend an agent against it?
- What is MITRE ATT&CK, and how does a detection team actually use it?
- A vendor says their ML intrusion detector is 99% accurate. Why might it still drown your SOC in false alarms?
- What is a model extraction attack, and how would you defend a model you serve through an API?
- How would you defend a company against phishing? Where do SPF, DKIM and DMARC fit in?
- A teammate wants to load a model file they downloaded from a public hub. What supply chain risks do you check?
- You are asked to red-team your company's customer support chatbot before launch. How do you go about it?
- Tell me about a security incident or near miss you handled. What did you do and what changed afterwards?
- Staff are pasting company data into public AI tools without approval. How would you handle shadow AI?
- Your SOC gets thousands of SIEM alerts a day and analysts are ignoring them. How do you fix alert fatigue?