Attackers now use LLMs to write phishing emails. What changes for defenders, and what still works?
AI security · Intermediate 2
Short answer
AI makes phishing fluent, personalised and cheap, in any language, so spotting bad grammar no longer works. What still works are controls that do not depend on the wording: DMARC and sender checks, link and attachment analysis, phishing-resistant MFA, process checks for payments and data requests, and training people to verify the request rather than judge the writing.
Deeper answer
LLMs help attackers research targets from public profiles, write convincing messages in Hindi, Tamil or English, and run many variations, which weakens filters that match known text. They also power chat-based scams that keep a conversation going.
Defenders should lean on signals attackers cannot easily fake: sender authentication, domain age and reputation, unusual sending patterns, links to newly registered domains, and requests that break normal process. Phishing-resistant MFA removes much of the payoff of stolen passwords. Update training: teach 'check the request and the channel', not 'look for typos'. Defenders can also use AI, for example classifiers and LLM triage of reported emails, while keeping a human in the loop.
What a strong answer covers
- AI makes phishing fluent, personalised and scalable
- Grammar-based spotting no longer works
- Controls independent of wording: sender checks, links, MFA
- Process checks and updated training
- Defenders can use AI too, with human review
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- Which detection signals still work when the text is perfect?
- How would you change your phishing training?
Common mistakes
- Still teaching staff to look for spelling mistakes
- Assuming a better content filter alone is enough
Learn it
AI-powered attacks and how defenders respond
- 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?
- 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?