What is a model extraction attack, and how would you defend a model you serve through an API?
AI security · Pro 1
Short answer
Model extraction is when an attacker sends many queries to your API and uses the answers to train a copy of your model, stealing its value or helping plan other attacks. Defences: authentication, rate and quota limits, monitoring for unusual query patterns, returning only what users need instead of full probabilities, terms of use, and watermarking where possible.
Deeper answer
Each answer is a labelled training example for the attacker. Detailed outputs such as full probability scores leak more than a single label. A stolen copy can also be used offline to find adversarial inputs that then work against your real model.
Defences come in layers: require API keys tied to accounts; set quotas and rate limits; watch for many diverse or systematic queries from one account or a group of new accounts; reduce output detail; and price or gate bulk access. For LLMs, watermarking outputs and contract terms help with proof and deterrence. Related privacy attacks, membership inference and training data extraction, need limits on what the model memorises, such as deduplicating training data, and testing whether it repeats sensitive records.
What a strong answer covers
- Defines extraction: queries used to train a copy
- Explains why it matters: lost value or a stepping stone to other attacks
- Rate limits, quotas and authentication
- Monitoring and reduced output detail
- Mentions watermarking, terms, or related privacy attacks
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- Why do probability scores make extraction easier?
- How is membership inference different from model extraction?
Common mistakes
- Assuming a model behind an API cannot be copied
- Relying only on legal terms without rate limits or monitoring
Learn it
Model extraction and privacy attacks
- 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?
- 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?
- 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?