EAP-TTLS and PEAP Tunneled Methods
What You'll Learn
You'll understand how EAP-TTLS and PEAP create secure tunnels using only server certificates to protect simpler inner authentication methods.
The Problem They Solve
After learning about EAP-TLS (which requires certificates on both server and client), you might wonder: what if you want strong encryption without deploying certificates to every user device? That's where tunneled EAP methods come in.
How Tunneled Methods Work
Both EAP-TTLS (Tunneled Transport Layer Security) and PEAP (Protected EAP) use a two-phase approach:
Phase 1: Build the Tunnel
The authentication server presents its certificate to the client (like visiting an HTTPS website). This establishes an encrypted TLS tunnel. The client validates the server's identity, but the server doesn't yet know who the client is.
Phase 2: Inner Authentication
Once the tunnel is secure, the client sends credentials through it. These could be simple username/password pairs, tokens, or other EAP methods. Because they travel inside the encrypted tunnel, they're protected from eavesdropping.
Analogy: Think of it like whispering a password through a soundproof phone booth. The booth (tunnel) is verified as secure, then you safely share your secret inside.
EAP-TTLS vs PEAP
- EAP-TTLS: More flexible; can tunnel almost any authentication protocol (PAP, CHAP, MS-CHAPv2, even other EAP methods)
- PEAP: Microsoft-backed; typically tunnels EAP methods only (commonly EAP-MSCHAPv2 or EAP-GTC)
Both achieve the same goal: strong outer encryption with only a server certificate, allowing simpler inner credentials.
Key Takeaway: EAP-TTLS and PEAP create encrypted tunnels using server-side certificates only, protecting weak inner authentication methods from wireless eavesdropping—offering enterprise security without client certificate deployment overhead.