Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
EAP is the container that carries an authentication method across a network link. EAP-TLS is the method that fills it with mutual certificate authentication.

What Are EAP and EAP-TLS?
EAP is best understood as an envelope. The Extensible Authentication Protocol, defined in RFC 3748, does not authenticate anyone; it defines how an authentication conversation is carried between a client and a server across a link that has no IP addressing yet. What goes inside the envelope is an EAP method, and there are dozens. The choice of method is where the security lives.
You meet EAP in three places: enterprise Wi-Fi, wired 802.1X port authentication, and mobile network authentication on Wi-Fi calling. In all three the pattern is the same—EAP travels between the client and the access device in EAPOL frames, and between the access device and the RADIUS server inside RADIUS attributes.
EAP-TLS, specified in RFC 5216 and updated for TLS 1.3 in RFC 9190, runs a full TLS handshake inside the EAP conversation. Both sides present certificates. The server proves it is the organisation’s authentication server; the client proves it is a device or user the organisation issued a certificate to.
The consequences are worth being precise about. No password exists in the exchange, so there is nothing to phish, spray, or crack offline. The identity is a certificate you issued, so revocation is immediate and centrally controlled. And because the client validates the server, a rogue access point cannot complete the handshake at all—it has no key for a certificate the client will trust.
The price is a certificate lifecycle. Every laptop, phone, tablet, meeting room display, and handheld scanner needs enrolment, renewal before expiry, and revocation on loss. Mobile device management handles this well for managed devices and poorly for everything else, which is why organisations keep a second method for the long tail.
PEAP and EAP-TTLS take a different approach: establish a TLS tunnel using a server certificate only, then run a simpler authentication inside it. PEAP with MSCHAPv2 is the configuration most UK organisations actually run, because it reuses the Active Directory password everyone already has.
| Method | Client credential | Server certificate | Main weakness |
|---|---|---|---|
| EAP-TLS | Certificate | Required | Lifecycle cost |
| PEAP-MSCHAPv2 | Password | Required | Client validation is often disabled |
| EAP-TTLS | Password or token | Required | Same, plus patchy native support |
| EAP-MD5 | Password hash | None | Obsolete; no mutual authentication |
| EAP-SIM / AKA | SIM credential | None | Depends on operator infrastructure |
The entire security of PEAP rests on one checkbox: does the client validate the server certificate, and is it pinned to a specific certificate authority and server name? If that is off—and on unmanaged devices, Android profiles configured by hand, and anything a user set up themselves, it frequently is—then the client will establish a tunnel with any server that offers a certificate.
An attacker exploits this with a laptop, a Wi-Fi adapter, and hostapd-wpe or eaphammer. They broadcast the corporate SSID, the client associates, the tunnel forms with the attacker’s certificate, and MSCHAPv2 runs inside it. The attacker now holds a challenge-response pair derived from the user’s domain password, crackable offline. MSCHAPv2’s weakness here is structural: its DES-based construction reduces to a single DES key brute force, which commercial services complete in under a day for any password.
What makes this worse is that the stolen credential is a domain password, not a Wi-Fi password, so it unlocks VPN, email, and anything else that trusts the directory. Any wireless assessment worth commissioning includes this test.
EAP-TLS pairs naturally with device-bound credentials elsewhere in the estate, including FIDO2 for application sign-in and machine identity for workloads. The common thread is the same: a private key that never travels is a better credential than a secret that does.
At Privia Security, we test wireless and wired authentication, including rogue RADIUS attacks, as part of our network security services.
A framework. EAP defines the message format and the conversation structure, but the actual authentication is performed by an EAP method carried inside it, such as EAP-TLS, PEAP, or EAP-TTLS. Saying a network uses EAP therefore tells you almost nothing about its security; the method and its client configuration are what matter.
The method itself is acceptable only while the client validates the server certificate. When that validation is disabled or misconfigured, an attacker can impersonate the authentication server, capture an MSCHAPv2 challenge-response pair, and recover the password offline. MSCHAPv2’s construction reduces to a single DES key search, which commercial cracking services complete quickly regardless of password strength.
A certificate authority you control, a way to enrol every device that needs network access, automated renewal before expiry, and working revocation. Mobile device management covers managed laptops and phones well. The hard part is usually the long tail: printers, scanners, meeting room equipment, and contractor devices, which often end up on a separate network instead.
In tunnelled methods the identity sent before the TLS tunnel is established is visible to anyone listening. Setting the outer identity to a placeholder such as [email protected] means only the realm is exposed, while the real username travels inside the encrypted tunnel. It costs nothing and removes a free username enumeration opportunity from anyone sitting in the car park.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.