You are asked to red-team your company's customer support chatbot before launch. How do you go about it?
AI security · Pro 2
Short answer
First get written scope and permission, and test a staging copy. Then list what could go wrong: data leaks, prompt injection, off-policy answers, tool misuse, cost abuse. Run manual tests plus automated attack suites with tools like promptfoo, garak or PyRIT, score results, report findings by severity, fix, and keep the attacks as regression tests.
Deeper answer
Scope: which system, which environment, what is off-limits, who to call if something breaks. Build the attack list from the threat model and the OWASP LLM Top 10, plus business harms specific to the bot, such as promising refunds it cannot give or revealing another customer's order.
Mix methods: creative manual probing by people who know the domain and languages your users speak, and automated suites that generate many variations of jailbreaks and injections, including indirect injection through documents the bot retrieves. Use a clear pass or fail rule per test, often an LLM judge checked by humans. Report each finding with steps, impact, severity and a suggested fix. Retest after fixes and add every successful attack to the CI suite.
What a strong answer covers
- Written scope and permission, staging environment
- Threat model and attack categories
- Manual and automated testing with named tools
- Scoring and a findings report by severity
- Fix, retest and add to regression suite
Answer it out loud in the mock interview about 2 min
Follow-ups to expect
- How do you decide the severity of a finding?
- Why test in the languages your users speak, not only English?
Common mistakes
- Starting tests without written permission and scope
- Running a tool once and calling the bot safe
Learn it
- 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?
- Walk me through the OWASP Top 10 for LLM applications. Which risks would you check first in a RAG chatbot?
- 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?
- 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?