PKI Enrollment Protocols (EST & CMP)
RFC 7030 (EST) and RFC 9810 (CMP, obsoletes RFC 4210) — hands-on PQC certificate enrollment with real OpenSSL 3.6 WASM crypto + an in-browser mock CA.
Why this matters: EST and CMP are how certificates actually get issued at scale in the real world — a PQC algorithm with no working enrollment protocol is a lab demo, not a deployable migration.
Start here: Pick an ML-DSA or ML-KEM parameter set and press Generate keypair: OpenSSL in the browser produces the end-entity key the CMP and EST enrollment steps use next, with the PEM available to inspect.
For your role
- Developer / Engineer
- EST (RFC 7030) and CMP (RFC 9810) enrollment with real OpenSSL 3.6 WASM crypto against an in-browser mock CA, including the KEM key update: the exchanges a client library implements.
- Security Architect
- The CMP KEM key update with an encrypted-certificate proof of possession is how enrollment works when the key cannot sign; the module shows both protocols against the same CA.
- Researcher / Academic
- Compare the EST and CMP enrollments of the same key against the RFCs, with the composite enrollment and certificate inspection steps the tool page defers to here.
- IT Ops / DevOps
- EST and CMP are how certificates get issued at scale; the module shows the requests and responses your enrollment endpoints will exchange with devices after the switch.
PKI Enrollment Protocols
When an end-entity needs an X.509 certificate, it doesn't just hand a self-signed key to the CA — the request is wrapped in a structured enrollment protocolthat carries the public key, attribute requests, proof-of-possession (POP), and authentication. Four enrollment protocols shape enterprise and automated PKI migration: EST (RFC 7030), CMPv3 (RFC 9810, July 2025, which obsoleted RFC 4210 and RFC 9480, alongside the RFC 9483 Lightweight CMP Profile), SCEP (RFC 8894), and ACME (RFC 8555).
EST — RFC 7030 (& SCEP / ACME)
Enrollment over Secure Transport — HTTPS-based, designed to be simple. Client POSTs a base64-encoded PKCS#10 CSR to /.well-known/est/simpleenroll; server returns a base64-encoded PKCS#7 degenerate SignedData containing the issued cert.
- Transport: HTTPS (TLS 1.2+; mutual TLS, or HTTP Basic/Digest over TLS)
- Request: PKCS#10 (RFC 2986 Certification Request)
- Response: PKCS#7 SignedData (single cert)
- POP: Self-signed PKCS#10 CSR (works for ML-DSA and SLH-DSA). A PKCS#10 CSR (
/simpleenroll) cannot prove possession of an ML-KEM key because KEM keys cannot sign; EST's/fullcmc(CMC) offers non-signature POP, but EST has no KEM-specific profile. A PKCS#9challengePassword(as used in SCEP RFC 8894) authenticates the request to the CA/RA but is not cryptographic POP of a KEM private key. - ACME (RFC 8555) proves domain control with challenges (
http-01,dns-01;tls-alpn-01is RFC 8737) in JWS-signed requests, and submits a PKCS#10 CSR at finalization (CA policy decides whether ML-DSA leaf keys are accepted).
CMPv3 — RFC 9810 & RFC 9483
Certificate Management Protocol — richer state machine supporting initial request (ir), cert request (cr), key update (kur), revocation (rr), and general messages (genm). RFC 9810 (obsoleting RFC 4210 and RFC 9480) defines CMPv3, with POP for KEM keys through the existing POPOPrivKey mechanisms and KEM-based message protection (KemCiphertextInfo plus a KDF over KemOtherInfo).
- Transport: HTTP (application/pkixcmp, RFC 9811, obsoletes RFC 6712)
- Request: CMP PKIMessage carrying CRMF (RFC 4211) CertReqMessages
- Response: PKIMessage with CertResponse (and encrypted cert for KEM POP)
- POP:
POPOSigningKeyfor signature keys (ML-DSA),POPOPrivKeysubsequentMessage(encrCertorchallengeResp, RFC 4211 / RFC 9883 / RFC 9810 §5.2.8.3) for KEM keys (ML-KEM), orraVerified - Keyfactor's EJBCA 9.4.2 PQC guide says CMP
encrCertPOP for ML-KEM is supported as of EJBCA 9.1. Its EJBCA 9.6.2 algorithm table lists ML-DSA via ACME, EST, and CMP. These are version-specific product claims; verify your deployed version, edition, CA profile, and HSM support. See the EJBCA PQC guide and supported-algorithms table.
Why this matters for PQC
PQC migration introduces three distinct enrollment mechanics across signing, KEM, and hybrid certificates:
- ML-DSA & SLH-DSA signature POP (EST, SCEP, ACME, CMP). The PKCS#10 CSR or CRMF
POPOSigningKeycarries the ML-DSA OIDs (RFC 9881) or SLH-DSA OIDs (RFC 9909) and proves private-key possession by signing the request structure with the subject key. - ML-KEM proof-of-possession (CRMF POPOPrivKey encrCert vs CSR). KEM keys (FIPS 203, RFC 9935 OIDs) only support encapsulation and decapsulation — they cannot sign a PKCS#10 CSR. In CMPv3 (RFC 9810) and CRMF KEM POP (RFC 9883, updating RFC 4211), CRMF replaces the CSR signature with
POPOPrivKeysubsequentMessage(encrCert): the CA encapsulates the newly issued certificate under the requester's ML-KEM public key, and the requester decapsulates the ciphertext, derives the key, decrypts the certificate and returns its hash incertConf; alternatively KEM-based MAC protection uses aKemCiphertextInfocarried ingenm/genporgeneralInfo, with a KDF overKemOtherInfo. Neither EST (RFC 7030, updated by RFC 8951, 8996, and 9908) nor SCEP (RFC 8894challengePassword) provides native KEM private-key POP. - Composite & parallel enrollment. RFC 10073 defines Composite ML-DSA algorithms for X.509/PKIX, combining a classical signature with ML-DSA under composite identifiers. It does not require every CA or validator to support them. The separate Composite ML-KEM document is still an Internet-Draft: revision 23, dated October 14, 2026, submitted to the RFC Editor queue as a Proposed Standard. Its status is not an assigned RFC number. Before adopting Composite ML-DSA, review RFC 10073's security caveat: it provides EUF-CMA but not SUF-CMA security against quantum adversaries, and is not recommended where the stronger property is required. The workshop demonstrates separate parallel certificates; it does not create a composite certificate.
Workshop tools
The Workshop tab drives real cryptographic operations in your browser using OpenSSL 3.6 WASM and our softHSM v3 (PKCS#11 v3.2). You'll:
- Generate an ML-DSA-65 keypair (or ML-KEM-768) via OpenSSL
genpkey - Send a real CMP Initial Request to an in-WASM mock CA
- POST a PKCS#10 CSR through a simulated EST
simpleenrollendpoint - Update an ML-KEM certificate with a signed CMP key update request, recover the encrypted certificate and confirm its hash
- Decode and chain-verify the issued certificate
Further reading
Related modules
In the Industry Landscape
Check your understanding
5 questions on PKI Enrollment Protocols (EST & CMP), each with its answer and the reason.
Take the quizNext step
Practice it: PKI Enrollment (EST + CMP)PKI Enrollment (EST + CMP) is the hands-on version of this module: the same ideas, run in your browser.
Production Tool Capabilities & Verification ChecklistPKI Engineers, IAM Architects & Network Automation Leads
Capabilities to require in your production tools:
- CMPv3 (RFC 9810 / RFC 9483) and CRMF (RFC 4211) support for `ML-KEM` certificate enrollment using `POPOPrivKey` `encrCert` encrypted-certificate proof-of-possession and explicit `certConf` hash verification (plus `KemOtherInfo` MAC protection).
- EST (RFC 7030), SCEP (RFC 8894), and ACME (RFC 8555) support for `ML-DSA` (RFC 9881) and `SLH-DSA` (RFC 9909) PKCS#10 CSR signature proof-of-possession, recognizing that PKCS#9 `challengePassword` only authenticates the request and cannot prove possession of an `ML-KEM` private key.
- Composite ML-DSA (RFC 10073) and parallel certificate issuance workflows for transitional hybrid PKI deployments.
How to evaluate in your environment
Execute CMPv3 `ir`/`kur` with `encrCert` POP for `ML-KEM-768` (including negative test with wrong `certConf` hash or unauthorized prior cert) and EST/ACME enrollment for `ML-DSA-65` against a staging CA (e.g., EJBCA 9.1+).
Production evidence to collect
CMPv3 PKIMessage transcript (`ir`/`ip`/`kur`/`kup`/`certConf`/`pkiconf`), negative confirmation-rejection log, and issued X.509 certificate chain verification.
Completing this Hub module and its browser-based sample exercises teaches the technical and governance decision criteria for your role; it does not test, validate, or certify your deployed production systems.
Record evidence for your environment
Identify the tested build and configuration. Use reference IDs for observations. For a proposed exclusion, record the system boundary or rule and why it excludes this build.
Evidence missing. 0 of 3 requirements have a reference or scope rationale.
Learning module content can be inaccurate. Please double-check its information. Report inaccuracies in PQC Today GitHub Discussions.