802.1X is a network access control standard that ensures only authenticated devices can connect to a network, using certificates or credentials verified through a central authentication server.
802.1X Network Security
802.1X can eliminate a lot of issues on your network. I consider it the gold standard when it comes to security. It does not eliminate the need for all of the other things that we talked about, but it does make sure that only protected devices are connecting to your network.
The configurations of 802.1X are quite a bit more in-depth and beyond this course, but it is something that is pretty cool to implement on your networks.
802.1X makes sure that the devices connecting to your network should be on your network. Otherwise, it does not allow those devices to connect to your network. It is quite a few steps above and beyond what the standard port security does for us. The standard port security just does things based off of MAC addresses, and is fairly simplistic in its implementation. What this does, though, is make sure that this device, either by certificates or username and passwords, can connect to your network.
An example of this is, I have my demo laptop here, and this is called the supplicant. The supplicant is the device that is trying to connect to your network. You plug in the supplicant into a port, or perhaps you are connecting it wirelessly. Whatever the case may be, the device that you are connecting to, whether wireless or via some sort of physical port, that is known as the authenticator, and it is authenticating this device right here.
Now, what it will do is, this connection right here is going to be EAP, so it is going to create the secure connection between those devices as it is authenticating this. Then it is going to reach out to the authentication server, which is going to have information on this device.
Now, the way it authenticates could vary. You could have something like a certificate that is on the computer, or it could be a username and password that somebody on the supplicant has to enter in, that information, in order to get onto the network. Maybe it is like a captive portal, where a web page comes up and then you enter the information into that captive portal and that gets sent off to this authentication server.
So this authentication server is the one that gives the thumbs up or thumbs down based on the information that it is given. And then the authenticator, if the authentication server says yes, this device can get on, it will turn that port on and the supplicant is allowed to then be on the network. If the authentication server says no, this is not allowed, then the authenticator will turn off this supplicant's access to the network. So it is pretty secure.
The problem with this is that you do have to have usernames and passwords. Well, that is not the only way of doing it. You have to install possibly certificates on the computer. There has to be some sort of mechanism to verify the identity of this supplicant.
The other part of this is setting up this connection between the authenticator and this Demo Pi 2, or whatever device you have. This is going to use something like RADIUS to make that connection, and that type of connection needs to be set up, and there are some little gotchas while you are setting this up to make this all happen.
So there is a little more in-depth into setting this up, but once you have it set up, it really locks down so only certain devices are allowed on.
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 →