How to Implement SCEP for Automated WiFi Certificate Enrollment

This guide explains how to implement SCEP (Simple Certificate Enrollment Protocol) for automated WiFi certificate enrollment across enterprise venues. It covers the full architectural blueprint - from PKI design and MDM integration to the mandatory three-step deployment sequence - and shows IT managers and network architects how to eliminate shared credentials, automate certificate lifecycle management, and satisfy PCI DSS and GDPR requirements at scale.

📖 10 min read📝 2,383 words🔧 2 worked examples❓ 4 practice questions📚 10 key definitions

Listen to this guide

View podcast transcript

INTRODUCTION AND CONTEXT - 0:00 to 1:00

Hello, and welcome to this technical briefing from Purple. Today we are unpacking SCEP, the Simple Certificate Enrollment Protocol, and how to implement it for automated WiFi certificate enrollment. If you are a network architect, an IT director, or managing infrastructure for large venues like retail chains, hospitals, or stadiums, this briefing is for you. We are cutting through the noise to discuss how to deploy EAP-TLS at scale, why SCEP is the right choice for device identity, and how you can practically deploy it in your environment. Let us get straight into it.

TECHNICAL DEEP-DIVE - 1:00 to 6:00

So, what exactly is the challenge we are solving here? In the world of enterprise WiFi security, EAP-TLS represents the gold standard. Unlike legacy methods such as PEAP or EAP-TTLS, which rely on user passwords, EAP-TLS mandates mutual certificate-based authentication. This means the client device must verify the network identity via a server certificate, and the network must verify the client identity via a unique client certificate.

Think about the vulnerability of passwords. They can be shared, phished, or stolen. In a sprawling enterprise environment, a compromised password can grant a bad actor access to your entire internal network. EAP-TLS eliminates this vector entirely. The authentication relies on X.509 certificates issued by a Public Key Infrastructure, or PKI.

But the core challenge with EAP-TLS is not the protocol itself. It is the logistics of getting unique client certificates onto thousands of devices, whether they are Windows laptops, iPads, or point-of-sale tablets. You cannot manually install certificates on thousands of devices. This is where Mobile Device Management platforms like Microsoft Intune or Jamf come into play. But how do you deliver those certificates securely?

You generally have two choices: PKCS or SCEP. Let me be absolutely clear on this. For WiFi authentication, you want SCEP. Here is why it matters. With SCEP, the MDM instructs the endpoint device to generate its own private key locally. That key stays locked in the device secure hardware. It never travels across the network. The device just sends a Certificate Signing Request to your Certificate Authority via a gateway, usually an NDES server.

Contrast that with PKCS, where the Certificate Authority generates the private key centrally and pushes it down over the network to the device. While PKCS has its place, say, for email encryption where you need key escrow, transmitting private keys over the network is a risk you do not need to take for network authentication. Keep the keys on the device. Use SCEP.

Now, let us talk implementation. If you take away one thing from this briefing, it is this rule of thumb: Trust before Authentication. You cannot just push a WiFi profile and expect it to work. There is a strict, three-step deployment sequence you must follow.

Step one: Deploy the Trusted Root Certificate. Before a device can ask for a client certificate, or trust your RADIUS server, it has to trust the issuing Certificate Authority. Push this profile first.

Step two: Configure and push the SCEP Certificate Profile. This tells the device how to talk to the SCEP gateway, what format to use for its subject name, and what the certificate is actually for. In this case, Client Authentication. You must link this profile to the Trusted Root you deployed in step one.

Step three: Deploy the 802.1X WiFi Profile. This is where you tie it all together. You specify the SSID, select WPA3-Enterprise, set the EAP type to EAP-TLS, and point it to the SCEP certificate for client authentication.

IMPLEMENTATION RECOMMENDATIONS AND PITFALLS - 6:00 to 8:00

Here is a major pitfall we see all the time. A client calls us and says, the certificates are on the device, but the WiFi profile shows an error in Intune. Almost every single time, this is a group targeting mismatch. If you assign the SCEP profile to a Users group, but assign the WiFi profile to a Devices group, the MDM cannot resolve the dependency. Match your targets exactly across all three profiles.

Let us look at a real-world scenario. Imagine a 200-room hotel. They have 150 managed iOS devices for housekeeping staff. Currently, they use a standard password network, and staff keep sharing the password with guests. It is a genuine operational headache. By migrating to WPA2-Enterprise with EAP-TLS via SCEP, the IT Director eliminates the password entirely. The iOS devices authenticate silently in the background using their certificates.

But what happens if a housekeeper loses a device, or leaves the company? Disabling their Active Directory account is not enough, because the certificate on that device is still cryptographically valid. This brings us to a critical security control: strict CRL checking. You must configure your RADIUS server to check the Certificate Revocation List. If a device goes missing, you revoke the certificate at the CA. The RADIUS server sees the revocation on the CRL and immediately blocks network access. Without strict CRL checking, your security posture is incomplete.

RAPID-FIRE Q&A - 8:00 to 9:00

Let us tackle a few rapid-fire questions we often hear from CTOs.

Question one: Is EAP-TLS required for WPA3 Enterprise? While WPA3 Enterprise supports other methods, EAP-TLS is strongly recommended and is required if you are implementing the WPA3 Enterprise 192-bit security suite, often called Suite B.

Question two: Can we use public certificates for clients? No. You must use a private internal CA for client certificates. Public CAs are for public-facing web servers. Your internal RADIUS server needs to trust your specific internal Root CA to validate your corporate devices.

Question three: How does this fit with OpenRoaming? OpenRoaming relies on Passpoint and 802.1X. Purple acts as a free identity provider for services like OpenRoaming under the Connect licence, facilitating seamless, secure roaming across venues using underlying certificate and identity frameworks.

SUMMARY AND NEXT STEPS - 9:00 to 10:00

To wrap up, transitioning to automated SCEP certificate deployment delivers real, measurable returns. You will see a 70 to 80 percent reduction in WiFi-related helpdesk tickets, because users are not getting locked out or typing passwords incorrectly. More importantly, you eliminate the risk of credential harvesting, ensuring you meet compliance frameworks like PCI DSS and GDPR.

Automating enterprise WiFi security is not just about locking things down. It is about making the secure path the easiest path for your users. Your next steps: audit your current 802.1X deployment. If you are still relying on passwords, design your PKI and plan the migration to EAP-TLS with SCEP. Check whether your RADIUS server is enforcing strict CRL or OCSP checking. And verify that your three deployment profiles all target the same group.

Thank you for listening to this technical briefing from Purple. For more detailed deployment guides and to understand how our analytics and identity platforms can integrate with your secure networks, visit purple dot ai.

Key Takeaways

✓SCEP (RFC 8894) automates X.509 certificate enrollment for managed devices. The private key is generated locally on the device and never transmitted over the network - this is the core security advantage over PKCS.
✓For 802.1X EAP-TLS WiFi authentication, always use SCEP. Reserve PKCS for use cases requiring key escrow, such as S/MIME email encryption.
✓The deployment sequence is non-negotiable: Trusted Root Certificate first, then SCEP Certificate Profile, then 802.1X WiFi Profile. All three profiles must target the exact same Azure AD group.
✓Strict CRL or OCSP checking on the RADIUS server is mandatory. Disabling an AD account does not revoke a certificate. Revoke at the CA and ensure the RADIUS server acts on it.
✓EAP-TLS satisfies PCI DSS 4.0 Requirement 8.6 for multi-factor authentication at the network layer and is required for WPA3 Enterprise 192-bit (Suite B) deployments.
✓Organisations migrating from password-based WiFi to EAP-TLS with SCEP typically report a 70-80% reduction in WiFi-related helpdesk tickets (Purple internal data, 2024).
✓For distributed estates (hotel groups, retail chains, multi-site public-sector), cloud-hosted SCEP gateways and managed PKI services eliminate the on-premises NDES infrastructure requirement without compromising security.

Executive summary

For venue operators running Guest WiFi across hotels, retail estates, stadiums, and conference centres, relying on pre-shared keys or basic captive portals for staff network access is a security liability. Modern network architecture demands 802.1X authentication using EAP-TLS (Extensible Authentication Protocol - Transport Layer Security), ensuring every device is cryptographically verified before it touches the network. The challenge is distribution: how do you deploy unique client certificates to thousands of Windows, iOS, and Android devices without burying your helpdesk?

The answer is SCEP - the Simple Certificate Enrollment Protocol. Formalised by the IETF as RFC 8894 in 2020, SCEP automates certificate enrollment across managed device fleets. When integrated with an MDM platform such as Microsoft Intune or Jamf, SCEP delivers zero-touch certificate provisioning: devices request, receive, and renew their own certificates without any IT intervention. The private key is generated locally on the device and never transmitted across the network - a fundamental security advantage over PKCS-based delivery.

This guide walks through the complete SCEP implementation workflow: PKI architecture, NDES gateway configuration, the mandatory three-step MDM deployment sequence, and the operational controls - particularly CRL checking and group targeting - that determine whether a rollout succeeds or stalls. Two real-world scenarios illustrate the approach in hospitality and retail environments. Purple operates across 80,000+ live venues and 350 million unique users; the patterns described here reflect what works at that scale.

Technical deep-dive

What SCEP actually does

SCEP sits between your MDM platform and your Certificate Authority (CA). It provides a standardised HTTP-based mechanism for devices to request, receive, and renew X.509 certificates without requiring a domain-joined credential or manual administrator involvement. The protocol was originally developed in the early 2000s and gained widespread adoption in enterprise MDM environments before the IETF formally published it as RFC 8894.

The six-step enrollment flow works as follows. First, the managed device connects to the SCEP gateway URL pre-configured in its MDM profile. Second, the device generates a private/public key pair locally and creates a Certificate Signing Request (CSR). Third, the SCEP gateway validates the device's authorisation using a challenge password or OTP embedded in the MDM policy. Fourth, the gateway forwards the validated CSR to the CA. Fifth, the CA signs the certificate and returns it to the gateway. Sixth, the gateway delivers the signed certificate to the device. Future renewals follow the same automated path - the device re-enrolls before expiry without any user or administrator action.

SCEP vs PKCS: the decision that matters

Microsoft Intune and most MDM platforms support two certificate delivery mechanisms: SCEP and PKCS. The distinction is architectural, not cosmetic.

With SCEP, the private key is generated on the device and stays there. The CA never sees it. The device's TPM (on Windows) or Secure Enclave (on iOS/macOS) protects the key at the hardware level. With PKCS, the CA generates the key pair centrally and transmits it to the device over the network. The CA retains a copy, enabling key escrow - which is useful for S/MIME email encryption but introduces unnecessary risk for network authentication.

For 802.1X WiFi authentication, use SCEP. The private key never leaves the device. That is the rule.

Criterion	SCEP	PKCS
Private key generated on	Device	CA (centrally)
Private key transmitted over network	Never	Yes
Supports TPM / Secure Enclave	Yes	No
Recommended for WiFi auth	Yes	No
Recommended for email encryption (S/MIME)	No	Yes
Key escrow possible	No	Yes

802.1X and EAP-TLS: the authentication framework

IEEE 802.1X is the port-based network access control standard that underpins enterprise WiFi security. It defines three roles: the supplicant (the client device), the authenticator (the access point - Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, or Fortinet), and the authentication server (a RADIUS server such as Microsoft NPS, FreeRADIUS, or Cisco ISE).

EAP-TLS is the most secure EAP method for 802.1X. Both sides present certificates: the RADIUS server presents its certificate to the client, and the client presents its SCEP-provisioned certificate to the RADIUS server. Neither side can impersonate the other without a valid, non-revoked certificate from the trusted CA hierarchy. This mutual authentication model eliminates credential theft, Evil Twin attacks, and rogue access point risks in a single architectural decision.

EAP-TLS satisfies PCI DSS 4.0 Requirement 8.6 for multi-factor authentication at the network layer. It is required for WPA3 Enterprise 192-bit (Suite B) deployments. For any wireless network in scope for cardholder data processing - retail point-of-sale, hotel front desk, stadium ticketing - EAP-TLS is the correct choice.

For a deeper look at secure WiFi architecture and how certificate-based authentication fits within a broader security posture, see our essential guide.

Implementation guide

The deployment sequence is non-negotiable. Intune and Jamf resolve profile dependencies in order: the WiFi profile depends on the SCEP profile, which depends on the Trusted Root profile. Deploy them out of sequence and the WiFi profile will fail to apply.

Step 1: Design your PKI

Before you touch an MDM console, design your certificate hierarchy. A two-tier PKI is standard: an offline root CA and an online issuing CA. The root CA's private key is the master trust anchor for your entire certificate infrastructure - keep it air-gapped. The issuing CA handles day-to-day certificate issuance and publishes the Certificate Revocation List (CRL) and OCSP responder.

For most enterprise venue deployments, Microsoft Active Directory Certificate Services (AD CS) running on Windows Server provides the issuing CA. Cloud-hosted PKI services from providers such as SCEPman or SecureW2 eliminate the on-premises infrastructure requirement entirely and are worth evaluating for distributed estate deployments across hotel groups, retail chains, or multi-site public-sector organisations.

Step 2: Deploy the NDES server (or cloud SCEP gateway)

NDES (Network Device Enrollment Service) is the Microsoft Windows Server role that acts as the SCEP gateway between your MDM and your CA. Key configuration requirements:

Publish the NDES URL externally via Azure AD Application Proxy (or equivalent reverse proxy). This allows remote devices to enroll before they arrive on-site, without opening inbound firewall ports.
The NDES service account requires Read and Enroll permissions on the CA certificate template.
Configure the certificate template with Key Usage set to Digital Signature and Key Encipherment, and Extended Key Usage set to Client Authentication (OID: 1.3.6.1.5.5.7.3.2).
Set an appropriate certificate validity period. One year is standard for client certificates; two years is acceptable for device certificates in stable fleets.

If you prefer to avoid on-premises NDES infrastructure, cloud SCEP gateways integrate directly with Intune and your CA via API, removing the IIS dependency entirely.

Step 3: Deploy the Trusted Root Certificate profile

In your MDM platform, create a Trusted Certificate profile and upload your Root CA certificate (and any Intermediate CA certificates) as .cer files. Deploy this profile to your target device groups before any other certificate or WiFi profiles. Without this step, devices cannot validate the RADIUS server's certificate during the EAP-TLS handshake, and they cannot trust the issuing CA when requesting their own SCEP certificate.

Rule of thumb: Always target the same Azure AD group (either Users or Devices) across all three related profiles. A mismatch here is the single most common cause of WiFi profile deployment failures.

Step 4: Configure the SCEP Certificate profile

Create a SCEP certificate configuration profile in your MDM:

Subject name format: For user-driven authentication, use CN={{UserPrincipalName}}. For device authentication (recommended for shared devices and IoT), use CN={{AAD_Device_ID}}.
Key usage: Digital Signature, Key Encipherment.
Extended key usage: Client Authentication (OID: 1.3.6.1.5.5.7.3.2).
SCEP server URL: The externally published NDES URL.
Root certificate: Link to the Trusted Root profile from Step 3.
Certificate validity period: Match the template configured on the CA.

Step 5: Deploy the 802.1X WiFi profile

Create a WiFi configuration profile:

SSID: Enter the network name exactly as broadcast by your access points.
Security type: WPA2-Enterprise or WPA3-Enterprise.
EAP type: EAP-TLS.
Client authentication certificate: Select the SCEP certificate profile from Step 4.
Server validation: Specify the Trusted Root certificate from Step 3 and enter the expected RADIUS server name. This prevents devices from connecting to rogue access points presenting fraudulent certificates.

Best practices

Enforce strict CRL checking on your RADIUS server

Certificate revocation is the operational control that closes the gap between disabling an account and blocking network access. When a device is lost, stolen, or an employee leaves, disable the AD account and revoke the certificate at the CA. Your RADIUS server must be configured to check the CRL on every authentication attempt. If the CRL is unavailable - because the CDP (CRL Distribution Point) is unreachable - most RADIUS servers default to failing open, which is a security risk. Ensure your CDPs are highly available and that your RADIUS server is configured to fail closed if the CRL cannot be fetched.

For real-time revocation, configure OCSP (Online Certificate Status Protocol) in addition to CRL. OCSP provides per-certificate status responses without requiring the RADIUS server to download and parse the entire CRL.

Use device certificates for shared and IoT devices

For shared devices - hotel housekeeping tablets, retail POS terminals, stadium access control readers - use device certificates rather than user certificates. Device certificates are tied to the machine identity, not a user account. This means the device authenticates regardless of which user is logged in, and revocation is tied to the device record rather than an employee's departure.

For retail deployments, device certificates on POS hardware also satisfy the PCI DSS requirement for network-layer device identity without introducing user-credential complexity at the point of sale.

Automate certificate renewal

SCEP supports automatic renewal: the MDM instructs the device to re-enroll before the certificate expires. Configure your SCEP profile to trigger renewal at 20% of the certificate's remaining validity period. For a one-year certificate, renewal begins approximately 73 days before expiry. This window provides enough time to resolve any renewal failures before the certificate expires and devices lose network access.

Expired certificates causing mass authentication failures are the most common operational incident in 802.1X deployments. Automated renewal via SCEP eliminates this risk entirely.

Segment networks by certificate attribute

RADIUS servers can read certificate attributes - Subject, SAN, or custom OIDs - and use them to assign devices to VLANs dynamically. A housekeeping tablet with a certificate issued from the HousekeepingDevices template lands on the housekeeping VLAN. A POS terminal with a certificate from the RetailPOS template lands on the PCI-scoped VLAN. This is cryptographically enforced network segmentation - far more reliable than SSID-based or MAC-based approaches.

For hospitality operators running Guest WiFi alongside Staff WiFi on the same physical infrastructure, VLAN assignment via certificate attributes ensures guests and staff are always on separate network segments, regardless of which SSID a device connects to.

Troubleshooting & risk mitigation

WiFi profile shows 'Error' or 'Not Applicable' in Intune

Root cause: Group targeting mismatch. The SCEP profile is assigned to a different group than the WiFi profile. Intune cannot resolve the certificate dependency.

Fix: Audit all three profiles (Trusted Root, SCEP, WiFi). Ensure they are all assigned to the exact same Azure AD group. If you are deploying to Users, all three profiles must target a Users group. If deploying to Devices, all three must target a Devices group.

NDES returns HTTP 403 errors

Root cause: The Intune Certificate Connector service account lacks Read or Enroll permissions on the CA certificate template, or firewall URL filtering is blocking SCEP query strings.

Fix: Verify the connector account has Read and Enroll permissions on the template in the CA console. Check firewall logs for blocked requests containing ?operation=GetCACaps or ?operation=PKIOperation. These query strings must pass through without modification.

Devices fail to renew certificates before expiry

Root cause: The SCEP renewal window is too short, or the NDES server is unreachable at the time of renewal.

Fix: Set the renewal threshold to 20% of certificate validity. Ensure the NDES URL is published via a highly available reverse proxy. Monitor NDES IIS logs for renewal request failures and alert on them proactively.

RADIUS rejects valid certificates

Root cause: The RADIUS server's trusted CA store does not include the issuing CA certificate, or the CRL is stale.

Fix: Import the full CA chain (Root CA + Issuing CA) into the RADIUS server's trusted store. Verify the CRL is being fetched successfully and that the CDP URL is reachable from the RADIUS server. Check the CRL's next-update timestamp - if it has passed, the CA needs to publish a new CRL.

For broader network performance considerations alongside security, see our bandwidth management guide .

ROI & business impact

The business case for SCEP-based certificate enrollment is straightforward. Password-based WiFi generates a predictable volume of helpdesk tickets: password expirations, lockouts, staff sharing credentials with guests, and onboarding friction for new starters. Certificate-based authentication is invisible to the end user. Devices connect automatically. There are no passwords to expire, share, or forget.

Organisations that migrate from password-based WiFi to EAP-TLS with SCEP typically report a 70-80% reduction in WiFi-related helpdesk tickets (Purple internal data, 2024, based on deployments across hospitality and retail estates). The helpdesk saving alone often justifies the implementation cost within the first year.

The compliance impact is equally concrete. EAP-TLS satisfies PCI DSS 4.0 Requirement 8.6 for multi-factor authentication at the network layer. For healthcare environments, it aligns with HIPAA technical safeguard requirements for wireless network access. For public-sector organisations, it supports NCSC Cyber Essentials Plus certification requirements for network access control.

For transport operators - rail franchises, airport operators, bus networks - certificate-based authentication on staff devices ensures that operational networks carrying safety-critical data are isolated from passenger WiFi and protected against credential-based attacks.

Purple's WiFi Analytics platform integrates with 802.1X-secured networks to deliver first-party data insights without compromising the security posture of the underlying infrastructure. The 29 billion data points collected across Purple's network demonstrate that security and analytics are complementary, not competing, objectives.

For feedback and experience management alongside your secure network deployment, see our venue feedback playbook .

Key Definitions

SCEP (Simple Certificate Enrollment Protocol)

An IETF-standardised protocol (RFC 8894) that automates X.509 certificate enrollment for managed devices. The device generates its own private key locally and sends only a Certificate Signing Request to the CA via a gateway. The private key never leaves the device.

IT teams encounter SCEP when configuring MDM platforms (Intune, Jamf) to deploy WiFi authentication certificates at scale. It is the recommended mechanism for 802.1X EAP-TLS deployments because the private key is hardware-protected on the endpoint.

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

The most secure 802.1X authentication method. Both the client device and the RADIUS server present X.509 certificates. Neither side can authenticate without a valid, non-revoked certificate from the trusted CA hierarchy.

EAP-TLS is the target authentication protocol that SCEP certificate deployment enables. It satisfies PCI DSS 4.0 Requirement 8.6 and is required for WPA3 Enterprise 192-bit (Suite B) deployments.

PKCS (Public Key Cryptography Standards)

A certificate delivery mechanism where the CA generates both the public and private key pair centrally and transmits them to the endpoint. The CA retains a copy of the private key, enabling key escrow.

IT teams choose between SCEP and PKCS when configuring certificate profiles in Intune. PKCS is appropriate for S/MIME email encryption where key escrow is required. It is not recommended for WiFi authentication because the private key is transmitted over the network.

NDES (Network Device Enrollment Service)

A Microsoft Windows Server role that acts as the SCEP gateway between an MDM platform and a Certificate Authority. It validates device enrollment requests and forwards CSRs to the CA.

NDES is a required infrastructure component for on-premises SCEP deployments with Microsoft Intune. It must be published externally via an application proxy to allow remote devices to enroll. Cloud SCEP gateways are an alternative that eliminates the on-premises NDES dependency.

CRL (Certificate Revocation List)

A list published by the CA containing the serial numbers of certificates that have been revoked before their expiry date. RADIUS servers check the CRL to ensure devices with revoked certificates cannot authenticate.

CRL checking is the operational control that enforces certificate revocation. IT teams must configure their RADIUS server to check the CRL on every authentication attempt and ensure the CRL Distribution Point (CDP) is highly available.

802.1X

An IEEE standard for port-based network access control. It defines the three-party authentication framework (supplicant, authenticator, authentication server) used in enterprise WiFi and wired networks.

802.1X is the framework within which EAP-TLS and SCEP operate. IT teams encounter it when configuring WPA2-Enterprise or WPA3-Enterprise SSIDs and when setting up RADIUS server policies.

RADIUS (Remote Authentication Dial-In User Service)

A networking protocol that provides centralised authentication, authorisation, and accounting (AAA) for network access. In 802.1X deployments, the RADIUS server validates client certificates and enforces VLAN assignment policies.

The RADIUS server is the authentication decision point in every 802.1X deployment. Common implementations include Microsoft NPS, FreeRADIUS, and Cisco ISE. It must be configured with the trusted CA chain and strict CRL or OCSP checking.

CSR (Certificate Signing Request)

A block of encoded text generated by a device that contains the device's public key and identity information. The device sends the CSR to the CA (via the SCEP gateway) to request a signed certificate. The corresponding private key is generated and retained on the device.

The CSR is the core artifact in the SCEP enrollment flow. IT teams configure the CSR format (subject name, key usage, EKU) in the SCEP certificate profile within their MDM platform.

PKI (Public Key Infrastructure)

The combination of hardware, software, policies, and procedures required to create, manage, distribute, and revoke digital certificates. A standard enterprise PKI consists of an offline root CA and an online issuing CA.

PKI is the prerequisite for any EAP-TLS deployment. IT teams must design and deploy a two-tier CA hierarchy before configuring SCEP. Cloud-hosted PKI services reduce the infrastructure burden for distributed estate deployments.

VLAN (Virtual Local Area Network)

A logical network segment that isolates traffic at Layer 2. In 802.1X deployments, RADIUS servers assign devices to VLANs dynamically based on certificate attributes, user identity, or policy.

VLAN assignment via RADIUS is the mechanism that enforces network segmentation in enterprise WiFi. IT teams use it to separate POS devices onto PCI-scoped VLANs, guest devices onto internet-only VLANs, and staff devices onto corporate VLANs - all from a single physical infrastructure.

Worked Examples

A 200-room Premier Inn property needs to deploy secure WiFi for 150 iOS housekeeping devices. Staff are currently sharing a WPA2-Personal password with guests, creating a compliance and operational risk. The IT Director needs to eliminate the shared password without disrupting daily operations.

The IT Director implements a Jamf-driven SCEP deployment in three phases. Phase one: the Root CA certificate is pushed to all 150 iOS devices via a Jamf Trusted Certificate profile, targeting the 'Housekeeping Devices' smart group. Phase two: a SCEP certificate profile is deployed, directing devices to an Azure AD App Proxy-published NDES server. The subject name uses CN={{SERIALNUMBER}} to tie the certificate to the device hardware. Phase three: a WPA2-Enterprise WiFi profile is pushed, specifying EAP-TLS and linking to the SCEP certificate. Devices authenticate silently. The shared password SSID is decommissioned. The RADIUS server is configured with strict CRL checking and VLAN assignment: housekeeping devices land on VLAN 20 (operations), guest devices on VLAN 10 (internet-only).

Examiner's Commentary: The key design decisions here are device certificates (not user certificates) for shared hardware, and VLAN assignment via certificate attributes rather than SSID. This means a device that somehow connects to the guest SSID still lands on the correct VLAN. The CRL checking configuration is non-negotiable: when a housekeeper leaves, the device certificate is revoked at the CA, and the RADIUS server blocks access within the CRL refresh interval - typically 15 minutes with OCSP, or up to one hour with CRL.

A retail chain with 500 locations needs to secure corporate WiFi for Windows POS tablets running payment processing software. PCI DSS 4.0 compliance requires multi-factor authentication at the network layer. The current WPA2-Personal setup fails the PCI DSS Requirement 8.6 assessment.

The network architect deploys EAP-TLS via Microsoft Intune and SCEP across all 500 locations. The deployment uses device certificates with CN={{AAD_Device_ID}} as the subject name, tying each certificate to the Intune device record. The three-profile sequence (Trusted Root, SCEP, WiFi) is deployed to the 'POS Devices' Azure AD group - the same group across all three profiles. The RADIUS server assigns POS devices to a dedicated PCI-scoped VLAN (VLAN 100) based on the certificate's issuing template. The CRL is published to a highly available CDN-hosted endpoint with a four-hour validity window. OCSP is enabled for real-time revocation checking. The deployment is validated against PCI DSS 4.0 Requirement 8.6 by the QSA.

Examiner's Commentary: The PCI DSS alignment is achieved by the combination of EAP-TLS (something you have - the certificate) and the device identity bound to the Intune record (something you are - the enrolled managed device). The VLAN assignment via certificate template ensures POS devices are always on the PCI-scoped network segment, regardless of physical location across the 500-site estate. The CDN-hosted CRL endpoint is a critical reliability decision: if the CRL is unreachable, authentication fails, causing a site-wide outage. High availability for the CRL is as important as high availability for the RADIUS server itself.

Practice Questions

Q1. You have deployed Trusted Root and SCEP certificate profiles to the 'All Staff' user group in Intune. You then deploy the WiFi profile to the 'Corporate Devices' device group. Devices receive the certificates but the WiFi profile shows 'Error' in the Intune console. What is the most likely cause, and how do you fix it?

Hint: Consider how Intune resolves dependencies between profiles and what happens when profiles target different group types.

View model answer

The root cause is a group targeting mismatch. The WiFi profile depends on the SCEP profile, which depends on the Trusted Root profile. Intune cannot resolve these dependencies when the profiles target different group types (Users vs Devices). Fix: redeploy all three profiles to the same group. If the WiFi profile targets 'Corporate Devices' (a device group), the SCEP and Trusted Root profiles must also target 'Corporate Devices'. Alternatively, move all three to a user group if user-based authentication is required.

Q2. A hotel housekeeper's iPad is reported stolen. You immediately disable the housekeeper's Active Directory account. The next morning, the stolen iPad is still connecting to the hotel's WPA2-Enterprise network. Why, and what two actions do you take to prevent this?

Hint: Think about what the RADIUS server actually validates during EAP-TLS authentication, and what controls govern certificate validity.

View model answer

Disabling the AD account does not revoke the client certificate stored on the iPad. The RADIUS server validates the certificate, not the AD account status, during EAP-TLS authentication. The two required actions are: (1) revoke the device certificate at the CA - this adds the certificate serial number to the CRL; (2) ensure the RADIUS server is configured with strict CRL checking so it fetches the updated CRL and rejects the revoked certificate on the next authentication attempt. For faster revocation, configure OCSP on the RADIUS server for real-time certificate status checks.

Q3. A retail chain is deploying 802.1X WiFi to 500 POS locations. The security architect proposes using PKCS certificate delivery instead of SCEP to avoid deploying an NDES server. The QSA reviewing the PCI DSS 4.0 assessment raises a concern. What is the concern, and what is the correct recommendation?

Hint: Consider what PCI DSS says about private key handling and what PKCS does with the private key during delivery.

View model answer

The QSA's concern is that PKCS transmits the private key over the network from the CA to the device. PCI DSS 4.0 Requirement 3.5 requires that private keys used for authentication are protected against disclosure. Transmitting the private key over the network - even encrypted - introduces a risk that SCEP eliminates entirely. The correct recommendation is to use SCEP, where the private key is generated on the POS device and never leaves it. To avoid on-premises NDES infrastructure, the architect should evaluate a cloud SCEP gateway service that integrates directly with Intune and the CA via API.

Q4. You are designing a WiFi network for a large conference centre that hosts 50+ events per year. Staff devices need to be on a secure 802.1X network. You want to ensure that if a contractor's device is compromised, it can be isolated from the network within 15 minutes. What certificate revocation mechanism do you configure, and why?

Hint: Compare CRL and OCSP in terms of revocation latency and what determines how quickly a RADIUS server acts on a revocation.

View model answer

Configure OCSP (Online Certificate Status Protocol) on the RADIUS server. CRL-based revocation has a latency determined by the CRL's validity period - typically one to 24 hours - meaning a revoked certificate may still authenticate until the RADIUS server fetches the next CRL. OCSP provides real-time per-certificate status responses: when a certificate is revoked at the CA, the OCSP responder immediately returns a 'revoked' status on the next query. With OCSP configured on the RADIUS server, a revoked contractor certificate is blocked on the next authentication attempt, typically within seconds. Ensure the OCSP responder is highly available - if it is unreachable and the RADIUS server is configured to fail closed, all authentications will fail.

Continue reading in this series

Why Is My Guest WiFi Not Connecting? Troubleshooting Captive Portal Issues

This authoritative technical reference guide explains the underlying mechanics of captive portal detection and details the six primary failure modes that prevent guest WiFi from connecting. It provides IT managers and network architects with a practical troubleshooting framework to resolve HTTP redirect issues, DNS conflicts, and MAC randomisation challenges.

Why Is My Guest WiFi Not Connecting? Troubleshooting Captive Portal Issues

GDPR and Guest WiFi: Compliance Guide for Venue Marketers and IT

This guide provides IT managers and venue operators with a practical framework for ensuring Guest WiFi services are fully GDPR compliant. It covers technical architecture, consent mechanics, data retention, and how to transform compliance into a secure first-party data asset.