The final step in enterprise integration is knowing when to kill a protocol. In security, 'Legacy' is a synonym for 'Vulnerable.' Maintaining support for old protocols creates a 'Lowest Common Denominator' security posture.
WEP (Wired Equivalent Privacy) and PPTP (Point-to-Point Tunneling Protocol) are completely broken. WEP can be cracked in seconds using the RC4 weakness, and PPTP's MS-CHAPv2 is vulnerable to rapid offline cracking.
💡 If you find a device using WEP or PPTP in 2025, it is not a 'legacy system'—it is a critical security hole.
| Protocol | Why it's Dead | Replacement | Current Risk |
|---|---|---|---|
| SSL v2/v3 | POODLE / BEAST | TLS 1.2 / 1.3 | Critical |
| WEP | IV Reuse / RC4 | WPA3 | Critical |
| PPTP | Weak Handshake | IPsec / WireGuard | High |
| TLS 1.0/1.1 | Weak Ciphers | TLS 1.2 / 1.3 | Medium/High |
The transition from SSL → TLS → TLS 1.3 was driven by the discovery of flaws in how symmetric keys were derived and how padding was handled (e.g., the Lucky13 attack).
Many servers offer 'TLS Fallback.' If a client says 'I only support TLS 1.0,' the server agrees. An attacker can perform a 'Downgrade Attack' by intercepting the handshake and tricking both parties into using the weakest common protocol.
# Checking for deprecated protocols with nmap
nmap --script ssl-enum-ciphers -p 443 target.com
# Output will list:
TLSv1.0: [Ciphers...]
TLSv1.1: [Ciphers...]
TLSv1.2: [Ciphers...]The `ssl-enum-ciphers` script is the industry standard for identifying 'Legacy Debt.' Any result showing TLS 1.0 or 1.1 should be flagged as a vulnerability.
Removing legacy protocols is a political challenge, not just a technical one. It requires a phased approach to avoid breaking critical business functions.
The most common mistake is disabling a protocol on the server but forgetting it on the load balancer or WAF.
Verify exercises to earn ★ 150 XP and unlock next lab level.