Skip to content
-
Subscribe to our newsletter & never miss our best posts. Subscribe Now!
  • https://www.facebook.com/
  • https://twitter.com/
  • https://t.me/
  • https://www.instagram.com/
  • https://youtube.com/
Cloud Security Tips Cloud Security Tips

What is cloud security

Cloud Security Tips Cloud Security Tips

What is cloud security

  • Home
  • About us
  • Contact us
  • Home
  • About us
  • Contact us
Subscribe
Close

Search

A laptop displaying a secure login screen with a blue shield icon, with a smartphone showing a multi-factor authentication code beside it, illustrating RADIUS network authentication
Security Tips

RADIUS Protocol: What It Is, How It Works and Why Networks Still Use It

By admin
November 12, 2026 8 Min Read
0

Every time you join a company Wi-Fi network, log in to a VPN, or sign in to a campus network, something has to decide whether you are who you claim to be. In most organisations, that decision is made by the RADIUS protocol. It is not new, it is not flashy, and most users never hear its name, yet it still sits behind a huge share of network authentication around the world.

The RADIUS protocol, short for Remote Authentication Dial-In User Service, is a networking protocol that provides centralised authentication, authorisation and accounting, known as AAA, for users who connect to a network. A network access server asks a central RADIUS server to check a username and password, the server answers accept or reject, and it can also record how long the session lasted. This guide explains what RADIUS is, how it works step by step, which ports and messages it uses, how it compares with TACACS+ and Diameter, and how to use it safely in 2026.

Table of Contents

Toggle
  • What Is the RADIUS Protocol?
  • How Does RADIUS Authentication Work?
  • RADIUS Ports, Packets and Attributes
  • RADIUS vs TACACS+ and Diameter
  • Where RADIUS Is Used Today
  • RADIUS Security Risks and How to Harden It
  • Frequently Asked Questions
    • What is RADIUS used for?
    • What port does RADIUS use?
    • Is RADIUS secure?
    • What is the difference between RADIUS and TACACS+?
    • Is RADIUS still used in 2026?
  • Conclusion

What Is the RADIUS Protocol?

RADIUS is a client-server protocol defined in RFC 2865 for authentication and authorisation and RFC 2866 for accounting. It was created in 1991 for dial-up access, when internet providers needed one place to check thousands of modem users, and it has survived because the basic idea is still sound: keep user credentials in one central place instead of copying them onto every switch, access point and VPN gateway.

In a RADIUS setup there are three main parts. The supplicant is the user or device trying to connect, for example a laptop joining Wi-Fi. The network access server, often called a NAS or authenticator, is the switch, wireless access point, VPN gateway or firewall that controls access to the network. The RADIUS server is the central authority, usually backed by a directory such as Active Directory or LDAP, that checks credentials and decides what the user is allowed to do.

That separation matters for security and administration. When an employee leaves, an administrator disables one account on the RADIUS server and that person loses Wi-Fi, VPN and wired network access at the same time. When a password changes, it changes in one place. Without central authentication, every device would need its own user list, and every change would have to be repeated dozens of times.

How Does RADIUS Authentication Work?

RADIUS authentication follows a simple request and response conversation. The user never talks to the RADIUS server directly. Instead, the network device in the middle passes the request on and enforces the answer.

  1. The user requests access. A laptop tries to join the corporate Wi-Fi network or a remote worker opens a VPN connection and enters a username and password.
  2. The NAS sends an Access-Request. The access point or VPN gateway bundles the username, the password, the device address and other details into a RADIUS Access-Request packet and sends it to the RADIUS server over UDP.
  3. The server checks the credentials. The RADIUS server looks up the user in its directory or database, checks the password, and checks any policy, such as the time of day, the user’s group, or whether the device is allowed on this network.
  4. The server replies. It sends back one of three main answers: Access-Accept, which allows the connection and may include extra details such as a VLAN to place the user in; Access-Reject, which blocks the connection; or Access-Challenge, which asks for more proof, for example a one-time code from an authenticator app.
  5. The NAS enforces the decision. On an accept, the access point lets the user onto the network, usually on the VLAN named in the reply. On a reject, it blocks access and usually shows a generic failure message.
  6. Accounting begins. If accounting is enabled, the NAS sends Accounting-Request packets when the session starts and stops, so the server can log who connected, from where, for how long, and how much data was used.

For Wi-Fi, this conversation usually runs inside the 802.1X framework with EAP, the Extensible Authentication Protocol. The access point forwards EAP messages between the laptop and the RADIUS server without understanding the password itself. That is why the same RADIUS server can serve Wi-Fi, wired 802.1X on office switches, VPN logins and administrative logins to network devices, all with one set of accounts.

RADIUS Ports, Packets and Attributes

RADIUS uses UDP, which is fast and simple, and it relies on a shared secret to protect packets. The server and each NAS share a secret string. The password in an Access-Request is hidden using that secret, and replies are signed with it, so a device that does not know the secret cannot forge a valid answer.

Purpose Official port (UDP) Older port (UDP)
Authentication 1812 1645
Accounting 1813 1646

Ports 1812 and 1813 are the official IANA-assigned ports. Ports 1645 and 1646 are the older, unofficial ports that some older equipment still uses by default, so firewall rules and server settings must match the port your equipment actually sends to. A common troubleshooting mistake is to open 1812 on the firewall while the access point is sending to 1645.

RADIUS packets carry attributes, also called attribute-value pairs. Common attributes include User-Name, User-Password, NAS-IP-Address, Service-Type, Framed-IP-Address, Session-Timeout and vendor-specific attributes, which let a vendor add its own settings such as a VLAN ID or a user role. The reply can therefore do more than say yes or no: it can place an employee on the staff VLAN, a guest on the guest VLAN, and a printer on a restricted VLAN, all from the same access point.

RADIUS vs TACACS+ and Diameter

RADIUS is often compared with two other AAA protocols. TACACS+, developed by Cisco, separates authentication, authorisation and accounting into different conversations, encrypts the whole packet body rather than just the password, and uses TCP instead of UDP. That separation gives finer control, especially for administrative logins to routers and switches, where you may want to allow one engineer to view settings and another to change them. RADIUS, by contrast, combines authentication and authorisation in one exchange, encrypts only the password, and uses UDP. It is simpler, widely supported by many vendors, and better suited to large numbers of end users.

Diameter is the intended successor to RADIUS, defined in RFC 6733. It uses TCP or SCTP, supports reliable delivery, better error handling, and stronger security, including TLS. In practice, Diameter is common in telecom networks, for example in mobile carrier authentication, while RADIUS remains dominant in enterprise Wi-Fi, wired networks and VPNs. Most organisations do not need to replace working RADIUS now, but they should know its limits and protect it properly.

Feature RADIUS TACACS+ Diameter
Transport UDP TCP TCP or SCTP
Encryption Password only Whole packet body TLS supported
AAA separation Combined Separate Separate
Typical use Wi-Fi, VPN, wired users Device administration Telecom networks

Where RADIUS Is Used Today

RADIUS is still the default choice in many places. In offices and schools, it powers 802.1X Wi-Fi and wired networks, so users sign in with their normal work account instead of a shared Wi-Fi password. In universities, the eduroam roaming service uses RADIUS so a student visiting another campus can join Wi-Fi with their home university login. Internet providers use it to authenticate broadband and dial-up customers and to record usage for billing.

It is also common for VPN authentication. When a remote worker connects, the VPN gateway sends the login to RADIUS, which can check the password and require a second factor. That is where multi-factor authentication makes a real difference: even if a password is stolen, an attacker still needs the second factor. RADIUS also works well with network access control, which checks a device’s health and identity before it is allowed onto the network and can place untrusted devices on a separate VLAN.

For remote access, RADIUS often sits behind a VPN gateway that encrypts the tunnel itself. To understand the tunnel, see our guide to what IPsec is and how IPsec VPNs work. The two technologies complement each other: IPsec protects the traffic, RADIUS decides who is allowed in.

RADIUS Security Risks and How to Harden It

RADIUS was designed in an era when networks were smaller and threats were simpler, so it has real weaknesses that need managing. The shared secret is the first one. If it is short, reused across all devices, or stored in plain text on a NAS, an attacker who obtains it can forge packets. Use a long, random secret of at least 22 characters, use a different secret for each NAS or group of NAS devices, and store it securely.

Second, RADIUS over UDP has no built-in encryption for most of the packet. Only the password is hidden, and other attributes, such as usernames, can be seen by anyone who can capture the traffic. Never send RADIUS across the public internet without protection. Keep the RADIUS server on a protected management network, allow only known NAS IP addresses to reach it, and use RadSec, which is RADIUS over TLS, when traffic must cross an untrusted network.

  • Use strong EAP methods. For Wi-Fi, prefer EAP-TLS with certificates, or PEAP with strong passwords, and avoid older methods such as PAP or EAP-MD5, which are easy to attack.
  • Require a second factor. Pair RADIUS with multi-factor authentication for VPN and administrative access, so a stolen password alone is not enough.
  • Patch and monitor. Keep the RADIUS server patched, log authentication failures and accounting records, and alert on unusual patterns such as many failed logins from one device.
  • Limit what a reply can do. Only return the attributes a user actually needs. A guest account should never receive a VLAN assignment for the finance network.
  • Use accounting. Accounting records help with troubleshooting and with investigating incidents, because they show who was connected, when, and from where.

A practical starting point for a small organisation is to run RADIUS on a dedicated server or a managed service, connect it to the existing user directory, enable 802.1X on Wi-Fi and wired ports, and test with a small group before rolling it out. Keep a fallback local account on critical switches so a RADIUS outage does not lock administrators out of the network.

Frequently Asked Questions

What is RADIUS used for?

RADIUS is used for centralised authentication, authorisation and accounting for network access. The most common uses are Wi-Fi and wired 802.1X authentication, VPN logins, broadband customer authentication, and administrative logins to network devices, all checked against one central server.

What port does RADIUS use?

RADIUS uses UDP port 1812 for authentication and UDP port 1813 for accounting. Older equipment may still use the unofficial ports 1645 for authentication and 1646 for accounting, so check your device settings and firewall rules before troubleshooting a connection failure.

Is RADIUS secure?

RADIUS can be secure when it is set up properly, but it is not secure by default. Use long, unique shared secrets, keep the server on a protected network, use strong EAP methods such as EAP-TLS, require multi-factor authentication for remote access, and use RadSec, which is RADIUS over TLS, when traffic crosses an untrusted network.

What is the difference between RADIUS and TACACS+?

RADIUS combines authentication and authorisation, encrypts only the password, and uses UDP, and it is mainly used for end-user network access. TACACS+ separates authentication, authorisation and accounting, encrypts the whole packet body, and uses TCP, and it is mainly used for administrative access to routers and switches.

Is RADIUS still used in 2026?

Yes. RADIUS is still widely used in 2026 for enterprise Wi-Fi, university networks including eduroam, VPN authentication and internet provider networks. Newer protocols such as Diameter exist, especially in telecom, but RADIUS remains the practical choice for most enterprise and campus networks because it is widely supported and well understood.

Conclusion

The RADIUS protocol is not the newest technology on a network, but it is one of the most useful. By keeping authentication in one central place, it makes Wi-Fi, VPN and wired access easier to manage, easier to audit, and easier to secure when it is configured with strong secrets, strong EAP methods and multi-factor authentication. If your organisation still relies on a shared Wi-Fi password on every access point, moving to RADIUS with 802.1X is one of the highest-value security upgrades you can make.

Author

admin

Follow Me
Other Articles
Magnifying glass inspecting red computer code for a hidden security flaw
Previous

What Is the EICAR Test File? How to Use It to Safely Test Your Antivirus

A glowing blue digital padlock inside a secure VPN tunnel arc over a network, illustrating how a VPN changes your IP address
Next

Does a VPN Change Your IP Address? Yes, and Here Is How It Works

No Comment! Be the first one.

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    Recent Posts

    • Compliance Risk Assessment: A Complete Guide for 2026
    • SX SFP Module: What It Is, How It Works, and When to Use It
    • Hotspot 2.0 (Wi-Fi Passpoint): What It Is and How It Works
    • Volume Boot Record (VBR): What It Is, How It Works, and How to Fix It
    • Can Website Owners See Who Visits Their Website? What They Can (and Cannot) See

    Recent Comments

    1. Compliance Risk Assessment: A Complete Guide for 2026 on ISO 27001 Compliance: What It Is, How to Get Certified, and How to Stay Compliant
    2. SX SFP Module: What It Is, How It Works & When to Use It on Network Access Control: What It Is, How It Works, Types and Examples
    3. Hotspot 2.0 (Wi-Fi Passpoint): What It Is & How It Works on WIPS: What Is a Wireless Intrusion Prevention System?
    4. Volume Boot Record (VBR): What It Is & How to Fix It on Hypervisor: What It Is, Types, Security Risks and How to Harden It
    5. Can Website Owners See Who Visits? What They See & Can't See on California Consumer Privacy Act (CCPA): What It Is, Your Rights, and How to Comply in 2026

    Archives

    • November 2026
    • October 2026
    • September 2026
    • August 2026
    • July 2026
    • June 2026
    • May 2026
    • February 2026

    Categories

    • Blog
    • Business
    • Security Tips
    • Tech
    • Travel
    • Uncategorized
    Copyright 2026 — Cloud Security Tips. All rights reserved. Blogsy WordPress Theme

    Powered by CookieAdmin
    Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
    None
    Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
    None
    Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
    None
    Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
    None
    Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
    None
    Powered by CookieAdmin