RADIUS Events Logs: How to View and Access Them

RADIUS servers are often called AAA (authentication, authorization and accounting) servers because they perform each of those three functions. A RADIUS server handles accounting – the process of tracking events as they occur – by generating event logs. RADIUS logs contain detailed information on the clients accessing your network. Checking those logs should be one […]

Track connectivity issues, failure, and error codes in real time.
Key Points
  • RADIUS functions as an AAA (Authentication, Authorization, and Accounting) server. Its Accounting component generates event logs that track connection requests, authentication success rates, and other key network data.
  • RADIUS event logs play a vital role in audit compliance, troubleshooting authentication failures, managing Wi-Fi and VPN connectivity issues, and monitoring devices and users' access to your network.
  • You can easily view events with SecureW2's CloudRADIUS or stream Accounting logs to existing infrastructure.

RADIUS servers are often called AAA (authentication, authorization and accounting) servers because they perform each of those three functions. A RADIUS server handles accounting – the process of tracking events as they occur – by generating event logs.

RADIUS logs contain detailed information on the clients accessing your network. Checking those logs should be one of your first steps when troubleshooting network connectivity issues or investigating suspected unauthorized network access. In this blog, we’ll show you exactly where to find RADIUS event logs, and why they’re important.

What are RADIUS Event Logs?

RADIUS servers can be configured to perform event logging, an in-depth record of events related to connection requests from RADIUS clients. These event logs can vary in detail, but they will often include the device, OS, user, whether the authentication was successful or failed, and error messages related to the authentication attempt.

Logs can be generated every time a RADIUS client attempts to authenticate to your network or VPN. They’re a great starting point for determining the root cause of Wi-Fi connectivity issues, or for meeting compliance requirements from auditing or regulatory authorities.

RADIUS Event Log Use Cases

Keeping event logs and regularly auditing them is necessary for modern cybersecurity. RADIUS event logs can be and are used for a variety of purposes, including:

  • Compliance audits
  • Troubleshooting authentication issues
  • Troubleshooting Wi-Fi and VPN connectivity problems
  • Tracking the devices accessing your network
  • SIEM or Syslog alarms

You can use event logs whenever you need to troubleshoot connection issues for a particular user or device. You can also import them to any Security Information and Event Management (SIEM) software you use, so you can be alerted right away when connection issues arise. In this way, they can serve as an early warning system for network authentication issues.

Finding Logs From Different RADIUS Servers

The steps for accessing RADIUS logs are slightly different, depending on which RADIUS server you use.

Network Policy Server (NPS) Logs

Network Policy Server (NPS) Server Manager Logs location
Source: Virtualization How To

Source: Virtualization How To

Network Policy Server (NPS) is Microsoft’s implementation of RADIUS. Network Policy Server logs can be viewed using Windows Server Manager or Windows Event Viewer UI (another system, part of the larger Windows Server package). You must decide whether you want to log RADIUS client authentication and accounting information to text log files stored on the local computer or to a SQL Server database on either the local computer or a remote computer.

Like with other RADIUS servers, NPS event logs contain authentication results and the reason for any failed authentication attempts.

NPS is only suitable as an addition to an existing Windows Server in most environments. Its logs may not be as detailed as other RADIUS server logs; sometimes they are missing accurate reasons for connection failures, like when users type in wrong passwords.

NPS and Active Directory (AD) are generally tied to on-premises infrastructure, as well. This means that NPS may not be a suitable choice for organizations looking for cloud-based identity management and access control solutions, such as Azure AD (Microsoft Entra ID) or similar.

FreeRADIUS Logs

FreeRADIUS is an open-source RADIUS server free for download and use. It can run on Unix-based platforms.

By default, FreeRADIUS stores accounting information in /var/log/freeradius of the Unix platform, but accessing these logs takes some technical expertise.

source: NXLog Docs

Where Do I Find Cloud RADIUS Event Logs?

Screenshot of Cloud RADIUS Event log entry with sample error codes

Cloud RADIUS, unlike an NPS server, is a managed and cloud-based platform that can be configured and deployed to any location. It also captures detailed logs for every network connection request and provides extensive information in addition to ACCESS_ACCEPT and ACCESS_REJECT responses.

You can easily find this information in the SecureW2 management portal by navigating to Data & Management and then selecting the RADIUS Events option.

Cloud RADIUS Event Log Fields and Meanings

Cloud RADIUS event logs were designed to provide administrators a clear snapshot of each authentication attempt. As such, we’ve incorporated numerous fields in them, including the following:

Region: Origin of the connection request.
Timestamp: Recorded time of the connection request.
Identity: Username used during the authentication.
Subject/Common Name: Name of the user using the certificate or token.
User Principal Name: Email ID of the user trying to connect to the network.
Device: Information related to the device such as a serial number.
Certificate serial: Serial number of the device’s certificate trying to connect to the network.
MAC Address: Media Access Control Address of the device trying to connect to the network.
Client Public IP: IPv4 address of the device, needed for the network to reach the device.
Operating System: Software that supports the device trying to connect to the network.
User Role: The user role designated by the administrator that the user belongs to.
Network Policy: This shows the network policy that applies to the user.
RADIUS Reply: Status of the RADIUS Authentication (ACCESS_ACCEPT/ACCESS_REJECT)
Error Message: If applicable, the reason why the remote access authentication attempt failed.

Cloud RADIUS Event Log Search Filters

Cloud RADIUS Event Log Search filters

RADIUS logs are a great tool for troubleshooting when you start getting reports that users can’t connect to your network. Granular search filters make it simpler to access them, which is why Cloud RADIUS includes a range of search settings.

Narrow your search by checking a specific user, for example, when only a single person is experiencing connectivity issues. You can also search by operating system, MAC address, and more.

Detailed and Easily Accessible RADIUS Logs with Cloud RADIUS

Event logs serve many purposes: they can be your first line of defense when an unauthorized party accesses your network, they can help you rapidly pinpoint the root cause of network connectivity problems, and they may be required for compliance reasons. Being able to quickly access and read RADIUS records is crucial.

Cloud RADIUS event logs streamline this process. Every authentication attempt is recorded in a detailed entry that provides administrators enhanced visibility. Additionally, granular search filters make it a simple matter to find the exact entry you need when you need it. Organizations using the SecureW2 Cloud RADIUS can view events from the management portal and export data to a SIEM provider to receive notifications in the event of connectivity issues.

We have affordable solutions for organizations of every size. Request a demo to see how Cloud RADIUS could work in your environment.


Frequently Asked Questions

How do I check the RADIUS logs?

You can check RADIUS logs through your RADIUS server platform or operating system event viewer. For example, FreeRADIUS typically logs to /var/log/freeradius/, while Microsoft NPS logs to the Windows Event Viewer. Many RADIUS platforms also store logs in text files or centralized SIEM platforms for easier monitoring and troubleshooting.

What are RADIUS event logs used for?

RADIUS event logs help administrators monitor authentication attempts, troubleshoot failed logins, verify policy enforcement, and track user or device access activity. They are also commonly used for compliance audits and security investigations.

Is RADIUS the same as LDAP?

No, RADIUS and LDAP serve different purposes. RADIUS is primarily used for network authentication and access control, while LDAP is a directory access protocol used to store and retrieve user and device information. In many environments, RADIUS servers integrate with LDAP directories like Active Directory to validate credentials. For more information about how LDAP can work with RADIUS, see our LDAP explainer.

What is the purpose of a RADIUS?

A RADIUS server manages authentication, authorization, and accounting (AAA) for network access. It verifies user or device identities before granting access to wired, wireless, or VPN networks and can also log connection activity for auditing and troubleshooting purposes.

What is the difference between authentication and accounting in RADIUS?

Authentication verifies a user or device identity before granting network access, while accounting tracks session activity after access is granted. Together, these functions help organizations secure and monitor network access effectively.