Every managed laptop, phone, Wi-Fi client and IoT device that authenticates with a certificate got that certificate through an enrolment protocol, and the enrolment endpoint is often the weakest link in the whole PKI. SCEP, EST, ACME and zero-touch onboarding protocols such as BRSKI decide who may ask the CA for a certificate, how the request proves possession of the key, and whether the subject name in the certificate can be trusted. Get it wrong and anyone who reaches the endpoint, or reuses a challenge, can obtain a certificate that your network access control, VPN or domain will accept. This guide compares the protocols, explains their security properties from the RFCs, covers MDM-driven SCEP through Microsoft Intune and NDES, constrained IoT enrolment, and how to monitor and migrate. It is for PKI engineers, endpoint and MDM teams, OT and IoT architects and NHI owners. Certificate lifecycle management in general is covered in the Machine Identity, PKI and Certificate Lifecycle Guide.
Key takeaways
- Enrolment authorisation is the control that matters. The CA can only be as trustworthy as the check that decides a requester deserves a certificate for the name it asks for.
- SCEP is Informational and relies on a shared challenge. RFC 8894 recommends a one-time, high-entropy, short-lived challengePassword and warns that omitting it allows unauthenticated enrolment.
- EST is the standards-track successor. RFC 7030 runs over TLS, recommends TLS client certificate authentication and lets the client bind its identity to proof of possession with
tls-unique. - MDM SCEP is only safe with a dynamic, validated challenge. Intune signs and encrypts a per-profile challenge containing the expected subject and SAN, and its NDES policy module rejects requests that do not match.
- Hardware-bound keys and attestation raise the bar. ACME with device attestation, TPM-backed keys and IDevID-based onboarding (BRSKI) prove the request comes from a genuine, specific device, not just from someone who knows a secret.
The enrolment protocols compared
| Protocol | Status | Transport | How the requester is authorised | Typical use |
|---|---|---|---|---|
| SCEP (RFC 8894) | Informational RFC, September 2020 | HTTP (POST required where supported), messages protected with CMS | challengePassword shared secret for initial enrolment; existing certificate for renewal | MDM enrolment of phones, laptops, network devices; legacy routers and printers |
| EST (RFC 7030) | Standards Track, October 2013 | HTTPS with TLS 1.1 or later (use TLS 1.2 or 1.3 in practice) | TLS client certificate (recommended), HTTP Basic or Digest inside TLS, or certificate-less TLS-SRP | Network equipment, IoT gateways, industrial devices, enterprise devices with an existing identity |
| EST-coaps (RFC 9148) | Standards Track, April 2022 | CoAP over DTLS | Certificate in the DTLS handshake; Basic and Digest not supported | Constrained IoT devices that already speak CoAP |
| BRSKI (RFC 8995) | Standards Track, May 2021 | TLS, then EST | Manufacturer IDevID plus a voucher from the manufacturer's MASA naming the owner's registrar | Zero-touch onboarding of new devices into an owner's PKI |
| ACME (RFC 8555) with device attestation | ACME is Standards Track; Apple supports device attestation in its ACME payload | HTTPS | Account key plus challenge; with attestation, proof of genuine hardware and a hardware-bound key | Apple managed devices (iOS 16, iPadOS 16.1, macOS 14, tvOS 16 or later); server TLS certificates |
Status checked on the RFC Editor on 27 October 2026. ACME for server certificates is covered in the ACME and Automated Certificate Management Guide.
SCEP: how it works and where it is weak
SCEP carries PKCS #10 requests inside CMS messages over HTTP. Initial enrolment uses PKCSReq (message type 19) authenticated with a challengePassword; renewal uses RenewalReq (17) signed with the existing certificate; CertPoll (20) polls for a pending request; GetCert (21) and GetCRL (22) retrieve certificates and CRLs. Clients discover CA features with GetCACaps, whose keywords include AES, SHA-256, POSTPKIOperation, Renewal and SCEPStandard.
- Challenge handling: RFC 8894 recommends a one-time challengePassword, says it should be high entropy with a limited lifetime, and notes that a second request using the same challenge can signal a breach. A static, reused challenge printed in an MDM profile or a device configuration guide is effectively a public enrolment key.
- No challenge, no authorisation: the RFC states that omitting the challenge allows unauthenticated authorisation of enrolment requests. Some SCEP servers can be configured this way for convenience; never expose one to an untrusted network.
- Algorithm downgrade: GetCACaps is unauthenticated, so an attacker in the path can strip capabilities. The RFC forbids single DES and MD5 and tells clients to treat a missing SCEPStandard keyword as a warning sign. Configure clients and servers for AES and SHA-256 only.
- Renewal proof of possession: RenewalReq is signed with the old key, so the client does not prove possession of the new key (RFC 8894 section 7.6). Limit renewal to the same subject and keep validity short.
- Subject trust: SCEP itself does not tell the CA whether the requester is entitled to the subject or SAN it asks for. Something else (the MDM, an RA policy module) must check it, otherwise any challenge holder can request any name.
- CA key use: SCEP uses the CA or RA key for signing and optionally encryption, which the RFC calls generally undesirable. Use a dedicated RA certificate rather than the issuing CA key.
MDM-driven SCEP with Intune and NDES
Most enterprise device certificates for Wi-Fi, VPN and Microsoft Entra or Active Directory authentication are issued by MDM SCEP profiles. With an AD CS Enterprise CA, Intune uses the Network Device Enrollment Service (NDES) and the Certificate Connector for Microsoft Intune.
| Component or setting | Secure configuration | Why |
|---|---|---|
| NDES placement | Separate domain-joined server, not a domain controller and not the issuing CA | Microsoft warns that NDES on the issuing CA is a security risk when it serves internet requests |
| Challenge | Intune's signed, encrypted challenge blob, validated by the Intune policy module on NDES | The blob carries the expected subject and SAN; requests that do not match are refused, and direct access to the NDES URL returns 403 |
| External publishing | Microsoft Entra application proxy or Web Application Proxy with passthrough pre-authentication, or a reverse proxy that supports query strings around 40 KB | SCEP cannot pre-authenticate, so the policy module is the main protection; keep NDES itself off the internet |
| NDES service account | Member of IIS_IUSRS on the NDES server, Read and Enroll on the SCEP template only | Minimal rights for a high-value NHI |
| Revocation rights | Issue and Manage Certificates on the CA for the NDES system or service account | Lets Intune revoke certificates for retired or wiped devices |
| Certificate template | Client Authentication only in application policies, "Supply in the request" subject, Publish in Active Directory unchecked, a dedicated template name in the MSCEP registry values (SignatureTemplate, EncryptionTemplate, GeneralPurposeTemplate) | Restrict what the certificate can be used for |
| Strong certificate mapping | Confirm issued certificates carry the SID SAN tag URL=tag:microsoft.com,2022-09-14:sid:<value> introduced with KB5014754 | Required for strong mapping in Active Directory; third-party CAs must support it |
- "Supply in the request" is dangerous anywhere else: a template that lets the requester choose the subject and grants Client Authentication allows impersonation if anyone other than the validated NDES path can enrol against it. Restrict enrol permission on SCEP templates to the NDES service account only, and audit them as part of AD CS reviews. See the AD CS Security Guide and the MITRE ATT&CK T1649 Steal or Forge Authentication Certificates Guide.
- Standalone NDES with a static challenge: NDES without the Intune module or an equivalent MDM validation issues certificates to anyone with the current challenge. Replace it, or confine it to an isolated management network with short challenge lifetimes.
- Third-party CAs: Intune supports SCEP with third-party CAs through their own connectors, without NDES. The same questions apply: is the challenge dynamic, is the subject validated, are certificates revoked when devices leave?
- Validity: Microsoft requires at least five days; most organisations issue device certificates for one year or less. Shorter validity reduces exposure after a device is lost but increases renewal load on NDES.
Intune administration itself is a privileged path to every device: the Stryker Cyberattack showed a hijacked admin account wiping tens of thousands of devices through Intune. Whoever can edit SCEP profiles can change the subject and SAN that devices will request. See the Microsoft Intune Guide.
EST: stronger enrolment for network and IoT devices
- Operations:
/.well-known/est/cacerts,/simpleenrolland/simplereenrollare mandatory;/fullcmc,/serverkeygenand/csrattrsare optional. - Client authentication: RFC 7030 recommends TLS client certificate authentication. Initial enrolment can use a manufacturer-installed or other previously installed certificate; HTTP Basic or Digest is permitted only inside TLS, and should be limited to one-time credentials if used at all.
- Proof-of-possession binding: clients should embed the TLS
tls-uniquevalue in the CSR so the server knows the authenticated TLS client holds the key in the request. Require it where your clients support it. - Trust anchor bootstrap: a client without a configured CA may fetch
/cacertsunauthenticated, but RFC 7030 requires out-of-band authorisation of that CA certificate (for example a fingerprint check) before any other exchange. Provision the trust anchor at manufacture or staging instead. - Server-side key generation:
/serverkeygensends a private key to the device. The RFC requires a confidentiality-providing cipher suite and encourages CMS encryption of the returned key. Prefer device-generated keys, ideally in a TPM or secure element, and use server-side generation only for devices that cannot generate good keys. - Constrained devices: EST-coaps (RFC 9148) carries the same operations as
/crts,/sen,/sren(mandatory) and/skg,/skc,/att(optional) over CoAP and DTLS, with certificate authentication in the DTLS handshake and a mandatory TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8 cipher suite. Where a registrar translates to HTTPS, proof-of-possession linking is lost and the EST server must trust the registrar's checks.
Zero-touch and attested enrolment
A shared secret proves only that the requester knows the secret. Device identity proves the request comes from a specific piece of hardware.
- BRSKI: a new device (the pledge) presents its 802.1AR IDevID manufacturer certificate to the owner's registrar; the manufacturer's MASA issues a signed voucher (RFC 8366 format) naming the registrar; once the device trusts the registrar it enrols for a locally issued LDevID over EST. No manual configuration on the device is needed.
- Apple managed device attestation: with the ACME payload, the private key is generated in the Secure Enclave and tied to that device, and the CA can validate attested properties against its inventory. Apple lists threats this addresses, including a compromised device lying about its properties and an attacker hijacking a certificate request. Keys are removed on erase or restore, so profiles must be reapplied.
- TPM-backed keys on Windows and Linux: request keys in the TPM through the key storage provider or platform tooling so the certificate cannot be copied to another machine. See the IoT Device Identity with TPM and DICE Guide.
- Onboarding standards for IoT fleets: FIDO Device Onboard and Matter device attestation solve the same first-contact problem for their ecosystems. See the FIDO Device Onboard Guide and the IoT Device Onboarding Guide.
Choosing a protocol
- MDM-managed phones and laptops: SCEP with a dynamic MDM-validated challenge is the realistic default; move Apple devices to ACME with attestation where your CA and MDM support it, and use TPM-protected keys on Windows.
- Network equipment and gateways: EST with an initial certificate from manufacturing or staging, re-enrolment with
/simplereenroll, and SCEP only for devices that support nothing else. - Constrained IoT: EST-coaps where devices use CoAP, BRSKI or a vendor onboarding protocol for zero-touch, and a registrar at the network edge.
- Legacy devices that only do SCEP with a static challenge: isolate the enrolment endpoint on a management network, issue from a dedicated subordinate CA with narrow EKUs, rotate the challenge after each staging batch and plan replacement.
- Small versus large organisations: a small organisation using a cloud MDM and a hosted CA mostly configures profiles and templates correctly. A large or OT-heavy estate runs several enrolment paths and needs a separate issuing CA per path, an RA policy for each, and an inventory that ties every issued certificate to an enrolled device.
Rolling out and migrating
- Inventory enrolment endpoints: list every SCEP, EST and ACME endpoint, the CA and template behind each, how requesters are authorised, and whether the endpoint is reachable from the internet.
- Fix the worst first: remove unauthenticated or static-challenge endpoints from untrusted networks, restrict template enrol rights to the RA service accounts, and drop DES, MD5 and SHA-1 from GetCACaps.
- Pilot: issue from a new template or subordinate CA to a pilot ring of devices; confirm Wi-Fi, VPN and sign-in still work and that the SID SAN tag or other mapping is present.
- Expand in rings by device type, keeping the old profile assigned until the new certificate is confirmed on each device, then remove the old profile and revoke the old certificates.
- Move to stronger methods (EST with client certificates, ACME with attestation, TPM-bound keys) as device support allows.
Rollback: keep the previous profile and template available, unassigned, for the pilot period. If the new path fails, reassign the old profile to the affected ring; do not reopen a static challenge to the internet as a shortcut.
Detection and measurement
- CA issuance logs: on AD CS, enable auditing of certificate services and monitor events 4886 (request received) and 4887 (certificate issued); alert on SCEP-template certificates whose subject or SAN does not match an enrolled device.
- NDES and policy module logs: failed challenge validations, repeated use of the same challenge and spikes in requests from one source.
- Template and profile changes: alert on changes to SCEP templates, enrol permissions, MSCEP registry values and MDM certificate profiles.
- Certificates in use without a device: certificates presented to RADIUS or VPN that do not map to a current device in the MDM inventory indicate theft or forgery (T1649 Steal or Forge Authentication Certificates, T1552.004 Private Keys).
| Metric | Target direction |
|---|---|
| Enrolment endpoints with static or no challenge reachable from untrusted networks | Zero |
| Device certificates with hardware-bound keys (TPM, Secure Enclave, secure element) | Up |
| Issued certificates not matched to a current managed device | Down to zero |
| Time from device retirement or wipe to certificate revocation | Hours |
| SCEP endpoints still offering legacy algorithms in GetCACaps | Zero |
Framework mapping
| Framework | Reference | Enrolment control |
|---|---|---|
| NIST SP 800-53 Rev. 5 | IA-3 Device Identification and Authentication | Certificates as device identity, issued only to authorised devices |
| NIST SP 800-53 Rev. 5 | IA-5(2) Public Key-based Authentication; SC-17 Public Key Infrastructure Certificates | Validated certification path, enrolment authorisation, revocation |
| NIST SP 800-53 Rev. 5 | SC-12 Cryptographic Key Establishment and Management | Device-generated, hardware-bound keys; protected server-side generation |
| NIST SP 800-53 Rev. 5 | CM-8 System Component Inventory | Every certificate tied to an inventoried device |
| NIST CSF 2.0 | PR.AA-01, PR.AA-03, ID.AM-01 | Hardware credentials managed, devices authenticated, hardware inventory |
| CIS Controls v8.1 | Control 1 Inventory and Control of Enterprise Assets; Control 4 Secure Configuration | Device inventory and secure configuration of CA, NDES and profiles |
| MITRE ATT&CK | T1649 Steal or Forge Authentication Certificates; T1552.004 Private Keys; T1557 Adversary-in-the-Middle | Abuse of enrolment, key theft, downgrade on unauthenticated discovery |
Common failure patterns
- Static SCEP challenge in every profile: the same password distributed to thousands of devices, staging guides and contractors, so anyone who obtains it can enrol.
- NDES on the issuing CA, published to the internet: one compromise exposes the CA itself.
- Open enrol rights on "Supply in the request" templates: any domain user can request a client authentication certificate for any name, bypassing NDES entirely.
- No revocation on device retirement: wiped or stolen devices keep valid certificates that the network still accepts.
- Unauthenticated trust anchor bootstrap: devices accept whatever CA certificate the first server offers, letting an attacker in the path become their CA.
- Software keys exported with the certificate: device certificates copied to another machine work exactly like the original.
Practitioner checklist
- Inventory every enrolment endpoint with its CA, template, authorisation method and network exposure.
- Use only dynamic, MDM-validated SCEP challenges; retire static-challenge and unauthenticated endpoints.
- Keep NDES off the CA and domain controllers and publish it only through a proxy with passthrough to the validated path.
- Restrict enrol rights on SCEP and EST templates to the RA service accounts, with Client Authentication only.
- Configure SCEP for AES and SHA-256 only; require TLS 1.2 or later and client certificate authentication for EST.
- Generate keys on the device in hardware where possible and use attestation where the platform supports it.
- Provision trust anchors at manufacture or staging, never by trusting the first CA offered.
- Revoke device certificates automatically on retirement, wipe or loss.
- Monitor CA issuance events, NDES validation failures and template or profile changes.
Standards and references
- IETF: RFC 7030 Enrollment over Secure Transport
- IETF: RFC 8894 Simple Certificate Enrolment Protocol
- IETF: RFC 9148 EST over Secure CoAP (EST-coaps)
- IETF: RFC 8995 Bootstrapping Remote Secure Key Infrastructure (BRSKI)
- Microsoft Learn: Configure infrastructure to support SCEP with Intune
- Apple Platform Deployment: Managed device attestation
- NIST: SP 800-53 Rev. 5
Related NHI Mgmt Group resources: Machine Identity, PKI and Certificate Lifecycle Guide · Enterprise PKI Design and CA Hierarchy Guide · 802.1X and EAP-TLS Enterprise Wi-Fi Guide · Certificate Revocation Guide