Secure network: certificates, identity and PasspointComparisons
SCEP vs ACME for WiFi certificates: which enrolment protocol to use
You will be able to choose an enrolment protocol per platform: ACME with device attestation for managed Apple fleets, SCEP with a per-request challenge for Windows and Android. You will also see how to migrate one platform at a time while Purple's cloud RADIUS validates EAP-TLS certificates from either path, with no...
14 min read

Watch the explainer
Enrol Apple devices with ACME and device attestation (RFC 8555 with the device-attest-01 challenge) where your MDM supports it. Keep SCEP (RFC 8894) for Windows and Android fleets for now. The choice flips on one question: do you need proof the key lives in genuine hardware? Purple's cloud RADIUS validates EAP-TLS certificates from either path.
SCEP or ACME: the short answer for WiFi certificates
SCEP and ACME solve the same problem. Both get a certificate onto a managed device without anyone copying files by hand. Both also end in the same place. The device presents its certificate over EAP-TLS, defined in RFC 5216, and your RADIUS server checks it. The difference is how the certificate authority (CA) decides a request is genuine.
SCEP, the Simple Certificate Enrolment Protocol in RFC 8894, trusts a challenge password. ACME, the Automated Certificate Management Environment in RFC 8555, can trust a signed statement from the device hardware. That second model comes from the ACME device attestation extension. At the time of writing, the extension is still an IETF Internet-Draft.
The verdict for a Purple estate is a split by platform. Use attested ACME on Apple fleets where your MDM supports the ACME payload. Keep SCEP on Windows and Android, where SCEP remains the certificate profile most MDMs document.
The verdict depends on one condition. Your network side must not care which protocol issued the certificate. Purple's cloud RADIUS validates EAP-TLS and looks up identity either way, so you can migrate one platform at a time. If your RADIUS layer were tied to a single enrolment path, the decision would be much harder.
What we compared, and why these criteria decide it
We scored SCEP and ACME on eight criteria. Each one changes either your security posture or your running cost on a multi-site estate. We used only each option's own public material: the RFCs, the IETF draft, Microsoft Intune documentation and Apple Platform Deployment documentation. Where a source did not document a behaviour, we left it out.
- Standard status. A published RFC is stable. A draft can still change before your CA and MDM settle on it.
- What the CA trusts. This is the core security difference. It decides what an attacker needs to obtain a valid WiFi certificate.
- Proof of a hardware key. A key that cannot leave the device cannot be copied to a second laptop.
- Platform reach. A protocol your MDM cannot deliver to half your fleet is not an option for that half.
- Servers you run. Every on-premises server means patching, monitoring and an out-of-hours outage risk.
- Renewal. Certificates expire. Silent renewal separates a quiet month from a helpdesk spike.
- Revocation. When someone leaves or loses a device, how fast does their access go?
- Network impact. Whether you touch SSIDs or access points on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist or Ubiquiti UniFi.
We did not score price, because neither protocol carries one. Cost sits with the CA, the MDM and the servers around them. The cost section below covers how each of those is structured.
How do SCEP and ACME compare, criterion by criterion?
The matrix scores both protocols and shows what the Purple Access secure network adds at the RADIUS layer. Purple is not a third enrolment protocol. It is the layer that consumes the certificate either protocol delivers.
{"caption":"SCEP vs ACME for WiFi certificates, scored from each protocol's own specification and vendor documentation","asOf":"2026-06-10","columns":[{"key":"c","label":"Criterion"},{"key":"s","label":"SCEP (RFC 8894)"},{"key":"a","label":"ACME with device attestation"},{"key":"p","label":"Purple Access secure network","highlight":true}],"rows":[["Standard status","Informational RFC, published 2020","RFC 8555 Proposed Standard; attestation is an IETF draft","EAP-TLS (RFC 5216) at cloud RADIUS"],["What the CA trusts","A challenge password delivered by the MDM","A vendor-signed attestation via device-attest-01","Certificate chain plus identity in your IdP"],["Proof of hardware key","None in the protocol","Yes, on supported Apple devices","Validates either; attested keys add assurance"],["Platform reach","Windows, macOS, iOS, iPadOS, Android via most MDMs","Apple platforms with an ACME-capable MDM","Any 802.1X client with a trusted certificate"],["Server you run","SCEP endpoint, e.g. Microsoft NDES plus connector","ACME endpoint at a CA that supports attestation","No RADIUS servers: cloud RADIUS"],["Renewal","MDM re-enrols before expiry","MDM places a new ACME order","No SSID change on renewal"],["Revocation","No revoke operation; revoke at the CA","revokeCert resource defined in RFC 8555","Leaver disabled in IdP loses access"],["Access point changes","None","None","None: hardware-agnostic"]],"footnote":"Sources: RFC 8894, RFC 8555, draft-ietf-acme-device-attest, Microsoft Intune and Apple Platform Deployment documentation. The Purple column describes Purple's own product scope.","download":{"filename":"scep-vs-acme-wifi-certificates.csv"}}
Read the matrix in two halves. The top four rows are where the protocols differ in substance. The bottom four show that, once a certificate sits on the device, the network sees the same thing.
Where do SCEP and ACME actually differ for WiFi?
The SCEP challenge password is the weak point
SCEP authorises a request with a challenge password carried in the certificate signing request. The CA treats that password as proof the requester is entitled to a certificate. A static, shared password therefore works like a credential. Anyone who reads it from a profile or a log can request a certificate.
Modern MDMs narrow that gap. Microsoft Intune, for example, generates a unique challenge per request. The Certificate Connector for Microsoft Intune validates it before the CA issues. That closes the shared-secret problem. It does not tell the CA anything about where the private key lives.
{"tone":"warning","title":"A static SCEP challenge is a credential","text":"Anyone holding a static challenge can request a WiFi certificate your RADIUS will accept. Use a per-request challenge and treat the SCEP endpoint as an exposed enrolment service."}
Attestation changes what the CA knows
With ACME device attestation, the device answers a device-attest-01 challenge. It returns an attestation statement signed by the platform vendor. On Apple devices, that statement comes from Apple and covers a key generated in the Secure Enclave. The CA can verify that the key is hardware-bound. It can also check that identifiers such as the serial number match the device it expected. Apple calls this managed device attestation.
That is a different promise from SCEP. SCEP can still place the key in hardware. Intune's Windows SCEP profile, for example, lets you enrol to the Trusted Platform Module (TPM) key storage provider. But the CA has to take that on trust. ACME lets the CA prove it. For why a hardware-bound key cannot be copied, see TPM-backed WiFi certificates.
Platform reach is where SCEP still wins
SCEP is the certificate profile most MDMs document across Windows, macOS, iOS, iPadOS and Android. Microsoft Intune documents SCEP certificate profiles for all of those platforms. That breadth matters on a multi-site estate with a mixed fleet.
Attested ACME is narrower today. Apple documents it for its own platforms. Your MDM must also support the ACME payload with attestation switched on. For Windows and Android, check your MDM's own documentation before you plan on ACME. Our comparison of MDM WiFi certificate profiles sets out what each MDM documents.
Renewal is close to a draw
Both protocols renew without anyone touching the device. With SCEP, the MDM re-enrols when a certificate reaches its renewal threshold. With ACME, the MDM triggers a new order and the device repeats the attestation.
The practical difference is where failures surface. A SCEP renewal fails if your SCEP endpoint or connector is down. An ACME renewal fails if the CA's ACME endpoint or the attestation step cannot complete. Monitor whichever dependency you own.
Revocation is where identity matters more than protocol
RFC 8555 defines a revokeCert resource, so ACME can revoke through the protocol itself. SCEP defines no revocation request. You revoke at the CA and publish the change through a certificate revocation list (CRL) or OCSP, the Online Certificate Status Protocol. Either way, revocation only bites if your RADIUS service checks it.
Purple adds a second control that does not depend on revocation lists. Each certificate maps to an identity in Microsoft Entra ID, Okta or Google Workspace. Disable a leaver's account and their WiFi access goes with it. Joiners, movers and leavers are handled where you already manage them.
Where does Purple fit between SCEP and ACME?
Purple Access runs three networks on the access points you already own: open, secure and xPSK. SCEP and ACME both belong on the secure network. There, devices authenticate with EAP-TLS against Purple's cloud RADIUS, and identity sets the VLAN.
{"kind":"lanes","direction":"lr","caption":"SCEP and ACME change the MDM and CA lanes; the network lane stays the same","alt":"Two enrolment paths, SCEP and ACME, both deliver a certificate to the device, which then authenticates over EAP-TLS to Purple cloud RADIUS where identity sets the VLAN.","lanes":[{"id":"mdm","label":"MDM"},{"id":"dev","label":"Device"},{"id":"ca","label":"Certificate authority"},{"id":"net","label":"Network"}],"nodes":[{"id":"m1","label":"SCEP profile pushed","sub":"Per-request challenge","lane":"mdm","tone":"neutral"},{"id":"m2","label":"ACME payload pushed","sub":"Attestation switched on","lane":"mdm","tone":"neutral"},{"id":"d1","label":"Device generates key pair","sub":"TPM or Secure Enclave where available","lane":"dev","tone":"neutral"},{"id":"c1","label":"SCEP endpoint checks challenge","sub":"RFC 8894","lane":"ca","tone":"neutral"},{"id":"c2","label":"ACME server checks attestation","sub":"device-attest-01","lane":"ca","tone":"neutral"},{"id":"c3","label":"Certificate issued","lane":"ca","tone":"success"},{"id":"d2","label":"Device holds certificate","lane":"dev","tone":"success"},{"id":"n1","label":"802.1X SSID on your access points","sub":"Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi","lane":"net","tone":"neutral"},{"id":"n2","label":"Purple cloud RADIUS","sub":"EAP-TLS check plus identity in Entra ID, Okta or Google Workspace","lane":"net","tone":"brand"},{"id":"n3","label":"VLAN set by identity","lane":"net","tone":"brand"}],"edges":[{"from":"m1","to":"d1","label":"profile"},{"from":"m2","to":"d1","label":"payload"},{"from":"d1","to":"c1","label":"SCEP request","style":"dashed"},{"from":"d1","to":"c2","label":"ACME order","style":"dashed"},{"from":"c1","to":"c3"},{"from":"c2","to":"c3"},{"from":"c3","to":"d2","label":"installed"},{"from":"d2","to":"n1","label":"EAP-TLS"},{"from":"n1","to":"n2","label":"RADIUS"},{"from":"n2","to":"n3"}]}
The diagram shows why the protocol choice stays contained. The MDM and CA lanes change between SCEP and ACME. The network lane does not.
Your SSID stays on 802.1X, the IEEE standard for port-based access control, with WPA2-Enterprise or WPA3-Enterprise. It points at Purple's cloud RADIUS. In the Cisco Meraki Dashboard, that is an SSID set to Enterprise with my RADIUS server. In Juniper Mist, HPE Aruba, Ruckus and Ubiquiti UniFi, it is the equivalent 802.1X or Enterprise security setting on the WLAN. No new hardware, and no change when you switch enrolment protocol.
Purple adds three things above the certificate. First, an identity lookup in Microsoft Entra ID, Okta or Google Workspace at connection. Second, VLAN assignment from that identity, so staff, managers and contractors land in different segments. Third, joiner, mover and leaver handling driven by your identity provider. You connect your MDM to Purple once. Setup takes five to 10 minutes for the whole organisation, not per site. See the Purple staff WiFi network for the full scope.
Some devices cannot enrol a certificate at all. Personal phones belong on the open network, using BYOD onboarding through a captive portal, the sign-in page shown before access. Printers, scanners and IoT kit belong on xPSK, which gives each device its own pre-shared key. Neither needs SCEP or ACME.
{"items":[{"value":"80,000+","label":"live venues on Purple","note":"Purple's own data"},{"value":"90","label":"countries deployed","note":"Purple's own data"},{"value":"5-10 min","label":"MDM setup, once per organisation","note":"Purple's own data"}]}
{"tone":"proof","title":"Staff WiFi on Purple at scale","text":"McDonald's recorded 80% fewer IT helpdesk requests on Purple, and JPMorgan runs staff WiFi on Purple across 5,000 branches. Whitbread runs segmented staff WiFi on Purple, with identity setting the segment."}
{"title":"Which enrolment path fits your estate","options":[{"name":"SCEP via your MDM","fitsWhen":["Your fleet is mostly Windows or Android","You already run AD CS with NDES or a hosted SCEP endpoint","Your MDM issues a unique challenge per request"],"notWhen":["You need proof the key was generated in hardware"]},{"name":"ACME with device attestation","fitsWhen":["Your Apple fleet is managed in an MDM with ACME payload support","Your CA supports the device-attest-01 challenge","Auditors want evidence that keys cannot be exported"],"notWhen":["Most of your devices run Windows or Android today"]},{"name":"Both, side by side","fitsWhen":["You run a mixed fleet across many sites","You want to migrate one platform at a time"],"notWhen":["Your RADIUS service can only trust one issuing CA"]}],"recommendation":"Run the Purple Access secure network as your EAP-TLS and cloud RADIUS layer. Enrol Apple devices with attested ACME where your MDM allows, keep SCEP elsewhere, and let identity set the VLAN."}
What does each enrolment path cost to run?
Neither protocol costs anything to use. Both are open IETF specifications. Your cost sits in three places: the CA that issues, the MDM that delivers and the servers you keep running between them.
On Microsoft infrastructure, the SCEP path means Active Directory Certificate Services (AD CS) plus the Network Device Enrollment Service (NDES) role. With Intune, add the Certificate Connector for Microsoft Intune. That is Windows Server capacity you patch, monitor and expose for enrolment. A managed PKI with a hosted SCEP endpoint removes those servers, priced per certificate or per device.
On the ACME path, the CA must run an ACME endpoint that supports device-attest-01. With a managed PKI, the provider runs that endpoint. With an in-house CA, you run it yourself. For the trade-offs, see managed PKI or AD CS for WiFi certificates.
{"caption":"What each enrolment path costs to run: structure, not amounts","asOf":"2026-06-10","columns":[{"key":"l","label":"Cost line"},{"key":"s","label":"SCEP path"},{"key":"a","label":"ACME path"},{"key":"p","label":"With Purple Access","highlight":true}],"rows":[["Protocol","Open RFC, no licence","Open RFC, no licence","Validates certificates from either path"],["Certificate authority","AD CS within Windows Server licensing, or managed PKI priced per certificate or device","Managed PKI or in-house CA with attestation support, priced per certificate or device","Trusts the issuing CA you configure"],["Servers to run","NDES and Intune connector on Windows Server, or none with a hosted SCEP endpoint","None on-premises when the CA hosts the ACME endpoint","None: cloud RADIUS replaces on-premises RADIUS"],["MDM","MDM licence per user or device; SCEP profiles documented widely","MDM licence per user or device; ACME payload support required","One MDM connection, five to 10 minutes"],["Ongoing staff time","Patch servers, watch challenge and connector health","Maintain CA policy and attestation trust","Manage access by identity, not device lists"],["Network change","None on access points","None on access points","None on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi"]],"footnote":"Pricing structure only. Check current pricing with each CA and MDM provider.","download":{"filename":"scep-vs-acme-cost-structure.csv"}}
The largest hidden cost on either path is often RADIUS, not enrolment. On-premises RADIUS servers need patching, high availability at every region and certificate trust updates. Purple's cloud RADIUS removes that line. If you are weighing a RADIUS replacement at the same time, see Cisco ISE alternatives for WiFi authentication.
What does moving from SCEP to ACME involve?
Moving one platform from SCEP to ACME is a profile change, not a network project. The work sits in your CA and MDM. Plan it in this order.
- Confirm your CA. Check that it runs an ACME endpoint supporting the device-attest-01 challenge.
- Confirm your MDM. Check that it delivers the ACME payload with attestation for the platform you are moving.
- Check the trust anchor. If ACME certificates come from the same issuing CA, RADIUS needs no change. If they come from a new CA, add it to the trusted CAs on Purple before you start.
- Pilot with one group. Deploy the ACME payload to a small device group at one site.
- Repoint the WiFi profile. Set the WiFi payload's identity certificate to the new ACME certificate for that group.
- Verify authentication. Confirm EAP-TLS succeeds and identity lands each device in the right VLAN.
- Roll out by site, then retire SCEP. Expand group by group. Remove the SCEP profile once every device on that platform has moved.
- Decommission last. Retire NDES or your SCEP endpoint only when no platform depends on it.
{"tone":"tip","title":"Keep SCEP live until the last device moves","text":"Run both profiles side by side during migration, so a failed ACME enrolment falls back to a working certificate. Your SSIDs and access points stay untouched throughout."}
Moving the other way, from ACME back to SCEP, follows the same steps in reverse. You would mostly do it for a platform where your MDM drops ACME support. Either direction, the network lane in the diagram does not move.
How to decide which certificate enrolment protocol to use
Use this decision rule, one platform at a time:
- Apple, managed, with ACME support in both your MDM and CA: enrol with ACME and device attestation.
- Apple without that support: enrol with SCEP and a per-request challenge, then revisit when your MDM adds the ACME payload.
- Windows: enrol with SCEP, store the key in the TPM where present, and use a per-request challenge. Tie access to device health with an Intune compliance policy.
- Android: enrol with SCEP through your MDM until it documents an attested path.
- Unmanaged personal devices: place them on the open network with BYOD onboarding.
- Devices that cannot hold a certificate: place them on xPSK with a key per device.
Every managed device then authenticates over EAP-TLS to Purple's cloud RADIUS. Identity in Microsoft Entra ID, Okta or Google Workspace sets the VLAN. The enrolment protocol becomes a per-platform setting, not an estate-wide bet.
Your next step: list your fleet by platform and check what your MDM and CA document for each. Then read the secure network pillar on certificates, identity and Passpoint for the full architecture. For the wider security picture, see the enterprise WiFi security guide.
Frequently asked questions
Is SCEP still safe to use for WiFi certificates?
Yes, when your MDM issues a unique challenge per request and the key sits in hardware where the platform allows. The weakness is a static, shared challenge password, which acts as a credential for anyone who copies it. SCEP also cannot prove where the private key was generated. For Windows and Android fleets, a well-configured SCEP profile remains a sound way to deliver EAP-TLS certificates.
Does ACME device attestation work on Windows and Android?
Check your MDM's documentation before you plan on it. Apple documents ACME with managed device attestation for its own platforms, which makes Apple fleets the natural place to start. The device attestation extension itself is still an IETF Internet-Draft. For Windows and Android, plan on SCEP with a hardware-backed key until your MDM and CA document an attested enrolment path for those platforms.
Do I need new access points or SSID changes to move from SCEP to ACME?
No. The enrolment protocol only changes how the certificate reaches the device. Your SSID stays on 802.1X with WPA2-Enterprise or WPA3-Enterprise, pointing at Purple's cloud RADIUS. That holds on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist and Ubiquiti UniFi alike. The only network-side check is that RADIUS trusts the CA that issues the new certificates.
Can SCEP and ACME certificates work on the same SSID?
Yes, provided both certificates chain to a CA your RADIUS service trusts. EAP-TLS checks the certificate, not the protocol that delivered it. Running both side by side is the normal migration pattern: Apple devices move to ACME while Windows and Android stay on SCEP. Purple's identity lookup and VLAN assignment work the same way for either certificate.
How is certificate enrolment priced?
The protocols are free; you pay for what surrounds them. AD CS comes within Windows Server licensing, while managed PKI providers price per certificate or per device. MDMs price per user or per device. On the SCEP path with AD CS, add the staff time to run NDES and the Intune connector. Purple's cloud RADIUS removes on-premises RADIUS servers from your cost lines.
Does ACME device attestation help with PCI DSS or ISO 27001 audits?
It strengthens your evidence for access control reviews. Attestation lets you show auditors that each WiFi certificate was issued to a hardware-bound key on a known device. Purple's RADIUS records add evidence for which identity connected and which VLAN it landed on. Together, they support the access control questions raised in PCI DSS and ISO 27001 reviews.
What happens to devices that cannot enrol a certificate?
They join a different Purple network rather than weakening the secure one. Personal devices join the open network through BYOD onboarding on a captive portal. Printers, scanners and IoT devices that cannot hold a certificate join the xPSK network, with a unique key per device. Identity still sets the VLAN on each network, so these devices stay segmented from staff traffic.
How long does it take to connect Purple to our MDM?
Five to 10 minutes, once, for the whole organisation. You connect your MDM to Purple a single time, not per site or per SSID. After that, certificates delivered by SCEP or ACME authenticate against Purple's cloud RADIUS at every site. McDonald's recorded 80% fewer IT helpdesk requests on Purple, and JPMorgan runs staff WiFi on Purple across 5,000 branches.
Frequently asked questions
Is SCEP still safe to use for WiFi certificates?
Yes, when your MDM issues a unique challenge per request and the key sits in hardware where the platform allows. The weakness is a static, shared challenge password, which acts as a credential for anyone who copies it. SCEP also cannot prove where the private key was generated. For Windows and Android fleets, a well-configured SCEP profile remains a sound way to deliver EAP-TLS certificates.
Does ACME device attestation work on Windows and Android?
Check your MDM's documentation before you plan on it. Apple documents ACME with managed device attestation for its own platforms, which makes Apple fleets the natural place to start. The device attestation extension itself is still an IETF Internet-Draft. For Windows and Android, plan on SCEP with a hardware-backed key until your MDM and CA document an attested enrolment path for those platforms.
Do I need new access points or SSID changes to move from SCEP to ACME?
No. The enrolment protocol only changes how the certificate reaches the device. Your SSID stays on 802.1X with WPA2-Enterprise or WPA3-Enterprise, pointing at Purple's cloud RADIUS. That holds on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist and Ubiquiti UniFi alike. The only network-side check is that RADIUS trusts the CA that issues the new certificates.
Can SCEP and ACME certificates work on the same SSID?
Yes, provided both certificates chain to a CA your RADIUS service trusts. EAP-TLS checks the certificate, not the protocol that delivered it. Running both side by side is the normal migration pattern: Apple devices move to ACME while Windows and Android stay on SCEP. Purple's identity lookup and VLAN assignment work the same way for either certificate.
How is certificate enrolment priced?
The protocols are free; you pay for what surrounds them. AD CS comes within Windows Server licensing, while managed PKI providers price per certificate or per device. MDMs price per user or per device. On the SCEP path with AD CS, add the staff time to run NDES and the Intune connector. Purple's cloud RADIUS removes on-premises RADIUS servers from your cost lines.
Does ACME device attestation help with PCI DSS or ISO 27001 audits?
It strengthens your evidence for access control reviews. Attestation lets you show auditors that each WiFi certificate was issued to a hardware-bound key on a known device. Purple's RADIUS records add evidence for which identity connected and which VLAN it landed on. Together, they support the access control questions raised in PCI DSS and ISO 27001 reviews.
What happens to devices that cannot enrol a certificate?
They join a different Purple network rather than weakening the secure one. Personal devices join the open network through BYOD onboarding on a captive portal. Printers, scanners and IoT devices that cannot hold a certificate join the xPSK network, with a unique key per device. Identity still sets the VLAN on each network, so these devices stay segmented from staff traffic.
How long does it take to connect Purple to our MDM?
Five to 10 minutes, once, for the whole organisation. You connect your MDM to Purple a single time, not per site or per SSID. After that, certificates delivered by SCEP or ACME authenticate against Purple's cloud RADIUS at every site. McDonald's recorded 80% fewer IT helpdesk requests on Purple, and JPMorgan runs staff WiFi on Purple across 5,000 branches.