O que é a Autenticação RADIUS e Como Funciona?

This guide provides a definitive technical reference on RADIUS authentication for IT leaders managing enterprise and guest WiFi deployments. It demystifies the AAA protocol, explains how 802.1X and EAP methods work together, and details how Purple's cloud-based platform simplifies deployment for hotels, retail chains, stadiums, and public-sector organisations. Readers will leave with a clear implementation roadmap, real-world case studies, and the decision frameworks needed to migrate from insecure pre-shared keys to a robust, identity-driven network access control architecture.

📖 6 min de leitura📝 1,416 palavras🔧 2 exemplos❓ 3 perguntas📚 10 termos-chave

🎧 Ouça este Guia

Ver Transcrição

### What is RADIUS Authentication and How Does It Work? — Purple Technical Briefing

**[INTRO — 1 minute]**

Welcome to the Purple Technical Briefing. I'm your host, and in the next ten minutes, we're going to demystify one of the most critical technologies for enterprise network security: RADIUS authentication. If you're an IT manager, a network architect, or a CTO responsible for WiFi at a large venue — a hotel, a retail chain, a stadium, or a conference centre — this briefing is specifically for you. We'll cut through the jargon, explain the architecture clearly, and give you the practical insights you need to make informed decisions this quarter.

Let's start with the big picture. Why does any of this matter?

If you're still running your guest or staff WiFi on a single shared password — a Pre-Shared Key, or PSK — you are operating with a significant and growing security risk. That password gets shared, written on receipts, photographed on whiteboards, and forwarded via messaging apps. Once it's out, you have no visibility into who is on your network, no ability to revoke access for a single user without disrupting everyone, and no audit trail if something goes wrong. For organisations subject to PCI DSS, GDPR, or HIPAA, this isn't just a technical problem. It's a compliance liability.

RADIUS is the solution that the industry has converged on to address this. So let's understand exactly what it is and how it works.

**[TECHNICAL DEEP-DIVE — 5 minutes]**

RADIUS stands for Remote Authentication Dial-In User Service. The name is a historical artefact from the early days of dial-up internet, but the protocol has evolved significantly and remains the backbone of enterprise network access control today. At its core, RADIUS is a centralised server-based system that manages network access using a framework called AAA — Authentication, Authorization, and Accounting. These three pillars are the foundation of everything we'll discuss today.

Authentication is the first pillar: verifying who someone is. Authorization is the second: determining what they're allowed to do. And Accounting is the third: recording what they actually did. Let's explore each one.

Authentication. When a user tries to connect to a WiFi network secured with WPA2-Enterprise or WPA3-Enterprise, their device — which we call the Supplicant — sends a connection request to the wireless access point. The access point, which we call the Authenticator, does not make the authentication decision itself. It acts as a relay, forwarding the request to the RADIUS server. The RADIUS server then validates the user's identity against a configured identity source. This could be Microsoft Active Directory, Azure Active Directory, Google Workspace, Okta, or a local user database. The identity source is the single source of truth for who is allowed on your network.

The RADIUS server can validate identity in several ways. The most common in enterprise environments are credential-based methods, where the user provides a username and password, and certificate-based methods, where the user's device presents a digital certificate. We'll talk about the security implications of each shortly.

Authorization. Once the user is authenticated, the RADIUS server doesn't just say yes and step aside. It also tells the access point exactly what to do with this user. It sends back a set of attributes — instructions, essentially — that define the user's network experience. The most important of these is typically the VLAN assignment. The RADIUS server might say: this user is a member of the corporate staff group, assign them to VLAN ten, which has access to internal file servers and printers. Or: this user is a guest, assign them to VLAN twenty, which only has internet access and is completely isolated from the corporate network. This dynamic VLAN assignment is one of the most powerful features of RADIUS, and it's the mechanism that enables proper network segmentation.

Accounting. The third pillar is often overlooked, but it's critically important for compliance and operations. As a user's session progresses, the RADIUS server logs key information: the time they connected, the time they disconnected, the total session duration, the amount of data they transferred, and the MAC address of their device. This creates a detailed audit trail for every connection on your network. Under PCI DSS 4.0, this kind of logging is not optional — it's a hard requirement. And in the event of a security incident, these logs are invaluable for forensic investigation.

Now, let's talk about the technical standard that makes all of this work: IEEE 802.1X.

802.1X is the standard that defines port-based network access control. It's the protocol that allows an access point to block all network traffic from a device until the RADIUS server has confirmed that the device is authorised. The communication between the user's device and the access point uses a protocol called EAP — the Extensible Authentication Protocol. EAP is essentially a framework that supports multiple authentication methods.

The three most common EAP methods in enterprise WiFi are: PEAP, which stands for Protected Extensible Authentication Protocol; EAP-TTLS; and EAP-TLS.

PEAP and EAP-TTLS are credential-based methods. They create an encrypted tunnel between the device and the RADIUS server, and then the user's username and password are verified inside that tunnel. They're relatively easy to deploy and work well in environments where you're not yet ready for a full certificate infrastructure.

EAP-TLS is the gold standard. It's certificate-based, meaning both the server and the client device present digital certificates to authenticate each other. There is no password involved at all. This completely eliminates the risk of credential theft, phishing attacks, and man-in-the-middle attacks. For corporate devices, EAP-TLS is the authentication method you should be working towards.

**[IMPLEMENTATION AND PITFALLS — 2 minutes]**

So how do you actually deploy all of this? Let me walk you through the key steps.

First, choose your RADIUS server. You can deploy an on-premise server — Microsoft's Network Policy Server is a common choice in Windows environments — or use a cloud-based RADIUS service. Cloud RADIUS platforms, like the one offered by Purple, provide a fully managed, highly available infrastructure without the operational overhead. For multi-site organisations, the cloud approach is almost always the right choice.

Second, integrate your identity source. Connect your RADIUS server to your organisation's identity directory. Most modern cloud RADIUS platforms support direct integration with Azure AD, Google Workspace, and Okta.

Third, configure your network hardware. Create a new SSID configured for WPA2-Enterprise or WPA3-Enterprise and point it at your RADIUS server. You'll also configure a shared secret — a password that encrypts the communication between the access point and the RADIUS server. This shared secret must match exactly on both sides. A mismatch here is one of the most common causes of authentication failures during initial deployment.

Fourth, define your authorisation policies. Map user groups to network policies — staff get full access on VLAN ten, guests get internet-only access on VLAN twenty.

Fifth, onboard your users. For corporate staff, deploy WiFi profiles via your MDM platform. For guests, use a captive portal. Purple's platform automates the guest onboarding flow, supporting social media logins, registration forms, and voucher codes.

**[RAPID-FIRE Q&A — 1 minute]**

Let's do a rapid-fire Q and A on the questions we hear most often.

First: What's the difference between RADIUS and a captive portal? A captive portal is the login page guests see when they connect. It works with RADIUS. The portal is the user interface; RADIUS is the back-end engine.

Second: Can I use RADIUS for wired networks? Absolutely. The 802.1X standard applies equally to wired Ethernet and wireless networks.

Third: Is RADIUS difficult to set up? It has a reputation for complexity, but modern cloud platforms have changed this dramatically. With a managed service like Purple, you can get a production-ready RADIUS deployment up and running quickly.

**[SUMMARY AND NEXT STEPS — 1 minute]**

To summarise: RADIUS is the centralised protocol that powers enterprise WiFi security. It implements the AAA framework to give you granular control over who can access your network, what they can do, and a complete audit trail of their activity. For venue operators, hoteliers, retailers, and public-sector organisations, deploying RADIUS is the foundational step in building a secure, compliant, and professionally managed WiFi infrastructure.

Your next step is clear: if you're still running on pre-shared keys, start planning your migration today. Review your current hardware for WPA3-Enterprise support, assess your identity directory integration options, and explore a cloud RADIUS platform that can scale with your organisation.

That's all we have time for on this Purple Technical Briefing. Thanks for listening. To learn more about how Purple can help you deploy secure, intelligent WiFi across your venues, visit us at purple dot ai. Until next time, stay secure.

Resumo Executivo

Para os líderes de TI em locais com múltiplos polos — hotéis, cadeias de retalho, estádios e centros de conferências —, fornecer um acesso WiFi seguro e fiável a milhares de utilizadores diários é um serviço de missão crítica que acarreta riscos operacionais e regulamentares significativos. A abordagem obsoleta de utilizar uma única chave pré-partilhada (PSK) para as redes de convidados e de funcionários já não é uma postura de segurança defensável. Expõe as organizações a violações de conformidade no âmbito do PCI DSS e do GDPR, a interrupções operacionais e a danos reputacionais resultantes de potenciais falhas de segurança.

A solução moderna e padrão da indústria consiste em centralizar o controlo de acesso à rede através do protocolo RADIUS (Remote Authentication Dial-In User Service). O RADIUS fornece uma estrutura robusta para os três pilares da segurança de rede — Autenticação, Autorização e Contabilização (AAA - Authentication, Authorization, and Accounting) — impondo um acesso baseado na identidade para cada utilizador e dispositivo. Ao integrar-se com um diretório de identidades existente, como o Azure AD, o Google Workspace ou o Okta, o RADIUS garante que apenas indivíduos autorizados se podem ligar e que o seu acesso é rigorosamente delimitado de acordo com a sua função.

Este guia fornece uma visão geral prática e acionável do RADIUS, da norma IEEE 802.1X subjacente e de como a plataforma de inteligência WiFi da Purple abstrai a complexidade da implementação. Foi escrito para arquitetos de rede e gestores de TI que precisam de tomar decisões de implementação neste trimestre, e não no próximo ano.

Análise Técnica Aprofundada

A Estrutura AAA: Autenticação, Autorização e Contabilização

O RADIUS opera no modelo cliente-servidor e é construído em torno da estrutura AAA, um conceito fundamental na segurança de redes. Compreender cada componente é essencial para uma implementação bem-sucedida.

A Autenticação é o processo de verificação da identidade de um utilizador. Quando um utilizador tenta ligar-se a uma rede WiFi protegida com WPA2/WPA3-Enterprise, o seu dispositivo — o Suplicante (Supplicant) — envia as credenciais para o Ponto de Acesso Sem Fios — o Autenticador (Authenticator). O Autenticador não toma a decisão de acesso por si próprio; reencaminha o pedido para o servidor RADIUS. O servidor RADIUS valida estas credenciais face a uma fonte de identidade configurada: Microsoft Active Directory, um IdP na nuvem como o Okta, ou uma base de dados de utilizadores local. A validação pode utilizar uma combinação de nome de utilizador e palavra-passe ou, para uma segurança significativamente mais forte, um certificado digital através de um método EAP, como o EAP-TLS.

A Autorização determina o que é permitido a um utilizador autenticado fazer. Com base nas políticas definidas pelo administrador de rede, o servidor RADIUS devolve atributos específicos ao Autenticador. Estes atributos ditam a atribuição de VLAN (separando o tráfego de convidados do tráfego corporativo), os limites de largura de banda e as restrições de acesso por hora do dia. Esta aplicação de políticas granular e dinâmica é uma das principais vantagens do RADIUS em relação aos sistemas estáticos baseados em PSK.

A Contabilização rastreia a atividade do utilizador ao longo da sessão. O servidor RADIUS regista os carimbos de data/hora da ligação, a duração da sessão, os dados transferidos e os endereços MAC dos dispositivos. Este rasto de auditoria é inestimável para a resolução de problemas, o planeamento de capacidade e os relatórios de conformidade. Ao abrigo do PCI DSS 4.0, o registo e a monitorização de todos os acessos aos recursos da rede constituem um controlo obrigatório.

Como o RADIUS e o 802.1X Funcionam em Conjunto

A norma IEEE 802.1X define o controlo de acesso à rede baseado em portas. Num contexto WiFi, o 802.1X permite que um ponto de acesso bloqueie todo o tráfego de um dispositivo — exceto as mensagens de autenticação — até que o servidor RADIUS tenha confirmado a autorização. A comunicação entre o Suplicante e o Autenticador utiliza o Extensible Authentication Protocol (EAP), transportado através da LAN como EAPOL (EAP over LAN). O Autenticador retransmite então esta informação para o servidor RADIUS utilizando o protocolo RADIUS.

A escolha do método EAP é uma decisão de segurança crítica:

Método EAP	Tipo de Autenticação	Nível de Segurança	Caso de Uso Recomendado
EAP-TLS	Baseado em certificados	Mais elevado	Dispositivos corporativos geridos — padrão de excelência
PEAP-MSCHAPv2	Baseado em credenciais	Médio	Ambientes predominantemente Windows em transição para certificados
EAP-TTLS/PAP	Baseado em credenciais	Médio	Ambientes de SO mistos com suporte a dispositivos legados

Para dispositivos corporativos, o EAP-TLS é o estado pretendido. Utiliza a autenticação mútua de certificados — tanto o cliente como o servidor apresentam certificados —, eliminando completamente as palavras-passe e os riscos associados de roubo de credenciais e phishing.

Portas e Transporte RADIUS

Por predefinição, o RADIUS utiliza a porta UDP 1812 para autenticação e autorização, e a porta UDP 1813 para contabilização. Algumas implementações legadas utilizam as portas 1645 e 1646. Desde o RFC 6613, o RADIUS também pode operar sobre TCP com TLS (RadSec), o que é cada vez mais utilizado em implementações na nuvem para uma maior segurança de transporte.

Guia de Implementação

Transição de PSK para RADIUS: Um Roteiro em Cinco Passos

Passo 1: Selecionar a sua Infraestrutura RADIUS. Escolha entre um servidor local (on-premise) (Microsoft NPS para ambientes Windows, FreeRADIUS para implementações de código aberto) ou um serviço RADIUS baseado na nuvem. Para organizações com múltiplos polos, uma plataforma RADIUS na nuvem como a da Purple é quase sempre a escolha correta. Fornece alta disponibilidade integrada, redundância geográfica e elimina a carga operacional da gestão de servidores.

Passo 2: Integrar a sua Fonte de Identidade. Ligue o servidor RADIUS ao diretório de identidades autoritativo da sua organização. As plataformas RADIUS modernas na nuvem suportam a integração direta com o Azure AD, o Google Workspace e o Okta via SAML ou LDAP. Para utilizadores convidados, a fonte de identidade é tipicamente um CRM, um sistema de gestão de propriedades (PMS) ou uma plataforma de WiFi para convidados concebida para o efeito.

Passo 3: Configurar o Hardware de Rede. No seu controlador de LAN sem fios ou nos pontos de acesso, crie um novo SSID configurado para WPA2-Enterprise ou WPA3-Enterprise. Aponte o SSID para o endereço IP do seu servidor RADIUS e configure o segredo partilhado (shared secret) — uma palavra-passe que encripta a comunicação entre o ponto de acesso e o servidor RADIUS. Este valor tem de corresponder exatamente em ambos os lados; uma incompatibilidade é uma das causas mais comuns de falhas na implementação inicial.

Passo 4: Definir Políticas de Autorização. Crie regras no servidor RADIUS que mapeiem grupos de utilizadores para políticas de rede. Um conjunto de políticas típico para um hotel pode incluir: Funcionários na VLAN 10 com acesso interno total; Prestadores de serviços na VLAN 30 com acesso limitado e um limite de largura de banda de 50 Mbps; Convidados na VLAN 20 com acesso apenas à Internet e um limite de sessão de 8 horas.

Passo 5: Integrar Utilizadores e Dispositivos. Para os funcionários corporativos, implemente perfis de WiFi com definições 802.1X através da sua plataforma MDM. Para os convidados, implemente um Captive Portal. A plataforma da Purple automatiza o fluxo de integração de convidados — suportando inícios de sessão através de redes sociais, formulários de registo e códigos de voucher — e cria contas de utilizador RADIUS temporárias que expiram automaticamente.

Melhores Práticas

Adotar o WPA3-Enterprise. Sempre que o hardware o suporte, o WPA3-Enterprise proporciona melhorias de segurança significativas em relação ao WPA2-Enterprise, incluindo Protected Management Frames (PMF) e uma encriptação mais forte através do modo de segurança de 192 bits. Realize uma auditoria ao hardware para identificar os pontos de acesso que requerem atualizações de firmware ou substituição.

Implementar o EAP-TLS para Dispositivos Corporativos. A autenticação baseada em certificados elimina a palavra-passe enquanto vulnerabilidade. Integre o seu servidor RADIUS com a sua PKI ou utilize uma solução de gestão de certificados baseada na nuvem. Automatize a implementação de certificados através de MDM para minimizar a sobrecarga de TI.

Impor a Segmentação de VLAN. A atribuição dinâmica de VLAN através de RADIUS é inegociável para a conformidade com o PCI DSS e a arquitetura Zero Trust. Certifique-se de que os seus switches de rede e firewalls impõem políticas de encaminhamento inter-VLAN que impedem o tráfego de convidados de alcançar os recursos corporativos.

Implementar uma Infraestrutura RADIUS Redundante. Configure pelo menos um servidor RADIUS primário e um secundário nos seus pontos de acesso. As plataformas RADIUS na nuvem fornecem normalmente esta funcionalidade de forma automática. Teste a ativação pós-falha (failover) regularmente.

Resolução de Problemas e Mitigação de Riscos

Modo de Falha	Causa Raiz	Resolução
Todos os utilizadores rejeitados	Incompatibilidade do segredo partilhado entre o AP e o servidor RADIUS	Verificar o segredo partilhado na configuração de ambos, AP e servidor RADIUS
Erros de certificado nos dispositivos clientes	Certificado do servidor RADIUS não é de confiança para o cliente	Instalar o certificado da CA raiz em todos os dispositivos clientes via MDM
Falhas de autenticação intermitentes	Servidor RADIUS sobrecarregado ou inacessível	Implementar um servidor RADIUS secundário; rever a capacidade do servidor
Portal de convidados não redireciona	Má configuração do walled garden	Garantir que o URL do portal e os domínios dos fornecedores de início de sessão social estão no walled garden
Utilizadores não conseguem voltar a ligar-se após a expiração da sessão	Sessão de contabilização não terminada corretamente	Rever a configuração de contabilização RADIUS; verificar se existem sessões obsoletas

ROI e Impacto no Negócio

O caso de negócio para a implementação do RADIUS é convincente em múltiplas dimensões. A redução do risco de segurança é o benefício mais imediato: substituir uma PSK partilhada por um acesso baseado na identidade elimina o vetor mais comum de intrusões de rede baseadas em WiFi, evitando potencialmente custos de violação que rondam, em média, os 3,4 milhões de libras para as empresas do Reino Unido. A garantia de conformidade no âmbito do PCI DSS, do GDPR e de regulamentações setoriais específicas é alcançada através da combinação do controlo de acesso baseado na identidade e de registos de contabilização abrangentes. Os ganhos de eficiência operacional são significativos em grandes implementações — a gestão centralizada de políticas significa que a integração de um novo utilizador ou a revogação do acesso de um funcionário que sai é uma ação única no diretório de identidades, e não uma reconfiguração manual em dezenas de pontos de acesso. Por fim, os dados de contabilização gerados pelo RADIUS fornecem inteligência acionável para o planeamento de capacidade, permitindo que as decisões de investimento em infraestruturas sejam fundamentadas em dados de utilização reais, em vez de estimativas.

Termos-Chave e Definições

RADIUS (Remote Authentication Dial-In User Service)

A networking protocol, standardised in RFC 2865, that provides centralised Authentication, Authorization, and Accounting (AAA) management for users connecting to a network service. It operates on a client-server model, where the Network Access Server (NAS) is the client and the RADIUS server is the decision-making authority.

This is the core engine of enterprise WiFi security. When an IT manager talks about 'moving to 802.1X', they are almost always talking about deploying a RADIUS server.

802.1X

An IEEE standard for port-based Network Access Control (PNAC). It defines the encapsulation of the Extensible Authentication Protocol (EAP) over IEEE 802 networks, enabling an authenticator (e.g., a WiFi access point) to enforce authentication before granting network access.

This is the standard that makes RADIUS work for WiFi. When configuring an SSID for 'WPA2-Enterprise', you are enabling 802.1X on that SSID.

AAA (Authentication, Authorization, Accounting)

A security framework for intelligently controlling access to computer resources, enforcing policies, and auditing usage. Authentication verifies identity, Authorization determines permitted actions, and Accounting records activity.

RADIUS servers are often called 'AAA servers'. Understanding this framework is the conceptual foundation for all network access control design.

Supplicant

In the 802.1X framework, the Supplicant is the client device — a laptop, smartphone, or IoT device — that is requesting access to the network. The supplicant software on the device handles the EAP authentication exchange.

When troubleshooting authentication failures, the supplicant configuration (e.g., the WiFi profile on a laptop) is often the source of the problem.

Authenticator

In the 802.1X framework, the Authenticator is the network device — typically a wireless access point or an Ethernet switch — that enforces access control. It relays EAP messages between the Supplicant and the Authentication Server but does not make the authentication decision itself.

The access point is a relay, not a decision-maker. This is a critical distinction: the AP's job is to forward the request to RADIUS and then act on the response.

EAP (Extensible Authentication Protocol)

An authentication framework defined in RFC 3748 that supports multiple authentication methods. EAP itself does not define a specific authentication mechanism; instead, it provides a standard format for negotiating and carrying various EAP methods (e.g., EAP-TLS, PEAP, EAP-TTLS).

When configuring 802.1X, you must choose an EAP method. The choice between EAP-TLS (certificates) and PEAP (passwords) is one of the most consequential security decisions in a WiFi deployment.

EAP-TLS (EAP Transport Layer Security)

A certificate-based EAP method that provides mutual authentication between the client and the RADIUS server using X.509 digital certificates. It is widely regarded as the most secure EAP method, as it eliminates passwords entirely.

EAP-TLS is the gold standard for corporate device authentication. Deploying it requires a Public Key Infrastructure (PKI) to issue and manage client certificates, which is why cloud-based certificate management solutions are increasingly popular.

Captive Portal

A web page that intercepts a user's connection to a public WiFi network, requiring them to complete an action — such as accepting terms of service, entering credentials, or authenticating via a social media account — before internet access is granted.

Captive portals work in conjunction with RADIUS for guest WiFi. The portal is the user-facing interface; RADIUS is the back-end authentication engine that validates the user's session and enforces access policies.

VLAN (Virtual Local Area Network)

A logical network segment created within a physical network infrastructure. VLANs allow network administrators to segregate traffic from different user groups — such as guests, staff, and IoT devices — even when they share the same physical hardware.

Dynamic VLAN assignment via RADIUS is the mechanism that enables network segmentation in enterprise WiFi. It is a fundamental requirement for PCI DSS compliance and Zero Trust architecture.

Shared Secret

A password configured on both the RADIUS client (the access point) and the RADIUS server to authenticate their communication and encrypt RADIUS attribute values. It must be identical on both sides.

A shared secret mismatch is one of the most common causes of RADIUS authentication failures during initial deployment. Always copy-paste rather than manually type this value.

Estudos de Caso

A 500-room hotel needs to provide secure WiFi for guests, conference attendees, and staff. Guests should have a frictionless onboarding experience, while staff require secure access to internal property management and point-of-sale systems. The hotel uses Oracle OPERA as its Property Management System (PMS).

Deploy Purple's cloud RADIUS platform integrated with the hotel's Oracle OPERA PMS. Provision three separate SSIDs: 'Hotel-Guest', 'Conference-WiFi', and 'Staff-Internal'. The 'Staff-Internal' SSID is configured for WPA3-Enterprise with EAP-TLS. Digital certificates are deployed to all hotel-owned devices via an MDM platform (e.g., Jamf or Microsoft Intune), enabling passwordless, seamless authentication for staff. The 'Hotel-Guest' SSID uses a branded captive portal integrated with OPERA. At check-in, OPERA automatically creates a temporary RADIUS user account with credentials valid for the duration of the guest's stay. The guest receives a QR code or a welcome email with a direct connection link. The 'Conference-WiFi' SSID uses a voucher-based system within Purple's platform, allowing event coordinators to generate unique, time-limited access codes for their attendees. All three SSIDs use dynamic VLAN assignment to enforce strict traffic segmentation.

Notas de Implementação: This architecture addresses three distinct user populations with appropriately tailored authentication methods. The PMS integration for guest access is a key operational efficiency gain, eliminating manual credential management at the front desk. The certificate-based approach for staff devices is the correct security choice for users with access to sensitive internal systems. The voucher system for conference attendees provides a scalable, self-service model for event management. VLAN segmentation across all three SSIDs ensures that a compromised guest device cannot reach the hotel's back-of-house network.

A retail chain with 200 stores across the UK wants to replace its insecure, shared-password guest WiFi network. The marketing team requires opt-in demographic data from store visitors to support targeted campaigns. The IT team uses Azure Active Directory for all corporate identity management.

Deploy Purple's cloud RADIUS and guest WiFi platform across all 200 stores using a centralised, templated configuration. For guest access, configure a branded captive portal on a dedicated guest SSID. The portal offers authentication via social media accounts (Facebook, Google) or a simple registration form, capturing opt-in marketing consent in compliance with GDPR. Purple's platform aggregates this data into a centralised analytics dashboard, providing the marketing team with visitor demographics, dwell times, and repeat visit rates. For corporate staff, integrate the RADIUS server with the existing Azure AD tenant. Staff connect to a separate 'Staff' SSID using their Azure AD credentials via PEAP, with a phased migration plan to EAP-TLS with certificates for the highest-risk roles. All guest traffic is isolated on a dedicated VLAN with no access to the store's internal network or EPOS systems, meeting PCI DSS network segmentation requirements.

Notas de Implementação: This solution simultaneously resolves the security, compliance, and marketing objectives. The social login and registration form options provide a low-friction guest experience while generating valuable, consented first-party data — a significant commercial asset in a post-third-party-cookie environment. The Azure AD integration for staff access is highly efficient, leveraging the existing identity investment and avoiding the creation of a parallel user database. The phased approach to EAP-TLS is a pragmatic deployment strategy that delivers immediate security improvements while building towards the target state.

Análise de Cenários

Q1. You are the IT architect for a large conference centre. A major technology company is renting your venue for a three-day conference with 5,000 attendees. The client has a hard requirement that attendees can connect to a secure, high-performance WiFi network without manually entering a password each day. The client uses Okta as their identity provider. How would you design the authentication solution?

💡 Dica:Consider how to provide a seamless, passwordless experience for a large number of users from a single external organisation. Think about certificate-based authentication and how to integrate with a third-party identity provider for a time-limited event.

Mostrar Abordagem Recomendada

The optimal solution is to provision a dedicated SSID for the conference configured for WPA3-Enterprise with EAP-TLS. Integrate your cloud RADIUS platform with the client's Okta tenant via SAML federation for the duration of the event. Before the conference opens, attendees are directed to a one-time onboarding portal where they authenticate with their Okta credentials. Upon successful authentication, a unique digital certificate is generated and installed on their device. For the remainder of the conference, their device automatically and securely connects to the SSID without any further user interaction. The certificates are issued with a validity period matching the conference duration and are automatically revoked at close. This delivers a seamless, passwordless experience while maintaining strong security, and it leverages the client's existing identity infrastructure rather than creating a separate credential system.

Q2. A private hospital needs to provide WiFi for patients and visitors, but must ensure this traffic is completely isolated from the network used for clinical systems, electronic health records, and medical devices, to comply with HIPAA and NHS DSP Toolkit requirements. What RADIUS feature is most critical to achieving this isolation, and how would you configure it?

💡 Dica:Focus on the Authorization pillar of the AAA framework. The key is not just authenticating users, but controlling what they can reach after authentication. Consider how RADIUS communicates network policy to the access point.

Mostrar Abordagem Recomendada

The most critical feature is dynamic VLAN assignment via RADIUS authorization policies. You would create a dedicated 'Patient-Guest' VLAN (e.g., VLAN 50) on the network infrastructure, configured with firewall rules that permit only internet access and explicitly deny all traffic to the clinical network VLANs. On the RADIUS server, create an authorization policy that assigns any user authenticating to the patient WiFi SSID to VLAN 50, regardless of their credentials. The RADIUS server communicates this assignment to the access point via the Tunnel-Type, Tunnel-Medium-Type, and Tunnel-Private-Group-ID attributes in the Access-Accept message. The access point then places the user's traffic into VLAN 50 at the point of connection. This ensures that even if a patient's device is compromised, it has no network path to clinical systems — a fundamental requirement for HIPAA compliance and clinical network security.

Q3. Your organisation has deployed 802.1X with RADIUS across its corporate estate. An employee reports that they cannot connect to the corporate WiFi from their new laptop, but they can connect successfully from their smartphone and from their previous laptop. The IT helpdesk has confirmed the employee's account is active in Azure AD. What is your diagnostic approach, and what are the three most likely root causes?

💡 Dica:The issue is device-specific, not user-specific — the user can authenticate from other devices. This narrows the problem to the device configuration, the device's certificate, or the device's supplicant settings. Start with the RADIUS server logs.

Mostrar Abordagem Recomendada

The diagnostic approach is to first examine the RADIUS server's authentication logs for Access-Reject messages corresponding to the MAC address of the new laptop. The rejection reason code will identify the root cause. The three most likely causes are: (1) Missing or invalid client certificate — if the deployment uses EAP-TLS, the new laptop may not yet have had a certificate provisioned via MDM. Check whether the device is enrolled in the MDM platform and whether the certificate deployment policy has been applied. (2) Incorrect WiFi profile — the new laptop may have the wrong 802.1X supplicant settings, such as the wrong EAP method, an incorrect RADIUS server certificate trust configuration, or the wrong username format. Verify the WiFi profile matches the standard corporate template. (3) Device not yet registered in the identity directory — some RADIUS policies perform a device compliance check against Azure AD. If the new laptop has not yet completed Azure AD join and device registration, it may fail this check even though the user's account is active.

Principais Conclusões

✓RADIUS is the industry-standard protocol for centralised network access control, implementing the AAA (Authentication, Authorization, Accounting) framework to manage who can access your WiFi, what they can do, and to log all activity.
✓It replaces insecure pre-shared keys (PSKs) with robust, identity-based authentication, ensuring every user and device has a unique, verifiable identity on the network.
✓IEEE 802.1X is the standard that enables RADIUS to work with WiFi access points, blocking all network traffic from a device until the RADIUS server has confirmed authorisation.
✓EAP-TLS (certificate-based authentication) is the gold standard for corporate devices, eliminating passwords entirely and providing the strongest protection against credential theft and phishing.
✓Dynamic VLAN assignment via RADIUS authorization policies is the mechanism that enforces network segmentation — a mandatory control for PCI DSS compliance and a cornerstone of Zero Trust architecture.
✓For guest WiFi, RADIUS works in conjunction with a captive portal: the portal handles the user-facing onboarding experience, while RADIUS manages the back-end authentication and session policy enforcement.
✓Cloud-based RADIUS platforms such as Purple simplify deployment, provide built-in high availability, and integrate directly with modern identity providers (Azure AD, Google Workspace, Okta), making enterprise-grade network access control accessible for organisations of all sizes.