RADIUS vs TACACS+ for Network Access
Choosing between RADIUS and TACACS+ affects how users connect to a network and how administrators control network devices. Both protocols support centralized authentication, authorization, and acco…
Choosing between RADIUS and TACACS+ affects how users connect to a network and how administrators control network devices. Both protocols support centralized authentication, authorization, and accounting (AAA), but they handle those functions differently and suit different access scenarios.
For most organizations, the choice is not simply one protocol or the other. RADIUS commonly supports user and device access to services such as Wi-Fi, VPNs, and 802.1X. TACACS+ is often used to manage administrator access to routers, switches, and firewalls. Understanding the differences helps you design network access that is easier to control, audit, and maintain.
What are RADIUS and TACACS+?
RADIUS (Remote Authentication Dial-In User Service) is a protocol for communicating between a network access server and a centralized AAA service. A wireless access point, VPN gateway, or switch can ask a RADIUS server to validate credentials and return access-related attributes. RADIUS is specified in RFC 2865, with accounting described in RFC 2866 and subsequent updates.
TACACS+ (Terminal Access Controller Access-Control System Plus) is another AAA protocol, commonly used to control administrative access to network infrastructure. It is described in RFC 8907 and is widely implemented by network equipment vendors.
In both cases, a device acting as an AAA client sends requests to an AAA server. The client is typically a network device or service—not the end user’s computer. The server checks the request against configured policies and, when appropriate, returns a decision or attributes.
RADIUS vs TACACS+: key differences
| Consideration | RADIUS | TACACS+ |
|---|---|---|
| Common use | User and device access to Wi-Fi, VPN, and wired 802.1X networks | Administrative access to network devices |
| Transport | Traditionally UDP; commonly uses ports 1812 for authentication and 1813 for accounting | TCP, commonly port 49 |
| AAA behavior | Authentication and authorization are closely coupled in the access exchange; accounting is separate | Authentication, authorization, and accounting are distinct functions |
| Authorization detail | Returns attributes that services interpret, such as VLAN or session settings | Can support granular, device-specific command authorization, depending on implementation |
| Traditional protocol protection | Protects the password attribute with an MD5-based mechanism; other packet attributes are not generally encrypted | Encrypts the packet body using a legacy mechanism; the header is not encrypted |
| Secure transport options | RADIUS over TLS (RadSec) is available where supported | Support and security properties vary by implementation; do not assume the protocol’s legacy encryption provides modern transport security |
Port numbers and capabilities can vary by configuration and product. Confirm supported modes and requirements in the documentation for your AAA server and network devices.
Authentication, authorization, and accounting
AAA describes three related but distinct controls:
- Authentication verifies an identity, such as a user, device, or administrator.
- Authorization determines what that identity is allowed to do.
- Accounting records relevant session or activity information for auditing and operations.
RADIUS and TACACS+ can both participate in AAA, but they structure the exchange differently. With RADIUS, an access request and response commonly handle authentication and convey authorization attributes together. Accounting is typically sent in separate messages. For example, a RADIUS response might grant access while assigning a user to a particular VLAN.
TACACS+ separates authentication, authorization, and accounting more explicitly. In network-device management, a device can authenticate an administrator and then consult the server for authorization decisions about commands. Whether command-level controls are available—and how detailed they are—depends on the device and server implementation.
When RADIUS is a good fit
RADIUS is widely used when a service needs to make centralized access decisions for users or devices. Common examples include:
- Wi-Fi access: An access point or wireless controller can consult RADIUS to authenticate users and apply network policies.
- Wired 802.1X: A switch can use RADIUS as part of port-based access control, applying attributes such as a VLAN assignment when supported.
- VPN access: A VPN gateway can use a RADIUS service to authenticate users and receive authorization attributes.
- Network access control: RADIUS can carry policy information between supported infrastructure and an AAA service.
RADIUS is a practical choice when the main question is whether a user or device can connect to a network service and which session attributes should apply. Its broad adoption also means it is commonly supported across access points, switches, VPN systems, and identity platforms.
When TACACS+ is a good fit
TACACS+ is often selected for administrative access to network infrastructure. For example, an organization might use it to centralize administrator logins to switches and routers and, where supported, decide which commands each administrator can run.
That separation can help teams apply distinct policies for authentication, authorization, and accounting. It can also make administrative activity easier to review when the network equipment records useful command or session details and forwards them to an accounting service.
TACACS+ is not automatically more secure or more manageable in every environment. Its value depends on whether the infrastructure and AAA server support the authorization controls you need, and whether administrators can operate the service reliably.
Security considerations for both protocols
Neither protocol replaces good transport security, careful policy design, or secure operations. Consider these safeguards when planning RADIUS or TACACS+ network access:
1. Protect traffic between clients and servers. Traditional RADIUS does not encrypt every attribute in a packet. Where supported, consider RADIUS over TLS (RadSec), specified in RFC 6614, or an appropriately protected network path. TACACS+ encrypts its packet body using a legacy mechanism, but that should not be treated as equivalent to modern, comprehensive transport protection. Assess available secure transport options for your implementation.
2. Restrict who can contact the service. Use network controls to limit AAA traffic to authorized clients and servers. Avoid exposing AAA listeners to untrusted networks.
3. Use strong, unique shared secrets where applicable. Protect secrets in configuration files and management systems, rotate them according to your procedures, and avoid reusing them across unrelated clients.
4. Apply least privilege. Grant users and administrators only the access they require. For device administration, test command authorization carefully so that essential operations are neither accidentally blocked nor broadly permitted.
5. Plan for outages. Use redundant AAA services where appropriate and document what happens if they become unreachable. A local emergency account can support recovery, but tightly restrict it, monitor its use, and test the recovery process.
6. Record and protect logs. Accounting data can contain sensitive operational details. Limit access to logs, protect them from tampering, and retain them according to your organization’s requirements.
7. Test policy changes before broad deployment. A malformed rule or mismatched attribute can interrupt user connectivity or administrator access. Validate changes with representative devices and a recovery path.
How to choose between RADIUS and TACACS+
Use the access scenario—not protocol preference alone—to guide the decision:
1. Identify what is being accessed. For user or device access to Wi-Fi, wired 802.1X, or VPN services, start by evaluating RADIUS support. For administrative logins to network devices, evaluate TACACS+ if you need its authorization model and your equipment supports it.
2. Define the authorization decisions you need. If you need to return session attributes such as a VLAN assignment, check what RADIUS attributes your clients and server support. If administrators need command-level authorization, confirm that the network devices and AAA service implement the required TACACS+ controls.
3. Check compatibility and operational requirements. Review vendor support, identity-source integration, failover behavior, logging, and the ability to test policies safely. Protocol support alone does not guarantee that a specific feature will work end to end.
4. Assess transport protection. Compare the secure transport options available in your actual products. Consider what information is exposed in transit and how the path is protected.
5. Design for continuity and auditing. Decide how devices behave during an AAA outage, how emergency access is controlled, and whether the resulting accounting records are useful for investigations.
Many networks use both protocols for different purposes. For instance, a company can use RADIUS for employee Wi-Fi and wired network access while using TACACS+ for administrator access to switches and routers. This division is often more appropriate than forcing a single protocol to serve every use case.
Example design
Imagine a company with managed laptops, employee Wi-Fi, and a team that administers network switches. The wireless infrastructure can use RADIUS to authenticate users and apply supported network attributes. The switches can use TACACS+ for administrator logins and, if supported, command authorization and accounting.
The company should separately define behavior for AAA service outages. For example, it might use redundant servers for normal access and maintain a tightly controlled local recovery account on critical devices. The recovery account should be tested, monitored, and protected rather than treated as an undocumented bypass.
Common mistakes to avoid
- Treating the protocols as interchangeable: They overlap in AAA roles, but their message models and common use cases differ.
- Assuming RADIUS encrypts the entire packet: Traditional RADIUS protects the password attribute, not all packet contents. Evaluate transport protection for the deployment.
- Assuming TACACS+ guarantees command control: Fine-grained authorization depends on both the server and the network device implementation.
- Ignoring failure behavior: A centralized service can become a dependency. Test redundancy and recovery before an outage occurs.
- Using broad fallback access: Emergency access should not silently grant more privilege than normal policy allows.
FAQ
Is RADIUS or TACACS+ more secure?
Neither is universally more secure. Security depends on the implementation, transport protection, policy, network exposure, and operational controls. Traditional RADIUS does not encrypt all packet attributes, while TACACS+ uses legacy packet-body encryption that should not be mistaken for modern transport security. Compare supported protections in your environment.
Can RADIUS be used for administrator access to switches?
Yes. Many devices support RADIUS for administrative authentication. Whether it provides the authorization detail you need—especially for individual commands—depends on the device and server. Check those capabilities before choosing it for device administration.
Can TACACS+ authenticate Wi-Fi users?
TACACS+ is primarily associated with device administration, while RADIUS is broadly used for Wi-Fi and other network access services. Use the protocol supported by the access infrastructure and identity service, and verify that it meets the required authorization and accounting needs.
Do organizations need to choose only one protocol?
No. It is common to use RADIUS for user or device network access and TACACS+ for network-device administration. Separate deployments can serve different access policies, provided they are operated and monitored consistently.
Conclusion
RADIUS and TACACS+ both support centralized network AAA, but they serve different strengths. RADIUS is commonly suited to user and device connectivity across Wi-Fi, wired 802.1X, and VPN services. TACACS+ is often a strong candidate for managing administrator access to network equipment, especially when supported command authorization is important.
For a sound radius tacacs+ network access design, map each protocol to the access scenario it supports best, verify implementation details, protect AAA traffic, and plan for outages and audits. In many environments, using both is the clearest way to meet distinct access requirements.