Extensible Authentication Protocol (EAP) is a widely used authentication framework that defines how authentication protocols should be structured, enabling a flexible range of methods such as EAP-TLS, EAP-MD5, and EAP-FAST. It supports diverse credential types including certificates, pre-shared keys, and username-password combinations.
Extensible Authentication Protocol (EAP)
One of the most well-used authentication protocols nowadays is EAP, or extensible authentication protocol.
Authentication protocols is just a generic term that we use to describe all the protocols that are used to communicate between different devices, or users and devices, or users and certain resources, in order to gain access to it. So it's an authentication that happens, hence the authentication protocols, but it's the actual protocol that's being communicated back and forth.
There are a lot of authentication protocols. In fact, if you look at the Wikipedia article on authentication protocols, this is how it breaks it down. We've developed these authentication protocols over time. One of the initial ones was password authentication protocol, or PAP. This one had some real weaknesses to it, so CHAP came out, or challenge handshake protocol. And now one of the newer ones is extensible authentication protocol.
Although this is different than these other two. In fact, this is not a protocol at all. Despite what the name says, it's actually a framework.
What is this framework? Extensible authentication protocol is a framework. Think of a framework as being like the blueprints to the house, versus the protocol as being the house. What is a blueprint? A blueprint describes how the house should be constructed, and then the protocol actually constructs it. Same thing when it comes to these authentication protocols: EAP is just the framework. It specifies how these protocols should look, and then there are a lot of protocols that are built towards this EAP. You can think of it as maybe a standard, or this blueprint.
So what are the actual protocols then that are associated with EAP? We call these EAP methods. Some examples of these are EAP-TLS, or TLS. We've got EAP-MD5, EAP-FAST. So we've got different methods that are built off of the EAP framework.
There are a lot of EAP methods — here's a list of many of the EAP methods. So why are there so many? It just depends on what our use cases are. There are a lot of different use cases out there. Some of these are outdated, so we produce different ones. Like EAP-MD5 is considered an outdated one now. But maybe we want to use certificates — well, the TLS one will use certificates. Or maybe we want to use a one-time password — well, that's what this POTP one is. Or maybe we want to do a pre-shared key.
So that allows us to create this framework. EAP creates this framework that then we can build these standards off of, and now we can choose what standards we want to use, what protocols we want to use, depending on what our scenario is. It makes it much more dynamic when we're implementing these, and also it makes it much more dynamic from a progression standpoint, because we can upgrade these as technologies get old and we need to improve upon them.
What this allows us to do is, I can be on my laptop connecting into maybe a server or a service and I need to be authenticated. Well, maybe I want to have different methods available. So we discuss back and forth through these protocols and say, okay, what method are we going to use? Maybe we are going to use a pre-shared key, or maybe we're going to use a certificate, or maybe we're going to use some user credentials, in order to exchange this information and authenticate either the user or the device, or a service on this device, to the service or the resource that we're trying to access.
So this allows me to use those credentials by entering a username and password and gaining access to those resources, or using something like certificates. That certificate could be installed on the computer, so I would install a certificate on the computer and that grants me access to those resources. Or maybe it's a certificate on a smart card — so I've got a smart card, and then when I scan that, that certificate grants me access. So it's like a form of credentials; it's to me rather than the device itself. So it gives me a lot of variety from that perspective.
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →