1. CIA triad
Confidentiality, Integrity, and Availability are the three goals every control protects.
cia_triad: confidential-integrity-availableTyporithm · medium
Step 1 of 8 · intro card
Security Interview
Interviewers probe fundamentals: define the CIA triad, contrast one-way hashing with reversible encryption, distinguish symmetric (shared secret) from asymmetric (key pair), explain the TLS handshake, and know why passwords are salted before hashing.
The CIA triad — Confidentiality, Integrity, Availability — is the framing for almost every security control, so be ready to define it and give an example of each.
Know the difference between hashing and encryption: hashing is a one-way function with no key (used for integrity and password storage), while encryption is reversible with a key. Symmetric encryption shares one secret key; asymmetric encryption uses a public/private key pair.
The TLS handshake authenticates the server with a certificate, then both sides derive symmetric session keys used for the bulk of the connection. Passwords are stored as salted hashes — a per-password random salt stops rainbow tables and ensures equal passwords hash to different values.
CIA triad: Confidentiality, Integrity, Availability.
Hashing is one-way; encryption is reversible with a key.
Salt is per-password random data, added before hashing.
concepts:
cia_triad: confidential-integrity-available
hashing_vs_encryption: oneway-vs-reversible
symmetric_vs_asymmetric: shared-vs-keypair
tls_handshake: cert-then-session-keys
salting: per-password-randomConnect each part of the code to the concept before you type.
Confidentiality, Integrity, and Availability are the three goals every control protects.
cia_triad: confidential-integrity-availableHashing is one-way (no key, cannot be reversed); encryption is reversible with a key.
hashing_vs_encryption: oneway-vs-reversibleSymmetric uses one shared secret; asymmetric uses a public/private key pair.
symmetric_vs_asymmetric: shared-vs-keypairTLS authenticates with a certificate, then negotiates symmetric session keys for the actual traffic.
tls_handshake: cert-then-session-keysA unique random salt per password defeats rainbow tables and makes identical passwords hash differently.
salting: per-password-randomRead the concept map and follow the code breakdown.
Type the implementation, repair mistakes and work through every recall exercise.
Use the final check without hints; revisit weak concepts in short practice sessions.