AAA (Authentication, Authorization, and Accounting) is a security framework used to manage network access at scale through centralized authentication servers rather than local device databases. Common protocols implementing this model include TACACS+, RADIUS, and Diameter.
AAA Services
Many times we authenticate to a local database. What I mean by that is we make a connection to maybe a server, or maybe it's a router or firewall or switch, and we are using the local database for our credentials to log into that machine. But that's not always feasible, especially at scale. We probably want some sort of authentication server. Well, that's what AAA services do for us.
AAA stands for authentication, authorization and accounting. Authentication is verifying the identity. Authorization is determining what they should have access to. And accounting tracks and logs that information.
One thing to understand about AAA is there is a AAA model, that is this idea that there's authentication, authorization and accounting, and we want to implement that. Then there are specific protocols or services or servers that we can use to implement this model to make sure it's implemented on our network. So many times I find that the model doesn't necessarily always 100% apply to network protocols, that we can use it in other scenarios as a model for authentication, for identity and access management services. But there are some specific protocols that are associated with AAA.
Let's just use an example here. I'm on a laptop right here, and let's say I'm logging into a router right here and I'm sshing into it. I need to SSH into it because I need to perform some work on it. Well, what I'm going to do is I'm going to SSH onto it, and perhaps it has some sort of local database. We call it the local database, a set of usernames and passwords that I can use to log into this router. I do my work and I log off of it.
That's great if I just have one or two routers, but let's say I have a thousand routers. Now, for me to do that on each one of those devices, that would take a long time, to have a separate username and password on those. Now think, if let's say somebody got laid off or fired or has left the company, and I've got to visit a thousand of those routers to remove that username and passwords. You can see how that would be both a management and a security nightmare, because are you going to get it off of all of those routers? So it creates some vulnerabilities there.
Versus if I set up a separate database that does the authentication. Now I can have those credentials on this separate system right here, and then the router uses that separate system in order to give permission or deny permission. Now all of those thousand routers are on the same page, because they're using the same database server.
So not only do we have this AAA model, but we also have protocols, services and servers that go along with that. So in this example right here we have the authenticator with the authentication servers back here. So these are these servers. The servers are what are running the services, which is just the program that's providing these services, and the protocols is the communication that's happening between these devices right here.
So what are examples of these protocols and services that are associated with AAA? Well, one of them is TACACS, which is a Cisco proprietary one. We have RADIUS and we have Diameter. So there's just a few examples.
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 →