What is the difference between hashing and encryption, and which do you use for passwords?
AI security · Beginner 3
Short answer
Encryption is two-way: with the key you can get the original data back. Hashing is one-way: you cannot reverse it, you can only hash a new input and compare. Passwords should be hashed, with a slow algorithm made for passwords such as Argon2 or bcrypt and a unique salt, never encrypted or stored as plain text.
Deeper answer
Use encryption when you need the data back later, such as a scanned ID document stored for KYC, or data in transit with TLS. Its safety depends on protecting the key. Use hashing when you only need to check a value matches, such as a password or a file's integrity.
Fast hashes like SHA-256 are good for checking files but poor for passwords, because attackers can try billions of guesses quickly. Password hashing algorithms are deliberately slow and take a salt, a random value per user, so two users with the same password get different hashes and precomputed tables do not work. Never invent your own scheme; use a maintained library.
What a strong answer covers
- Encryption is reversible with a key
- Hashing is one-way and compared, not reversed
- Passwords use a slow password hash
- Explains salt
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- What is a salt, and what attack does it stop?
- Why is SHA-256 a poor choice for storing passwords?
Common mistakes
- Saying passwords should be encrypted so they can be recovered
- Using a fast hash such as MD5 or plain SHA-256 for passwords
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?
- 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?