Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

5.4.1. Remote Access: VPN, ZTNA, and Jump Servers

💡 First Principle: Network attacks exploit specific protocol weaknesses, architectural assumptions, or configuration errors. Each attack exploits something that the protocol designers assumed would be trustworthy. ARP assumes any device can claim any IP-to-MAC mapping. DNS assumes recursive resolvers will accept authoritative answers. TCP assumes both endpoints want a connection. Understanding the assumption being exploited is the key to understanding both the attack and its defense.

DoS and DDoS:
Attack TypeMechanismDefense
SYN floodSends massive SYN packets, exhausting server half-open connection tableSYN cookies (server encodes state in ISN, doesn't allocate until ACK); rate limiting
Smurf attackICMP echo requests to broadcast with spoofed source = victim; all hosts reply to victimDisable directed broadcasts (ip directed-broadcast off on routers)
Fraggle attackSame as Smurf but using UDP echoDisable UDP echo; disable directed broadcasts
Ping of DeathOversized ICMP packets that overflow buffersModern OSes patched; historical
HTTP floodHigh volume of legitimate-looking HTTP requestsWAF rate limiting; CAPTCHA; behavioral analysis
Amplification DDoSSmall request → large response; spoofed source IP floods victim (DNS, NTP, SSDP, Memcached)Source address validation (BCP38); rate limit amplifiable services
Volumetric DDoSSaturate bandwidth with raw traffic volumeUpstream scrubbing center; CDN; anycast routing
Man-in-the-Middle (MITM):
AttackSetupTargetDefense
ARP spoofingPoison ARP tables to claim gateway MACLocal network segmentDynamic ARP Inspection (DAI); 802.1X; static ARP entries
DNS spoofingPoison DNS cache with false recordsDNS resolutionDNSSEC; DoH/DoT
SSL strippingDowngrade HTTPS to HTTP by intercepting redirectHTTPS connectionsHSTS (force HTTPS even without redirect); HSTS preloading
BGPM hijackingAdvertise more specific routes to intercept trafficInternet routingRPKI; BGPsec
Session hijackingSteal authenticated session tokenApplication sessionSecure cookie flags (HttpOnly, Secure, SameSite); short token lifetime
Password attacks:
AttackMethodTargetDefense
Brute forceTry all combinationsShort/simple passwordsAccount lockout; MFA; strong password policy
Dictionary attackTry common words/passwordsWeak passwordsSame as above + password manager
Rainbow tablePre-computed hash→password lookupsUnsalted hashesSalted hashes (bcrypt, Argon2, scrypt)
Credential stuffingUse breached credential lists on other sitesPassword reuseMFA; breach detection; unique passwords
Password sprayingTry common passwords against many accountsLockout evasionBehavioral analytics; alert on distributed low-volume attempts

Injection attacks: SQL injection, command injection, LDAP injection — all exploit insufficient input validation. Defense: parameterized queries, input validation, output encoding, least-privilege database accounts. Covered in detail in Domain 8 (Phase 9).

⚠️ Exam Trap: Rainbow table attacks are defeated by salting — adding a unique random value to each password before hashing. This means two users with the same password have different hashes. Rainbow tables precompute hash-to-password mappings; with a unique salt, a separate rainbow table would need to be computed for each salt value — computationally infeasible. Simply using SHA-256 instead of MD5 does NOT defeat rainbow tables; salting does.

Reflection Question: An attacker captures the password hash file from a compromised server. The file contains SHA-256 hashes without salts. The attacker cracks 40% of passwords in two hours using a rainbow table. A second server uses bcrypt with a per-user salt. Why would the attacker's rainbow table approach fail against the bcrypt server, and what is the attacker's best remaining option against the bcrypt hashes?

Alvin Varughese
Written byAlvin Varughese
Founder15 professional certifications