Skip to content
Access

Secure network: certificates, identity and PasspointComparisons

Cloud NAC vs RADIUS: what you need for WiFi access control

You will be able to choose between on-premises RADIUS, cloud NAC and Purple cloud RADIUS for WiFi access control. The deciding test is simple: if your requirement is which person, on which device, gets which VLAN, cloud RADIUS with EAP-TLS covers it. Only mandated endpoint posture checks or wired switch port control...

13 min read

Watch the explainer

For most multi-site WiFi estates, the answer is cloud RADIUS, not cloud NAC. IEEE 802.1X with EAP-TLS certificates and identity from Microsoft Entra ID or Okta covers WiFi access control. RADIUS attributes set each VLAN on the access points you already own. Cloud NAC earns its cost only when you must check endpoint posture or control wired switch ports.

Do you need cloud NAC or cloud RADIUS for WiFi?

The terms get blurred, so define them first. RADIUS is the authentication protocol defined in RFC 2865. Your access points send it every connection request and act on the reply. IEEE 802.1X is the standard that makes a device prove its identity before it reaches the network. EAP-TLS, defined in RFC 5216, is the 802.1X method that uses a device certificate instead of a password.

Network access control (NAC) is a wider product category. A NAC platform runs RADIUS too, then adds endpoint posture checks, device profiling and remediation. Posture means a device's health, such as its patch level or antivirus status. Cloud NAC delivers that platform as a hosted service.

Our verdict: for WiFi access control across a multi-site estate, choose Purple cloud RADIUS. The verdict depends on one condition. Your requirement must be about which person and which device joins, and which VLAN (virtual LAN segment) they land on. If policy also demands a health check on each laptop or each wired switch port, the answer flips towards NAC.

Branch estates show where the line usually falls. JPMorgan runs staff WiFi on Purple across 5,000 branches. In a branch, store or hotel, the WiFi requirement is identity and segmentation, repeated at every site. That is a RADIUS job, and the cloud is the right place to run it.

{"items":[{"value":"80,000+","label":"live venues on Purple","note":"In 90 countries"},{"value":"99.9%","label":"RADIUS uptime SLA"},{"value":"99.999%","label":"Purple platform uptime"},{"value":"5,000","label":"JPMorgan branches on Purple staff WiFi"}]}

Which criteria decide cloud NAC vs RADIUS?

We compared three options on seven criteria. Each criterion changes the outcome for at least one type of estate. We scored each option from the standards and from each category's own public documentation, not from sales claims.

The three options are:

  • On-premises RADIUS: Microsoft Network Policy Server (NPS) or FreeRADIUS, running on servers you own.
  • Cloud NAC: a hosted NAC platform with RADIUS, posture, profiling and remediation.
  • Purple cloud RADIUS: the secure network in Purple Access, with EAP-TLS, identity integration and Passpoint.

Passpoint, also called Hotspot 2.0, lets a device join a trusted network automatically, with no captive portal. A captive portal is the web page a visitor sees before getting access.

The seven criteria are:

  1. Scope of control. WiFi only, or wired switch ports as well.
  2. Endpoint posture. Whether policy requires a device health check before or after access.
  3. Identity source. On-premises Active Directory, or a cloud identity provider (IdP) such as Microsoft Entra ID, Okta or Google Workspace.
  4. Hardware fit. Whether the option works across a mixed estate of access points with no new hardware.
  5. Segmentation. Whether identity sets the VLAN through standard RADIUS attributes.
  6. Availability and operations. Who patches, scales and fails over the service, and what the SLA covers.
  7. Audit evidence. What records you can hand an auditor for PCI DSS, ISO 27001 or GDPR.

We left out axes that never change the answer. All three options speak RADIUS and all three support 802.1X, so neither separates them.

How do cloud NAC and RADIUS compare side by side?

The matrix scores each option on the seven criteria, plus guest and headless devices. Read across the rows that match your requirement. The posture and scope rows decide most shortlists.

{"caption":"Cloud NAC vs RADIUS for WiFi access control","asOf":"2026-06-10","columns":[{"key":"c","label":"Criterion"},{"key":"onprem","label":"On-premises RADIUS"},{"key":"nac","label":"Cloud NAC"},{"key":"purple","label":"Purple cloud RADIUS","highlight":true}],"rows":[["Scope of control","WiFi and wired 802.1X","WiFi and wired ports","WiFi: open, secure and xPSK networks"],["Endpoint posture","Not included","Core feature, usually agent-based","Not in scope; access set by identity and certificate"],["Identity source","Active Directory or LDAP on site","Cloud IdPs on each vendor's integration list","Microsoft Entra ID, Okta, Google Workspace"],["Hardware fit","Any 802.1X access point or switch","802.1X access points and switches","Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, Fortinet"],["Segmentation","VLAN via RFC 3580 attributes you configure","VLAN plus quarantine after posture checks","Identity sets the VLAN at every site"],["Availability","Your build; you design failover","Vendor hosted; SLA set in each contract","99.9% RADIUS SLA on a 99.999% uptime platform"],["Operations","You patch, scale and renew server certificates","Vendor runs the service; you run agents and policy","Purple runs the service; no new hardware"],["Audit evidence","Logs you collect and retain","Logs in the vendor console","One console; Purple is ISO 27001 and Cyber Essentials certified"],["Guest and headless devices","Separate captive portal and MAC lists to build","Guest and profiling modules","Captive portal on the open network; a key per device on xPSK"]],"footnote":"Scored from RFC 2865, RFC 3580, IEEE 802.1X and each category's public documentation. Check your cloud NAC shortlist against these rows, as features differ by vendor.","download":{"filename":"cloud-nac-vs-radius-matrix.csv"}}

The VLAN row matters more than it looks. RFC 3580 defines the tunnel attributes RADIUS returns to place a device on a VLAN. All three options use it. The difference is who maintains the mapping, and whether it follows identity changes in your IdP.

Where do cloud NAC and RADIUS differ in practice?

Posture is where the answer flips

RADIUS answers two questions: who is this, and which VLAN do they get? NAC adds a third: is this device healthy? Answering it needs an agent or a scan on every endpoint. It also needs a way to move a device after it has joined. NAC uses RADIUS dynamic authorisation, known as CoA and defined in RFC 5176, for that move.

Test your policy wording. "No device on the corporate VLAN without current patches" is a posture requirement. "Only managed devices belonging to current staff" is an identity requirement. An EAP-TLS certificate issued through your MDM (mobile device management) platform already proves the device is managed. It also proves which person it belongs to.

Scope: WiFi access or every switch port

NAC's second strength is wired control. If audit scope includes 802.1X on every switch port in every back office, NAC or on-premises RADIUS covers both media. Purple's scope is WiFi: open, secure and xPSK networks on the access points you own. For branch, venue and campus estates, WiFi is where staff phones, laptops, scanners and tablets connect.

Identity: a directory on site or in the cloud

NPS authenticates against on-premises Active Directory. A cloud-only Microsoft Entra ID tenant leaves it with no directory to query, so domain controllers stay in place. Purple connects directly to Microsoft Entra ID, Okta and Google Workspace. Joiners, movers and leavers flow from your IdP into WiFi policy. Disable a leaver in the IdP and Purple revokes their WiFi access.

{"tone":"warning","title":"Password-based 802.1X is running out of road","text":"[Microsoft documents](https://learn.microsoft.com/en-us/windows/security/identity-protection/credential-guard/considerations-known-issues) that Credential Guard blocks MSCHAPv2-based single sign-on, which breaks saved credentials for PEAP-MSCHAPv2 networks. Plan the move to certificate-based EAP-TLS whichever option you choose."}

PEAP (Protected EAP) wraps a password exchange inside a TLS tunnel. It was the default for a decade on NPS estates. The Credential Guard change pushes you to certificates either way, so make EAP-TLS part of the decision rather than a later project.

Operations: who patches and who fails over

On-premises RADIUS puts every operational task on your team. That covers servers in at least two locations, operating system patches, RADIUS server certificate renewals and capacity for peak connection bursts. Our guide to FreeRADIUS vs cloud RADIUS breaks down that work line by line.

Cloud NAC and Purple both move the service off your servers. Purple runs the largest cloud RADIUS in the world, with a 99.9% RADIUS uptime SLA on a platform that runs at 99.999% uptime. For how regions, failover and the SLA work together, see cloud RADIUS high availability.

{"kind":"lanes","direction":"lr","caption":"Where each option sits between the access point and your identity source","alt":"Three lanes compare on-premises RADIUS, cloud NAC and Purple cloud RADIUS, each starting at an 802.1X access point and ending at an identity or posture source.","lanes":[{"id":"l1","label":"On-premises RADIUS"},{"id":"l2","label":"Cloud NAC"},{"id":"l3","label":"Purple cloud RADIUS"}],"nodes":[{"id":"a1","label":"Access point (802.1X)","sub":"SSID set to WPA2 or WPA3 Enterprise","lane":"l1","tone":"neutral"},{"id":"a2","label":"RADIUS servers you run","sub":"NPS or FreeRADIUS; you patch and fail over","lane":"l1","tone":"neutral"},{"id":"a3","label":"Active Directory on site","sub":"Domain controllers stay in place","lane":"l1","tone":"neutral"},{"id":"b1","label":"Access point or switch port","sub":"802.1X on WiFi and wired","lane":"l2","tone":"neutral"},{"id":"b2","label":"Hosted NAC service","sub":"RADIUS plus profiling and posture policy","lane":"l2","tone":"neutral"},{"id":"b3","label":"Endpoint agent","sub":"Reports device health; CoA moves failing devices","lane":"l2","tone":"neutral"},{"id":"c1","label":"Access point (802.1X)","sub":"Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi","lane":"l3","tone":"neutral"},{"id":"c2","label":"Purple cloud RADIUS","sub":"EAP-TLS; 99.9% RADIUS uptime SLA","lane":"l3","tone":"brand"},{"id":"c3","label":"Your identity provider","sub":"Microsoft Entra ID, Okta, Google Workspace","lane":"l3","tone":"success"}],"edges":[{"from":"a1","to":"a2","label":"RADIUS","style":"solid"},{"from":"a2","to":"a3","label":"Directory lookup","style":"solid"},{"from":"b1","to":"b2","label":"RADIUS","style":"solid"},{"from":"b3","to":"b2","label":"Posture","style":"dashed"},{"from":"c1","to":"c2","label":"RADIUS","style":"solid"},{"from":"c2","to":"c3","label":"Identity and groups","style":"solid"},{"from":"c2","to":"c1","label":"VLAN by identity","style":"dashed"}]}

Where does Purple fit in network access control for WiFi?

Purple Access runs three networks on one platform, on the access points you already own. Identity sets the VLAN on all three.

  • Secure network: EAP-TLS, cloud RADIUS, IdP integration and Passpoint for staff and managed devices.
  • xPSK network: a key per device or per resident for devices that cannot run 802.1X. xPSK covers iPSK and PPSK, the vendor terms for an individual pre-shared key.
  • Open network: captive portal access and BYOD onboarding for guests and visitors.

Purple is hardware-agnostic and works as a cloud overlay. In the Cisco Meraki dashboard, you set the SSID's association requirement to "Enterprise with my RADIUS server" and add Purple. In HPE Aruba Networking Central, Ruckus One or SmartZone, the Juniper Mist dashboard and the UniFi Network application, set WLAN security to WPA2 or WPA3 Enterprise. Then add Purple as the RADIUS server. Purple's setup guides give the exact steps for each console.

Guest marketing on the open network sits in Engage, and DNS filtering sits in Shield. Neither is needed for the access control decision in this guide. For the full design of certificates, identity and Passpoint, read the secure network guide.

{"title":"Which access control fits your estate","options":[{"name":"On-premises RADIUS","fitsWhen":["One site with Active Directory on servers you already run","A site that must authenticate with no internet path"],"notWhen":["Your directory has moved to Microsoft Entra ID, Okta or Google Workspace","You run many sites with no local IT"]},{"name":"Cloud NAC","fitsWhen":["Policy requires endpoint posture checks before access","Wired switch ports are in audit scope"],"notWhen":["Your requirement is WiFi access by identity","You cannot deploy agents to every endpoint"]},{"name":"Purple cloud RADIUS","fitsWhen":["Multi-site WiFi on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist or Ubiquiti UniFi","Identity in Microsoft Entra ID, Okta or Google Workspace","Staff, guests and headless devices on one platform","You want no RADIUS servers to run"],"notWhen":["Policy mandates device health checks on every wired port"]}],"recommendation":"For WiFi access control across a multi-site estate, choose Purple cloud RADIUS: EAP-TLS, identity-set VLANs and a 99.9% RADIUS uptime SLA, with no new hardware."}
{"tone":"proof","title":"JPMorgan, 5,000 branches","text":"JPMorgan runs staff WiFi on Purple across 5,000 branches. Purple runs the largest cloud RADIUS in the world and serves 80,000+ venues in 90 countries."}

What does each option cost to run?

Licence lines mislead in this comparison. The real cost sits in servers, failover, agents and engineering hours. The table compares the structure of each cost, not amounts.

{"caption":"Cost structure: what you pay for with each option","asOf":"2026-06-10","columns":[{"key":"line","label":"Cost line"},{"key":"onprem","label":"On-premises RADIUS"},{"key":"nac","label":"Cloud NAC"},{"key":"purple","label":"Purple cloud RADIUS","highlight":true}],"rows":[["Licence model","Free software (FreeRADIUS) or Windows Server licences (NPS)","Subscription, usually per endpoint or per device","Subscription"],["Infrastructure","Servers or VMs in at least two locations","No servers; agents on managed endpoints","No servers; runs on access points you own"],["High availability","You build, test and maintain failover","Covered by the vendor's contracted SLA","99.9% RADIUS uptime SLA included"],["Staff time","Patching, upgrades, capacity and log retention","Posture rules, agent rollout and policy","Identity mapping and policy"],["Growth","Add servers ahead of peak demand","Add endpoint licences as devices grow","Purple scales the service"],["Change cost","Server refresh cycle","Agent and switch configuration per site","RADIUS migration, usually a weekend"]],"footnote":"Structure only. Ask each vendor for a quote scoped to your sites and device counts.","download":{"filename":"cloud-nac-vs-radius-cost-structure.csv"}}

On-premises RADIUS looks cheapest on paper. FreeRADIUS is open source and NPS ships as a Windows Server role. Your costs arrive as hardware, a second site for failover and the hours an engineer spends keeping both healthy. A single lapsed server certificate can stop every 802.1X connection at once.

Cloud NAC moves the servers off your books. Per-endpoint pricing then grows with every phone, scanner and tablet you add. You also fund the agent rollout and the switch configuration that posture enforcement needs.

Purple cloud RADIUS removes the servers and the agents. You keep your access points, controllers and VLAN design. What remains for your team is policy: which groups map to which VLANs.

What does moving to Purple cloud RADIUS involve?

A RADIUS migration to Purple is usually a weekend exercise. The work is configuration, not hardware. A typical sequence runs like this:

  1. Inventory. List every SSID, its authentication method, its VLAN rules and every RADIUS client: access points or controllers.
  2. Connect identity. Link Microsoft Entra ID, Okta or Google Workspace to Purple, and map groups to VLANs.
  3. Pilot. Point one SSID at one site to Purple. Test each device type you run.
  4. Cut over. Change the RADIUS server on production SSIDs in your console, using configuration templates where your console offers them.
  5. Decommission. Keep the old server reachable through a short fallback window, then retire it.

Moving from NPS or FreeRADIUS

If you already run EAP-TLS, the swap is the five steps above. If you run PEAP-MSCHAPv2, treat the certificate rollout as a separate workstream. Your MDM platform issues device certificates, and the RADIUS change can happen before or after. Splitting the two keeps each change small and easy to roll back.

Moving from cloud NAC

Start with the posture rules. List each rule and the requirement it serves. Many map to identity: "managed device, current staff member" becomes a certificate plus an IdP group. Rules that do not map are your evidence for keeping posture checks where policy mandates them.

Moving headless devices

MAC address lists are the usual fallback for printers, sensors and smart TVs. Move them to the xPSK network instead. Each device gets its own key, and the key sets its VLAN. Revoke one key and nothing else on the network changes.

How do you decide between cloud NAC and RADIUS?

Use one decision rule. Write your access requirement as a sentence. If it reads "this person, on this device, gets this VLAN", choose Purple cloud RADIUS. Only a mandated health check on wired ports moves the requirement into NAC territory.

Three questions settle most cases:

  • Does policy demand device posture, or only managed devices? Managed devices are an EAP-TLS and identity requirement.
  • Where does your directory live? Microsoft Entra ID, Okta or Google Workspace points to cloud RADIUS.
  • How many sites have no local IT? Every one of them makes on-premises servers harder to run.

For a multi-site estate on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist or Ubiquiti UniFi, the answer is usually cloud RADIUS. Your next step is a pilot SSID at one site. Read how Purple cloud RADIUS works, then book the pilot. For the wider security picture, see the enterprise WiFi security guide.

Frequently asked questions

Is cloud RADIUS the same as cloud NAC?

No. Cloud RADIUS authenticates devices over 802.1X and returns policy, such as the VLAN, to your access points. Cloud NAC includes that RADIUS function, then adds endpoint posture checks, device profiling and remediation, usually through an agent on each device. If your WiFi requirement is identity and segmentation, cloud RADIUS covers it. Posture is the feature that separates the two categories.

Does Purple cloud RADIUS work with the access points we already own?

Yes. Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You point your WPA2 or WPA3 Enterprise SSID at Purple as its RADIUS server in your existing console. No new hardware is required. You keep your controllers, switching and VLAN design.

How long does a migration from on-premises RADIUS take?

A RADIUS migration to Purple is usually a weekend exercise. You inventory SSIDs and VLAN rules, connect your identity provider and pilot one SSID. Then you change the RADIUS server in your console and keep the old server as a short fallback. If you are also moving from PEAP to EAP-TLS, run the certificate rollout through your MDM as a separate workstream.

Can we run Microsoft NPS or FreeRADIUS alongside Purple during the move?

Yes. The cleanest pattern is a pilot SSID pointed at Purple while production SSIDs stay on NPS or FreeRADIUS. Once each device type passes on the pilot, you switch production SSIDs site by site. Keep the old server running until the fallback window closes, then decommission it. Nobody loses access during the change.

Does cloud RADIUS give us evidence for PCI DSS and ISO 27001 audits?

Yes, it gives you evidence for both. Certificate-based 802.1X shows strong authentication, and identity-set VLANs show segmentation between payment systems and staff or guest traffic. Purple holds ISO 27001 and Cyber Essentials certification and is built for GDPR and CCPA. Your auditor still assesses your whole environment. Purple supplies evidence for the WiFi access controls within it.

How is cloud NAC priced compared with cloud RADIUS?

Both are usually subscriptions, but the unit differs. Cloud NAC is commonly priced per endpoint or per device, so cost climbs with every phone, scanner and laptop. On-premises RADIUS has low software cost, but you pay in servers, failover design and engineering time. Purple cloud RADIUS is a subscription with no servers to run. Compare the total cost to run, not licence lines alone.

What happens to WiFi if cloud RADIUS is unreachable?

Purple backs cloud RADIUS with a 99.9% RADIUS uptime SLA on a platform that runs at 99.999% uptime. Devices already authenticated keep their session until they next re-authenticate, for example on roaming or at session timeout. Our guide to cloud RADIUS high availability explains the regions, the failover design and what the SLA covers.

Do we need NAC for IoT devices that cannot do 802.1X?

No. Devices that cannot run 802.1X, such as printers, sensors and smart TVs, belong on Purple's xPSK network. Each device, or each resident, gets its own key, and that key sets the VLAN. A lost or retired device loses its key without affecting anything else. You manage it from the same console as your secure and open networks.

Frequently asked questions

Is cloud RADIUS the same as cloud NAC?

No. Cloud RADIUS authenticates devices over 802.1X and returns policy, such as the VLAN, to your access points. Cloud NAC includes that RADIUS function, then adds endpoint posture checks, device profiling and remediation, usually through an agent on each device. If your WiFi requirement is identity and segmentation, cloud RADIUS covers it. Posture is the feature that separates the two categories.

Does Purple cloud RADIUS work with the access points we already own?

Yes. Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You point your WPA2 or WPA3 Enterprise SSID at Purple as its RADIUS server in your existing console. No new hardware is required. You keep your controllers, switching and VLAN design.

How long does a migration from on-premises RADIUS take?

A RADIUS migration to Purple is usually a weekend exercise. You inventory SSIDs and VLAN rules, connect your identity provider and pilot one SSID. Then you change the RADIUS server in your console and keep the old server as a short fallback. If you are also moving from PEAP to EAP-TLS, run the certificate rollout through your MDM as a separate workstream.

Can we run Microsoft NPS or FreeRADIUS alongside Purple during the move?

Yes. The cleanest pattern is a pilot SSID pointed at Purple while production SSIDs stay on NPS or FreeRADIUS. Once each device type passes on the pilot, you switch production SSIDs site by site. Keep the old server running until the fallback window closes, then decommission it. Nobody loses access during the change.

Does cloud RADIUS give us evidence for PCI DSS and ISO 27001 audits?

Yes, it gives you evidence for both. Certificate-based 802.1X shows strong authentication, and identity-set VLANs show segmentation between payment systems and staff or guest traffic. Purple holds ISO 27001 and Cyber Essentials certification and is built for GDPR and CCPA. Your auditor still assesses your whole environment. Purple supplies evidence for the WiFi access controls within it.

How is cloud NAC priced compared with cloud RADIUS?

Both are usually subscriptions, but the unit differs. Cloud NAC is commonly priced per endpoint or per device, so cost climbs with every phone, scanner and laptop. On-premises RADIUS has low software cost, but you pay in servers, failover design and engineering time. Purple cloud RADIUS is a subscription with no servers to run. Compare the total cost to run, not licence lines alone.

What happens to WiFi if cloud RADIUS is unreachable?

Purple backs cloud RADIUS with a 99.9% RADIUS uptime SLA on a platform that runs at 99.999% uptime. Devices already authenticated keep their session until they next re-authenticate, for example on roaming or at session timeout. Our guide to [cloud RADIUS high availability](guide:cloud-radius-high-availability) explains the regions, the failover design and what the SLA covers.

Do we need NAC for IoT devices that cannot do 802.1X?

No. Devices that cannot run 802.1X, such as printers, sensors and smart TVs, belong on Purple's xPSK network. Each device, or each resident, gets its own key, and that key sets the VLAN. A lost or retired device loses its key without affecting anything else. You manage it from the same console as your secure and open networks.

Turn this guide into a plan for your estate

Tell us about your sites and the hardware you run. A Purple engineer maps Purple Access on top of it with you, and you keep the plan.

  1. Book a demoTell us what runs on your WiFi today, and a Purple network engineer maps it with you.
  2. Map your SSIDs onto threeOpen, secure and xPSK, on the access points you already own. You leave with the plan.
  3. Prove it on one site firstJudge the result on tickets and audit evidence, then roll out.

Book a demo

Tell us about your network

Led by a Purple network engineer. No slides.