1.Explain the OSI model and where security controls sit.
Physical, data link, network, transport, session, presentation, application. Map controls: port security at layer 2, ACLs and firewalls at 3 and 4, TLS at the presentation boundary, WAF and application filtering at 7. Interviewers use the mapping, not the list, to judge you.
2.What is the TCP three-way handshake?
SYN, SYN-ACK, ACK. The security angle is the half-open state after SYN-ACK — a SYN flood fills that table so legitimate connections are refused. SYN cookies mitigate it without keeping state.
3.How does DNS work, and how is it attacked?
Recursive resolution from resolver to root, TLD and authoritative servers, with caching at each step. Attacks: cache poisoning, spoofed responses over UDP, DNS tunnelling for exfiltration, and NXDOMAIN floods. Defences include DNSSEC, DoH or DoT, and monitoring for high-entropy subdomain queries.
4.What is ARP spoofing?
An attacker on the local segment answers ARP requests with their own MAC, so traffic for the gateway flows through them. Defend with dynamic ARP inspection, DHCP snooping and port security — and remember that TLS still protects the content even when the path is hijacked.
5.Difference between NAT and a firewall?
NAT translates addresses so many internal hosts share a public IP; it hides topology as a side effect but is not a security control. A firewall enforces policy. Candidates who call NAT a security feature get marked down.
6.What is a proxy and how does it help security?
It terminates and forwards traffic on behalf of clients, giving you URL filtering, TLS inspection, malware scanning and a central log of every outbound request. That log is often the most valuable investigation source in a breach.