What is the CIA triad, and how would you use it to judge a security problem?
AI security · Beginner 2
Short answer
CIA stands for confidentiality, integrity and availability. Confidentiality means only the right people see data. Integrity means data is not changed without permission. Availability means systems work when people need them. For any incident or design, I ask which of the three is at risk, how badly, and which control protects it.
Deeper answer
The triad is a checklist for impact. A leaked customer list is a confidentiality problem; a changed bank account number in an invoice is an integrity problem; a website knocked offline is an availability problem. One incident can hit more than one: ransomware encrypts files (availability) and often steals them first (confidentiality).
Each goal has typical controls. Confidentiality: access control, encryption, data minimisation. Integrity: hashing, digital signatures, change approval, audit logs. Availability: backups, redundancy, rate limits and tested recovery. The goals can pull against each other, so a good answer names the trade-off, such as strict access slowing down an urgent fix.
What a strong answer covers
- Names confidentiality, integrity and availability correctly
- Gives an example of each goal being broken
- Links each goal to controls
- Notes one incident can hit more than one goal, or that goals trade off
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- Which part of the triad does ransomware hit, and why is the answer often more than one?
- How does the triad apply to an LLM chatbot?
Common mistakes
- Saying encryption alone covers all three goals
- Forgetting availability, as if security were only about secrecy
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 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?