CMC enrollment must authorize each certificate action, not just the connection
Certificate Management over CMS (CMC) carries certificate requests, responses, revocation, and status information inside CMS messages. The July 2026 revision in RFC 10002 modernizes the message structures, while RFC 10003 covers transport and RFC 10004 lists compliance requirements. A registration authority or certificate authority that only authenticates the HTTPS connection is missing much of CMC's security model.
CMC messages can be signed with CMS SignedData, authenticated with AuthenticatedData, or encrypted with EnvelopedData. A Full PKI Request can contain several controls, including identity proof, proof of possession, transaction identifiers, nonces, modification requests, and certificate acceptance. The receiver must verify the CMS signature before acting on those controls. RFC 10002 also requires a Full PKI Response when a request fails, remains pending, or needs to return information beyond the issued certificates.
That message model creates a useful audit boundary. The connection authenticates the transport peer. The CMS control authenticates the requested action at the PKI layer. A registrar should record which control caused an issuance, which transaction it belongs to, and whether the end entity accepted the result. This matters when an enrollment request crosses an RA, a CA, and one or more back-end signing services.
Bind the request to a transaction
RFC 10004 requires transaction IDs, sender nonces, and recipient nonces across end entities, RAs, and CAs. Their presence is not enough if the service does not preserve them. A CA should reject a response that does not match the outstanding request, and a client should reject a response that reuses a nonce or references an unknown transaction. If the RA stores only a certificate serial number, investigators lose the link between the approval and the request that produced it.
Proof-of-possession controls need the same treatment. A signed request can show that a key signed the request, while a POP link random value binds the key proof to the transaction. The server should treat a missing or stale POP witness as a failed enrollment, not as an optional hint. Batch requests add more state, so each response body and bodyPartID must map back to the correct request entry.
Separate approval from issuance
The end entity can ask for changes. The RA can modify a request or add extensions. The CA decides whether to issue the certificate. Keeping these decisions as separate records prevents a common failure where an account with permission to submit a request is also treated as an authority to approve it.
Certificate acceptance is another explicit action. When the CA asks for confirmation, the client sends a Full PKI Request containing the acceptance control, and the CA returns a confirming Full PKI Response. Automation should wait for that response before placing the certificate into service. Otherwise a rollback or a rejected certificate may still be deployed by a job that only saw the issuance response.
Operational checks
Inventory every CMC endpoint, including HTTP, email, and any other supported transport. Restrict algorithm policy at the CMS layer and reject unsigned controls when policy requires signatures. Keep request and response bodies long enough for incident review, but redact private-key archival material and other sensitive payloads. Alert on repeated badMessageCheck failures, unknown transaction IDs, nonce reuse, and a spike in pending confirmations.
Finally, test interoperability against the published CMC test cases and each vendor's supported control set. RFC 10004 describes requirements by role, and a product that calls itself CMC-compatible can still omit controls that another implementation depends on. Record the supported controls in the PKI service inventory so a later upgrade does not silently remove identity proof, POP, or acceptance handling.
Top comments (0)