AAA (Triple-A) — Authentication, Authorization, Accounting
Every secure network answers three questions about every user and device: Who are you? What may you do? and What did you do? Those three questions are Authentication, Authorization, and Accounting. This lesson defines each A, contrasts local and server-based methods, and pins down the canonical ports: RADIUS UDP 1812/1813 and TACACS+ TCP 49.
The three A’s
AAA (pronounced “triple-A”) is the framework for controlling access to network devices and services. It answers three separate questions, each with its own job.
- Authentication — who are you? Proving identity with a password, certificate, token, or biometric.
- Authorization — what are you allowed to do? The permissions, privilege level, and commands you may use after you are authenticated.
- Accounting — what did you do? Logging and metrics: who logged in, when, from where, what they ran, and when they left.
The order matters: authentication happens first, authorization is applied to the identity that was
proven, and accounting records everything afterwards. A user can be authenticated and still be
unauthorized for a particular command — if a help-desk technician logs in successfully but may
not run configure terminal, the authentication succeeded and the authorization failed.
Local or server-based authentication
AAA can be administered in two fundamentally different ways, and real deployments use both: the device points to an external server for the normal case and keeps a local fallback for when the server is unreachable.
| Method | Where credentials live | Strengths | Limits |
|---|---|---|---|
| Local | On the device itself (username … password … in the IOS config). | Simple, no external server, always available. | Must be configured on every device; does not scale; hard to audit centrally. |
| Server-based | On a central AAA server (RADIUS or TACACS+). | One place to manage users, privileges, and logs; scales to many devices. | Depends on reachability of the server; needs a fallback. |
group radius local
lists methods left to right. The device tries RADIUS, and only if it gets no response does it try the
local database. If you wrote local group radius the device would check its own database
first — usually the opposite of what you want when central management is the goal.RADIUS and TACACS+
RADIUS (Remote Authentication Dial-In User Service) is an open, standards-based AAA protocol defined in RFC 2865 (with accounting in RFC 2866). It is the most widely supported AAA protocol and is used for network access — VPNs, wireless (802.1X), dial-in, and device administration.
| Feature | RADIUS | TACACS+ |
|---|---|---|
| Transport | UDP | TCP |
| Port(s) | 1812 auth, 1813 accounting | 49 (all functions) |
| Standard | Open (RFC 2865 / 2866) | Cisco (TACACS+ draft) |
| Auth + authorization | Combined | Separated |
| Encryption | Password field only | Entire packet body |
| Per-command authorization | Limited | Yes — granular |
| Typical use | Network access: VPN, 802.1X, dial-in | Device administration (router/switch login) |
TACACS+ (Terminal Access Controller Access-Control System Plus) is a Cisco AAA protocol used mainly to control administrative access to network devices. It separates the three functions, so a device can use different servers or methods for each; it encrypts the entire packet body; and it supports granular, per-command authorization — ideal for device administration where you must control exactly which commands each admin may run.
Configuring IOS AAA with RADIUS
On a Cisco IOS device, AAA must be enabled before any method list takes effect. The
sequence below enables AAA, defines a RADIUS server named RADIUS-1 at
192.168.1.10, sets the shared secret, and applies a method list for login.
| Command | What it does |
|---|---|
aaa new-model | Enables the AAA access-control model globally. Without it, AAA commands are rejected. |
radius server RADIUS-1 | Names a RADIUS server definition so it can be referenced by a group. |
address ipv4 … auth-port 1812 acct-port 1813 | Sets the server’s address and the canonical authentication and accounting ports. |
key cisco-1 | The shared secret used to encrypt traffic between the device and the server (must match on both). |
aaa authentication login default group radius local | For login, try the RADIUS group first, then fall back to the local database if the server is unreachable. |
aaa new-model (or the AAA commands are rejected); Step 2 define the
server with radius server, its address and the canonical ports, and the
key; Step 3 apply the method list with
aaa authentication login default group radius local. Forgetting the method list is the
most common miss — the server is defined but never consulted.802.1X and network admission control
802.1X is an IEEE standard for port-based network access control. Its rule is simple: a device may not pass traffic on a switch port (or wireless link) until it has authenticated. It is the technical foundation of Network Admission Control (NAC), which asks not only who is connecting but whether the device is healthy (patched, compliant) before granting access.
- Supplicant — the client device (laptop, phone, IP phone). It requests access and presents credentials (via EAP).
- Authenticator — the switch or wireless access point the client plugs into. It controls the physical port, relays EAP messages, and stays closed until authentication succeeds.
- Authentication server — the central RADIUS server. It holds the credentials and makes the accept/reject decision; it runs the actual AAA.
The client speaks EAP (Extensible Authentication Protocol) to the switch using EAPoL (EAP over LAN); the switch relays those messages to the RADIUS server inside RADIUS packets. Notice the pattern: 802.1X provides the access control, and RADIUS provides the AAA behind it — which is why this standard belongs in the same lesson as the two protocols.
The canonical facts in one place
Reproduce this table from memory before the exam.
| Fact | Value |
|---|---|
| Authentication | Proves who you are |
| Authorization | Defines what you may do |
| Accounting | Records what you did |
| RADIUS transport and ports | UDP 1812 (authentication), UDP 1813 (accounting) |
| TACACS+ transport and port | TCP 49 |
| RADIUS encryption | Password field only |
| TACACS+ encryption | Entire packet body |
| Enable AAA on IOS | aaa new-model |
| Method-list fallback | group radius local (server first, local second) |
| 802.1X roles | Supplicant, authenticator, authentication server |
| 802.1X credentials protocol | EAP, carried as EAPoL and relayed inside RADIUS |
| Central AAA protocols | RADIUS (RFC 2865) and TACACS+ |
Review
Check what you have learned with these review questions.
Sources & references
- Rigney, C., Willens, S., Rubens, A. & Simpson, W. RFC 2865: Remote Authentication Dial In User Service (RADIUS) (2000). rfc-editor.org/rfc/rfc2865.
- Rigney, C. RFC 2866: RADIUS Accounting (2000). rfc-editor.org/rfc/rfc2866.
- Cisco. TACACS+ Configuration Guide (TACACS+ uses TCP port 49; encrypts the entire packet body; separates AAA functions). cisco.com.
- Cisco. AAA: Authentication, Authorization, and Accounting (IOS configuration guide) —
aaa new-model,radius server, and method lists. cisco.com. - IEEE. IEEE 802.1X: Port-Based Network Access Control. standards.ieee.org.
- IANA. Service Name and Transport Protocol Port Number Registry (RADIUS 1812/1813, TACACS 49). iana.org.
- Cisco. CCNA (200-301) Exam Topics, Security Fundamentals, and CyberOps Associate (200-201) Exam Topics, Security Concepts. cisco.com.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.