Staff are pasting company data into public AI tools without approval. How would you handle shadow AI?
AI security · Pro 2
Short answer
Banning everything usually drives it underground. I would find out what people use and why, offer an approved tool with proper data terms, write a short policy on what data may go where, add technical controls for the riskiest data, and train people with real examples. Then keep an AI inventory and review new tools through a quick, clear process.
Deeper answer
Start with discovery: proxy and DNS logs, browser extension lists, expense claims and a no-blame survey. Classify the risk: customer personal data, source code, unreleased financials and credentials are the main concerns, along with DPDP Act duties for personal data.
Then offer a safe path: an enterprise AI tool with data not used for training, sign-on, logging and retention settings. Write a one-page policy with clear examples of allowed and not allowed. Back it with controls: data loss prevention rules for identifiers and secrets, blocking unapproved tools that handle sensitive data, and an intake form so teams can request a new tool and get an answer in days, not months. Measure adoption of the approved tool and repeat discovery every quarter.
What a strong answer covers
- Discovers actual use without blame
- Offers an approved alternative
- Short policy on data classes
- Technical controls such as DLP or blocking
- Ongoing review and a fast intake process
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- How would you discover which AI tools staff are already using?
- What would your one-page AI policy say?
Common mistakes
- Banning all AI tools with no approved alternative
- Writing a long policy that no one reads and nothing enforces
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?
- 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?
- Your SOC gets thousands of SIEM alerts a day and analysts are ignoring them. How do you fix alert fatigue?