Course contentsShow
← Security
Lesson 544 of 3,05212. Network Security - WirelessFree lesson

RADIUS Server Configuration and Security

Configure RADIUS authentication servers with proper secret management, encryption, and redundancy.

RADIUS Server Configuration and Security

What You'll Learn

You'll learn how to properly configure and secure a RADIUS authentication server to safely manage wireless network access without exposing credentials or creating single points of failure.

What Is RADIUS Server Security?

When you deployed 802.1X, EAP-TLS, or PEAP in previous lessons, there was always a RADIUS server behind the scenes making authentication decisions. Think of RADIUS (Remote Authentication Dial-In User Service) as the gatekeeper that your access points consult before letting anyone onto your network.

But if your gatekeeper is poorly configured, attackers can steal credentials, perform man-in-the-middle attacks, or bring down your entire wireless authentication system.

Core Security Principles

Secret Management

The shared secret between your access point and RADIUS server is like a password protecting their conversation. Use strong, randomly generated secrets (minimum 32 characters), never reuse them across multiple APs, and rotate them periodically. Weak secrets can be brute-forced if attackers capture RADIUS traffic.

Encryption in Transit

RADIUS wasn't designed with modern encryption standards. Only the password field is encrypted (using the shared secret). Use RadSec (RADIUS over TLS) whenever possible to encrypt the entire RADIUS session, protecting usernames, attributes, and metadata.

Server Redundancy

A single RADIUS server is a single point of failure. Deploy at least two servers in active-passive or active-active configuration. Clients should automatically fail over if the primary server becomes unreachable, ensuring authentication continues during outages or attacks.

Additional Hardening

  • Restrict RADIUS server access to only authorized access points by IP address
  • Enable detailed logging for audit trails
  • Use certificate-based authentication between RADIUS clients and servers
  • Keep software patched and updated

Key Takeaway: A secure RADIUS deployment requires strong shared secrets, encrypted communication channels (preferably RadSec), redundant server architecture, and strict access controls—treat it as critical infrastructure for your wireless security.