How would you defend a company against phishing? Where do SPF, DKIM and DMARC fit in?
AI security · Intermediate 1
Short answer
Use layers. SPF lists which servers may send mail for our domain, DKIM signs messages, and DMARC tells receivers what to do when those checks fail and sends us reports, which stops others spoofing our exact domain. Add mail filtering, phishing-resistant MFA, link and attachment checks, an easy report button, and short, regular training.
Deeper answer
SPF, DKIM and DMARC protect your own domain from being forged. Roll DMARC out in stages: start with p=none to collect reports and find all legitimate senders, such as the payroll or marketing tool, then move to quarantine and reject. They do not stop look-alike domains such as a letter swapped or a different ending, or mail from a real but hacked account.
So other layers matter: filtering and sandboxing of attachments, warnings for external senders and new domains, phishing-resistant MFA such as passkeys or security keys so a stolen password is not enough, and processes such as call-back checks before payment changes. Make reporting one click and thank people who report; measure report rate, not just click rate.
What a strong answer covers
- Explains SPF, DKIM and DMARC correctly
- Knows their limit: look-alike domains and hacked accounts
- Phishing-resistant MFA and technical filtering
- Easy reporting and process checks
- Training without blame
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- Why does DMARC not stop a look-alike domain?
- Why start DMARC with p=none?
Common mistakes
- Thinking DMARC stops all phishing
- Relying only on training and blaming people who click
Learn it
Phishing and social engineering
- 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?
- 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?