From the Cybersecurity course. Covers both halves — offensive (how it’s attacked) and defensive (how it’s detected and stopped) — because interviews for either side probe the other.
Files
- AppSec, Crypto & Defence — OWASP-style vulnerabilities, crypto fundamentals, secure design, incident response
Note on framing
Security interviews reward threat modelling out loud: who’s the attacker, what do they want, what’s the trust boundary, what happens when it’s crossed. Reciting the OWASP Top 10 is table stakes; reasoning about a specific system’s exposure is the signal.
Also: for anything offensive, always frame it within authorisation — scope, rules of engagement, and a written agreement. Candidates who talk about attacking things without mentioning authorisation raise a flag, regardless of technical skill. → rules of engagement
Related
- Cybersecurity course
- Concepts: auth questions — heavy overlap
- Networking: TLS & DNS
Software engineering
Infrastructure & security
Computer science
Hardware & engineering