Explain least privilege. How would you apply it to a new team's cloud and app access?
AI security · Beginner 3
Short answer
Least privilege means every person, service and AI agent gets only the access it needs, for only as long as it needs it. In practice I start from no access, grant roles per job, avoid shared admin accounts, use short-lived credentials, require MFA, and review access regularly so leftovers are removed when people change roles or leave.
Deeper answer
Least privilege limits the blast radius. If an account is phished or a key leaks, the attacker gets only what that account could do. It applies to machines too: a reporting service needs read access to one database, not admin on the whole cloud account. AI agents with tools need the same care, because an injected instruction can only use the rights the agent holds.
Practical steps: role-based groups instead of per-person grants, separate admin accounts used only for admin work, just-in-time elevation with approval, secrets in a vault rather than in code, and a quarterly access review. Log privileged actions so you can see when broad rights are actually used.
What a strong answer covers
- Defines it: only the access needed, for only as long as needed
- Explains blast radius if an account is compromised
- Uses roles, MFA and short-lived or just-in-time access
- Regular access reviews and removal
- Applies it to services or AI agents too
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- How do you handle an engineer who needs production access during an outage?
- How does least privilege apply to an AI agent with tools?
Common mistakes
- Giving everyone admin to move fast and promising to tighten later
- Never reviewing access, so old rights pile up
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.
- 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?