Implementación de WPA3-Enterprise para una seguridad inalámbrica mejorada

Esta guía de referencia técnica proporciona una hoja de ruta completa y práctica para los líderes de TI que realizan la transición de WPA2 a WPA3-Enterprise. Cubre los cambios arquitectónicos, las mejoras de seguridad obligatorias como EAP-TLS y PMF, y las estrategias de implementación prácticas para proteger las redes corporativas en entornos empresariales complejos.

📖 6 min de lectura📝 1,275 palabras🔧 2 ejemplos❓ 3 preguntas📚 8 términos clave

🎧 Escuchar esta guía

Ver transcripción

Implementing WPA3-Enterprise for Enhanced Wireless Security. A Purple WiFi Intelligence Briefing.

Welcome to the Purple Technical Briefing series. Today we're cutting straight to what matters: WPA3-Enterprise — what it actually means for your network, why the timing is critical right now, and how to get from where you are today to a fully compliant, future-proof wireless infrastructure.

If you're running a hotel group, a retail estate, a conference centre, or a public-sector facility, this briefing is for you. We're not going to wade through academic theory. We're going to talk about real decisions, real configurations, and real outcomes.

WPA3-Enterprise became a mandatory requirement for Wi-Fi CERTIFIED devices in 2020, and yet the majority of enterprise environments are still running WPA2. That gap is your risk exposure. PCI DSS 4.0, which came into full enforcement in March 2024, explicitly references stronger authentication standards. GDPR obligations around data protection by design are increasingly interpreted to include network-layer security. The window for treating WPA3 as a "nice to have" has closed.

Let's get into it.

So what actually changes with WPA3-Enterprise? Let's start with the authentication layer.

WPA2-Enterprise relies on IEEE 802.1X with EAP — Extensible Authentication Protocol — and that part doesn't change with WPA3. What changes is everything around it. The handshake, the encryption, and the management frame protection.

Under WPA2, the four-way handshake used to derive session keys is vulnerable to offline dictionary attacks. An attacker captures the handshake, takes it offline, and runs it against a wordlist. This is the basis of the KRACK attack — Key Reinstallation Attack — disclosed in 2017. WPA3 replaces this with SAE — Simultaneous Authentication of Equals — which is a Diffie-Hellman-based key exchange. The critical difference is that SAE provides forward secrecy. Even if an attacker captures every packet of a session and later compromises a long-term key, they cannot retroactively decrypt that session. Each session has its own ephemeral keys.

On the encryption side, WPA2 uses CCMP-128 — Counter Mode with Cipher Block Chaining Message Authentication Code Protocol — based on AES-128. WPA3-Enterprise mandates GCMP-256 — Galois Counter Mode Protocol with 256-bit keys — for its 192-bit security mode. This is the mode you want for any environment handling sensitive data: healthcare records, payment card data, government information.

Then there's Protected Management Frames — PMF — defined under IEEE 802.11w. Under WPA2, PMF is optional. Under WPA3, it is mandatory. Management frames are the control signals that manage association, disassociation, and authentication between clients and access points. Without PMF, an attacker can forge deauthentication frames — forcing clients off the network — as a denial-of-service attack or as a precursor to a man-in-the-middle attack. Mandatory PMF closes that vector entirely.

Now, the RADIUS server configuration. This is where most implementations either succeed or stall. Your RADIUS server — whether that's Microsoft NPS, FreeRADIUS, Cisco ISE, or Aruba ClearPass — needs to be configured to support EAP-TLS as the primary authentication method for WPA3-Enterprise. EAP-TLS uses mutual certificate-based authentication. The client presents a certificate, the server presents a certificate, and both validate each other. There are no passwords in this exchange. This eliminates credential-based attacks entirely.

The certificate infrastructure — your PKI — is the backbone of this. You need a Certificate Authority, either internal using Microsoft Active Directory Certificate Services, or a cloud-based PKI service. Each client device needs a certificate enrolled, typically via your MDM platform — Intune, Jamf, or similar. The RADIUS server needs its own server certificate from a CA that your clients trust. And you need an OCSP or CRL endpoint so clients can validate certificate revocation in real time.

For environments where full EAP-TLS is not immediately achievable — perhaps because you have a mix of managed and unmanaged devices — EAP-TTLS or PEAP with MSCHAPv2 remains an option as a transitional measure. But I want to be direct: credential-based EAP methods are a stepping stone, not a destination. The security posture of EAP-TLS is categorically superior, and your roadmap should target it.

One more thing on the technical side: transition mode. Most modern wireless controllers support WPA3 Transition Mode, which allows WPA2 and WPA3 clients to associate to the same SSID simultaneously. This is your migration path. You enable transition mode, validate that WPA3 clients are authenticating correctly, monitor your logs, and then — once you have confidence in the client estate — you move to WPA3-only. Don't try to do a hard cutover on day one. Transition mode exists precisely to avoid that risk.

Now let me give you the three most common failure modes I see in WPA3-Enterprise deployments, and how to avoid them.

First: certificate lifecycle management. Organisations deploy PKI, issue certificates, and then forget that certificates expire. A certificate expiry on your RADIUS server will take down authentication for every single client on your network simultaneously. You need automated renewal, monitoring alerts at 90 days, 60 days, and 30 days before expiry, and a tested renewal runbook. This is not optional. I have seen large hotel groups lose all corporate wireless access because a RADIUS certificate expired over a bank holiday weekend.

Second: client compatibility assumptions. Not every device in your estate will support WPA3. Legacy IoT devices — building management systems, older point-of-sale terminals, some CCTV systems — may only support WPA2 or even WPA. The answer is network segmentation. Put your WPA3-capable corporate devices on a WPA3-only SSID. Put your legacy IoT on a separate, isolated VLAN with WPA2, with strict firewall rules preventing lateral movement. Do not compromise your primary network's security posture to accommodate legacy devices.

Third: RADIUS server redundancy. A single RADIUS server is a single point of failure. In a multi-site deployment — a retail chain with 200 stores, for example — you need at minimum a primary and secondary RADIUS server, with failover configured at the wireless controller level. Test your failover. Actively test it. Simulate a primary RADIUS failure in a maintenance window and confirm that clients authenticate against the secondary within your acceptable timeout threshold.

For hospitality environments specifically — anyone running a guest WiFi platform — you have a dual network challenge. Your corporate network carries staff devices and back-office systems, and it should be WPA3-Enterprise with EAP-TLS. Your guest network is a different problem entirely, typically handled via a captive portal with social or email authentication. These are separate SSIDs, separate VLANs, and separate security policies. Do not conflate them.

A few questions I get asked regularly.

Do I need new access points? Probably not. Most access points manufactured after 2019 support WPA3 via firmware update. Check your vendor's release notes. Ruckus, Cisco Meraki, Aruba, and Ubiquiti all have WPA3 support in current firmware.

How long does a full deployment take? For a 50-site retail estate with an existing MDM and Active Directory, budget 12 to 16 weeks. The PKI build and certificate rollout is the long pole in the tent.

What does this cost? The infrastructure components — RADIUS, PKI, MDM — you likely already have. The incremental cost is professional services for configuration and testing, plus any access point firmware or replacement costs. For most organisations, the compliance risk mitigation alone justifies the investment.

Does WPA3 affect throughput? Negligibly. GCMP-256 is computationally efficient. In practice, you will not notice a throughput difference on modern hardware.

To wrap up: WPA3-Enterprise is not a future consideration. It is a present requirement for any organisation serious about network security, regulatory compliance, and protecting the data of the people who use your venues.

Your immediate next steps: audit your current access point firmware versions and confirm WPA3 support. Assess your PKI readiness — do you have an internal CA, or do you need to build one? Review your RADIUS server configuration and redundancy. And map your client device estate to identify any legacy devices that will need to be segmented.

Purple's platform integrates directly with your wireless infrastructure to provide the analytics and management layer on top of your secure network foundation. Whether you're running a hotel group, a retail chain, or a public venue, the combination of WPA3-Enterprise for your corporate network and a properly secured guest WiFi layer gives you both the security posture and the data intelligence your business needs.

Thanks for listening. If you want to go deeper on any of these topics — certificate authentication, RADIUS configuration, or guest network architecture — the full written guide is available on the Purple website, along with our broader library of technical reference material. Until next time.

Resumen Ejecutivo

Para los líderes de TI empresariales, la transición a WPA3-Enterprise ya no es un elemento de la hoja de ruta futura; es un requisito operativo actual. Desde 2020, WPA3 ha sido obligatorio para todos los dispositivos Wi-Fi CERTIFIED, sin embargo, muchas redes empresariales —que abarcan hostelería, comercio minorista y sedes del sector público— siguen ancladas a WPA2. Esta brecha representa una exposición significativa al riesgo, especialmente a medida que los marcos de cumplimiento como PCI DSS 4.0 y GDPR exigen cada vez más controles de seguridad de red robustos y de última generación.

Esta guía proporciona un desglose técnico completo de WPA3-Enterprise, centrándose en sus mejoras arquitectónicas fundamentales sobre WPA2. Detallamos el cambio obligatorio hacia una encriptación más fuerte (GCMP-256), la necesidad de Protected Management Frames (PMF) y la implementación crítica de la autenticación mutua basada en certificados a través de EAP-TLS. Diseñado para arquitectos de red y CTOs, este documento omite la teoría académica en favor de estrategias de implementación prácticas, metodologías de resolución de problemas y estudios de casos reales para garantizar una infraestructura inalámbrica segura, escalable y conforme.

Escuche el podcast técnico complementario para una visión general ejecutiva:

Análisis Técnico Detallado: Arquitectura WPA3-Enterprise

La diferencia fundamental entre WPA2 y WPA3-Enterprise no reside en el marco 802.1X subyacente, que sigue siendo el estándar para el control de acceso a la red basado en puertos, sino en los protocolos criptográficos y las protecciones de tramas de gestión construidas a su alrededor. WPA3 aborda las vulnerabilidades sistémicas de su predecesor, dirigiéndose específicamente a los ataques de diccionario fuera de línea y la manipulación de tramas de gestión.

Autenticación e Intercambio de Claves

WPA2-Enterprise se basa en el handshake de 4 vías para derivar claves de sesión, un proceso que ha demostrado ser vulnerable a los ataques de reinstalación de claves (KRACK) y a la fuerza bruta de diccionario fuera de línea si se utilizan credenciales débiles. WPA3 lo mitiga implementando Simultaneous Authentication of Equals (SAE), un protocolo de intercambio de claves basado en Diffie-Hellman. SAE garantiza la confidencialidad directa; incluso si un atacante compromete una clave a largo plazo, no puede descifrar retroactivamente el tráfico capturado, ya que cada sesión utiliza claves efímeras y únicas.

Para entornos empresariales, el mecanismo de autenticación principal se orienta decisivamente hacia EAP-TLS (Extensible Authentication Protocol-Transport Layer Security). Aunque WPA2 permitía métodos más débiles basados en credenciales como PEAP o EAP-TTLS, WPA3-Enterprise fomenta encarecidamente, y en el modo de alta seguridad de 192 bits lo exige, EAP-TLS. Esto requiere autenticación mutua basada en certificados, eliminando por completo las contraseñas y neutralizando los vectores de robo de credenciales.

Mejoras Criptográficas

WPA2 utiliza CCMP-128 (Counter Mode with Cipher Block Chaining Message Authentication Code Protocol) basado en AES-128. WPA3-Enterprise introduce una suite de seguridad opcional pero altamente recomendada de 192 bits, alineada con la Commercial National Security Algorithm (CNSA) Suite. Este modo exige GCMP-256 (Galois/Counter Mode Protocol con claves de 256 bits) para una encriptación robusta, junto con criptografía de curva elíptica de 384 bits para el establecimiento y la gestión de claves.

Tramas de Gestión Protegidas (PMF)

Según IEEE 802.11w, las Tramas de Gestión Protegidas (PMF) aseguran las señales de control que gestionan la asociación, desasociación y autenticación de clientes. En WPA2, PMF era opcional, dejando las redes vulnerables a tramas de desautenticación falsificadas, un precursor común de ataques de denegación de servicio o de intermediario. WPA3 hace que PMF sea obligatorio para todas las conexiones, cerrando fundamentalmente este vector de ataque.

Guía de Implementación: Despliegue de WPA3-Enterprise

La transición de una red empresarial a través de cientos de ubicaciones minoristas o un extenso complejo hotelero requiere un enfoque por fases y metódico. Los siguientes pasos describen una estrategia de despliegue independiente del proveedor.

Fase 1: Auditoría de Infraestructura y Preparación de PKI

El requisito previo para WPA3-Enterprise, específicamente utilizando EAP-TLS, es una infraestructura de clave pública (PKI) robusta.

Evaluar las Capacidades de RADIUS: Asegúrese de que sus servidores RADIUS (por ejemplo, Cisco ISE, Aruba ClearPass, FreeRADIUS) sean compatibles con los parámetros WPA3 y estén configurados para EAP-TLS.
Establecer una Autoridad de Certificación (CA): Despliegue una CA interna (como Microsoft AD CS) o aproveche un servicio PKI basado en la nube.
Integración de MDM: Utilice plataformas de Mobile Device Management (MDM) (Intune, Jamf) para automatizar el despliegue de certificados de cliente en dispositivos gestionados. Esto es fundamental para la escalabilidad.

Para más información sobre el despliegue de certificados, consulte Autenticación de Certificados WiFi: Cómo los Certificados Digitales Protegen las Wireless Networks .

Fase 2: Habilitación del Modo de Transición WPA3

Un cambio drástico rara vez es factible en entornos empresariales diversos. La mayoría de los controladores de LAN inalámbrica empresariales admiten el Modo de Transición WPA3, lo que permite que un único SSID acepte clientes WPA2 y WPA3 simultáneamente.

Configurar SSID de Transición: Habilite el Modo de Transición WPA3 en el SSID corporativo.
Monitorizar la Asociación de Clientes: Utilice su panel de gestión inalámbricatablero para monitorizar las conexiones de los clientes. Asegúrese de que los dispositivos modernos negocien WPA3 correctamente, mientras que los dispositivos heredados recurran a WPA2.
Abordar problemas de compatibilidad: Identifique los dispositivos que no se asocian. A menudo, los controladores inalámbricos heredados tienen dificultades con el requisito obligatorio de PMF de WPA3, incluso en modo de transición. Actualice los controladores siempre que sea posible.

Fase 3: Segmentación de red y aislamiento de sistemas heredados

No todos los dispositivos serán compatibles con WPA3. Los dispositivos IoT heredados, los sistemas de punto de venta más antiguos o los equipos médicos especializados en entornos de Healthcare a menudo carecen del hardware o las actualizaciones de firmware necesarios.

Aislar dispositivos heredados: Cree una VLAN dedicada y aislada y un SSID WPA2-only separado específicamente para estos dispositivos.
Implementar controles de acceso estrictos: Aplique reglas de firewall estrictas a esta VLAN heredada, evitando el movimiento lateral hacia la red corporativa segura WPA3.

Fase 4: Aplicación completa de WPA3

Una vez que la gran mayoría de la flota corporativa esté utilizando WPA3 con éxito y los dispositivos heredados estén segmentados, cambie el SSID corporativo principal a WPA3-Enterprise only.

Mejores prácticas para entornos empresariales

Implementar la tecnología es solo la mitad de la batalla; mantener su integridad requiere una disciplina operativa continua.

Automatizar la gestión del ciclo de vida de los certificados: La causa más común de fallo de EAP-TLS son los certificados caducados. Implemente procesos de renovación automatizados y mecanismos de alerta 90, 60 y 30 días antes de la caducidad del certificado del servidor RADIUS.
Garantizar la redundancia de RADIUS: Un único servidor RADIUS es un único punto de fallo. Implemente servidores RADIUS primarios y secundarios en ubicaciones geográficamente diversas, configurando una conmutación por error sin interrupciones en los controladores inalámbricos.
Separar las redes de invitados y corporativas: Nunca confunda las políticas de seguridad corporativas con el acceso de invitados. Las redes corporativas requieren WPA3-Enterprise con EAP-TLS. Las redes de invitados deben utilizar VLAN aisladas, gestionadas normalmente a través de captive portals. Las soluciones de Guest WiFi de Purple proporcionan un acceso de invitados seguro y conforme a la normativa, al tiempo que capturan valiosos WiFi Analytics .
Aprovechar OpenRoaming: Para una conectividad segura y sin interrupciones en diferentes ubicaciones, considere implementar Passpoint/Hotspot 2.0. Purple actúa como proveedor de identidad gratuito para servicios como OpenRoaming bajo la licencia Connect, facilitando un acceso seguro y sin fricciones sin comprometer los estándares de seguridad empresarial.

Resolución de problemas y mitigación de riesgos

Incluso con una planificación meticulosa, las implementaciones encuentran fricción. Aquí se presentan los modos de fallo comunes y las estrategias de mitigación.

Síntoma: Los clientes no pueden conectarse cuando el modo de transición está habilitado.

Causa raíz: Los controladores de cliente heredados a menudo fallan cuando encuentran la difusión obligatoria de PMF (Protected Management Frames) por parte del punto de acceso en modo de transición, incluso si están intentando una conexión WPA2. Mitigación: Actualice los controladores de la interfaz de red inalámbrica (NIC) del cliente. Si no hay actualizaciones disponibles, el dispositivo debe trasladarse al SSID WPA2-only heredado y aislado.

Síntoma: Fallos generalizados de autenticación en todos los dispositivos.

Causa raíz: El certificado del servidor RADIUS ha caducado, o el certificado de la Root CA ha sido revocado o eliminado de los almacenes de confianza del cliente. Mitigación: Renueve e implemente inmediatamente el certificado del servidor RADIUS. Revise las alertas de gestión automatizada del ciclo de vida para evitar la recurrencia.

Síntoma: Alta latencia durante el roaming entre puntos de acceso.

Causa raíz: 802.11r (Fast BSS Transition) está mal configurado o es incompatible con el método EAP específico en uso. Mitigación: Asegúrese de que 802.11r esté explícitamente habilitado y sea compatible tanto con el controlador WLAN como con los dispositivos cliente para el SSID WPA3. Pruebe el rendimiento del roaming durante las ventanas de mantenimiento.

ROI e impacto empresarial

La transición a WPA3-Enterprise requiere inversión en servicios profesionales, posibles actualizaciones de hardware e infraestructura PKI. Sin embargo, el retorno de la inversión se mide en mitigación de riesgos y cumplimiento normativo.

Para una gran cadena de Retail , el coste de una violación de datos que implique información de tarjetas de pago supera con creces los costes de implementación de WPA3. El cumplimiento de PCI DSS 4.0 requiere una encriptación y autenticación robustas; WPA3-Enterprise satisface directamente estos requisitos, agilizando las auditorías de cumplimiento y evitando posibles multas.

Además, la modernización de la infraestructura inalámbrica proporciona una base estable y de alto rendimiento para futuras iniciativas digitales, ya sea el despliegue de sensores IoT avanzados en Hospitality o la habilitación de sistemas de punto de venta móviles seguros. El impacto empresarial es una arquitectura de red resiliente, conforme a la normativa y preparada para el futuro.

Términos clave y definiciones

WPA3-Enterprise

The current standard for enterprise wireless security, mandating stronger encryption, protected management frames, and forward secrecy, typically deployed with 802.1X and RADIUS.

Required for compliance (PCI DSS, GDPR) and securing corporate data against modern cryptographic attacks.

EAP-TLS (Extensible Authentication Protocol-Transport Layer Security)

An authentication framework requiring both the client and the RADIUS server to present digital certificates to verify each other's identity.

The gold standard for WPA3-Enterprise authentication, eliminating the reliance on vulnerable user passwords.

PMF (Protected Management Frames)

A security standard (802.11w) that encrypts the control frames used for client association and disassociation.

Mandatory in WPA3, PMF prevents attackers from forging deauthentication packets to knock users off the network or execute man-in-the-middle attacks.

SAE (Simultaneous Authentication of Equals)

A secure key establishment protocol used in WPA3 that replaces the vulnerable 4-way handshake of WPA2.

SAE provides forward secrecy and protects against offline dictionary attacks, ensuring that even if a password is weak, the handshake cannot be brute-forced.

GCMP-256 (Galois/Counter Mode Protocol)

A highly secure, efficient encryption protocol utilizing 256-bit keys.

Mandated for the WPA3-Enterprise 192-bit security suite, required for environments handling highly sensitive data like government or financial records.

RADIUS (Remote Authentication Dial-In User Service)

A centralized networking protocol that provides Authentication, Authorization, and Accounting (AAA) management for users connecting to a network service.

The core backend server in a WPA3-Enterprise deployment that validates client certificates or credentials before granting network access.

Forward Secrecy

A cryptographic feature ensuring that session keys are ephemeral; compromising a long-term key in the future will not allow an attacker to decrypt past recorded sessions.

A critical enhancement in WPA3 provided by the SAE handshake, protecting historical data.

PKI (Public Key Infrastructure)

The framework of roles, policies, hardware, software, and procedures needed to create, manage, distribute, use, store, and revoke digital certificates.

The necessary prerequisite infrastructure for deploying EAP-TLS authentication in a WPA3-Enterprise environment.

Casos de éxito

A 200-room luxury hotel is upgrading its corporate network to WPA3-Enterprise. They have a mix of modern corporate laptops, iPads used by concierge staff, and legacy Wi-Fi-enabled door locks that only support WPA2. How should the network architect design the SSIDs and VLANs to ensure maximum security without breaking operational functionality?

The architect must employ network segmentation.

Create a primary corporate SSID ('HotelCorp_Secure') configured for WPA3-Enterprise only, utilizing EAP-TLS. Deploy certificates to all corporate laptops and iPads via the hotel's MDM solution. Assign this SSID to the primary corporate VLAN.
Create a secondary, hidden SSID ('Hotel_IoT_Legacy') configured for WPA2-Personal (PSK) or WPA2-Enterprise (if supported by the locks), utilizing a complex, rotated passphrase or MAC authentication bypass (MAB).
Assign the legacy SSID to a heavily restricted, isolated VLAN. Configure firewall rules to allow the door locks to communicate ONLY with the specific on-premise or cloud-based door management server, blocking all lateral movement to the corporate VLAN or the internet.

Notas de implementación: This approach correctly prioritizes security for capable devices while accommodating legacy hardware. Attempting to use WPA3 Transition Mode on a single SSID often fails because legacy IoT devices frequently crash when encountering mandatory PMF frames. Physical/logical segmentation is the only secure method for handling mixed-capability environments.

A public sector organization has deployed WPA3-Enterprise with EAP-TLS. On a Monday morning, no staff can connect to the wireless network. The wireless controller shows clients associating, but failing RADIUS authentication. What is the most likely cause, and what is the immediate remediation step?

The most likely cause is an expired RADIUS server certificate. Because EAP-TLS relies on mutual authentication, if the server presents an expired certificate, the clients will immediately reject the connection and terminate the handshake.

Immediate remediation: The IT team must generate a new Certificate Signing Request (CSR) from the RADIUS server, have it signed by the internal CA, and bind the new certificate to the EAP-TLS authentication policy on the RADIUS server. Services must then be restarted.

Notas de implementación: This scenario highlights the critical importance of certificate lifecycle management. EAP-TLS is highly secure but brittle if administrative processes fail. The organization must implement automated alerting for certificate expiration to prevent future outages.

Análisis de escenarios

Q1. You are the network architect for a large retail chain rolling out WPA3-Enterprise. During the pilot phase at three stores using WPA3 Transition Mode, several older barcode scanners frequently drop off the network and require manual reboots to reconnect. Modern tablets connect without issue. What is the most appropriate architectural response?

💡 Sugerencia:Consider how legacy wireless drivers handle unfamiliar management frames broadcast in Transition Mode.

Mostrar enfoque recomendado

The barcode scanners are likely crashing due to the mandatory Protected Management Frames (PMF) broadcast by the APs in Transition Mode. The appropriate response is to abandon Transition Mode for these devices. Create a dedicated, hidden WPA2-only SSID mapped to an isolated VLAN specifically for the scanners, and configure the primary corporate SSID to WPA3-Enterprise only for the modern tablets.

Q2. A CTO mandates the deployment of WPA3-Enterprise across all corporate offices within 60 days to meet new compliance requirements. The current environment uses WPA2-Enterprise with PEAP-MSCHAPv2 (username/password). The organization does not currently have an internal Certificate Authority (CA) or a Mobile Device Management (MDM) solution. Is this timeline realistic, and what is the critical path?

💡 Sugerencia:Evaluate the prerequisites for the recommended WPA3 authentication method (EAP-TLS).

Mostrar enfoque recomendado

The 60-day timeline is highly unrealistic. To properly implement WPA3-Enterprise, the organization should migrate to EAP-TLS to eliminate credential vulnerabilities. The critical path requires designing and deploying a PKI (Certificate Authority) and implementing an MDM solution to distribute client certificates. Building this infrastructure from scratch, testing it, and enrolling all corporate devices will almost certainly exceed 60 days. The architect must communicate this dependency to the CTO.

Q3. During a security audit, an examiner notes that your RADIUS servers are configured for EAP-TLS, but the 'Certificate Revocation List (CRL) checking' feature is disabled on the wireless controllers and RADIUS servers. Why is this a significant security finding in a WPA3 environment?

💡 Sugerencia:What happens if a corporate laptop is stolen, but its certificate has not yet expired?

Mostrar enfoque recomendado

Without CRL or OCSP checking enabled, the RADIUS server has no way of knowing if a presented certificate has been revoked by the CA prior to its natural expiration date. If a device is lost or an employee is terminated, their certificate must be revoked. If revocation checking is disabled, that compromised certificate can still be used to successfully authenticate and access the WPA3-Enterprise network, entirely defeating the purpose of mutual authentication.