Security · 8 min read

RADIUS vs TACACS+: Differences, Ports and When to Use Each

RADIUS vs TACACS+ compared: transport and ports, encryption, how they separate authentication, authorization and accounting, command authorization, and which to use for network access and device administration.

Use RADIUS to control users and devices joining the network, and TACACS+ to control administrators managing network devices. RADIUS runs over UDP, hides only the password and combines authentication with authorization. TACACS+ runs over TCP, obfuscates the whole packet and separates authentication, authorization and accounting, so it can approve each command an administrator types.

RADIUS vs TACACS+ at a glance

RADIUSTACACS+
StandardIETF RFC 2865 (authentication), RFC 2866 (accounting)RFC 8907 (2020, documents the protocol as deployed)
Transport and portsUDP 1812 auth, 1813 accounting (legacy 1645/1646); CoA on UDP 3799TCP 49
What is protectedOnly the User-Password attribute is hiddenThe entire packet body is obfuscated
AAA functionsAuthentication and authorization combined in one replyAuthentication, authorization and accounting fully separate
Command authorizationNo (privilege level only)Yes, each command can be permitted or denied
EAP / 802.1X supportYes, the standard for 802.1X and enterprise Wi-FiNo
Accounting detailSessions, time and bytes for network accessEvery command an administrator runs
Best forNetwork access: wired 802.1X, Wi-Fi, VPN, guest portalsDevice administration: switches, routers, firewalls

Why RADIUS dominates network access

RADIUS carries EAP, the protocol family behind 802.1X and WPA2/WPA3-Enterprise. Every enterprise access point, switch and VPN gateway supports it. It returns VLANs and policies in its reply, and with Change of Authorization (RFC 5176) it can move a device to another VLAN mid-session. See our dynamic VLAN and CoA tutorial.

Why TACACS+ dominates device administration

Because TACACS+ separates authorization, the server can approve show commands for the NOC while denying configure commands, and it logs each command for audit. That is exactly what change control and least privilege require. Follow the TACACS+ setup tutorial.

Security of each protocol in 2026

  • RADIUS/UDP uses MD5-based integrity. The 2024 Blast-RADIUS attack showed forged accepts are possible without Message-Authenticator. Patch servers, require Message-Authenticator and use RADIUS over TLS (RadSec, TCP 2083) between sites.
  • TACACS+ body obfuscation is also MD5-based. RFC 8907 states it does not provide strong security, so keep TACACS+ on an isolated management network or inside an encrypted tunnel.

Can I use both?

Yes, and most enterprises do. Many policy servers speak both protocols against the same user directory. Users and devices use RADIUS, and administrators use TACACS+.

What about Diameter?

Diameter (RFC 6733) was designed as RADIUS's successor for mobile operators. It runs over TCP or SCTP on port 3868 and is used in 4G/5G core networks, rarely in enterprise LANs.

FAQ

Frequently asked questions

What port does TACACS+ use?

TCP port 49.

What ports does RADIUS use?

UDP 1812 for authentication and 1813 for accounting. Older systems use 1645 and 1646. Change of Authorization uses UDP 3799, and RADIUS over TLS (RadSec) uses TCP 2083.

Which is more secure, RADIUS or TACACS+?

TACACS+ protects the whole packet body while RADIUS hides only the password, but both rely on MD5-based protection. Run either inside a protected management network or encrypted transport.

Can RADIUS do command authorization?

Not per command. RADIUS can return a privilege level or role, but only TACACS+ approves each command separately.

Is TACACS+ a Cisco protocol?

It originated at Cisco, but it is documented by the IETF in RFC 8907 and supported by most network and firewall vendors.

Need help designing your network?

Navijin engineers provide free design consultations, bills of materials and quotations for business projects.