Certificate Enrollment Flow
This section describes the end-to-end certificate enrollment flow for devices managed by BigFix MCM, using MCM Proxy, NDES Proxy, and Microsoft Certificate Authority.
Step-by-Step Enrollment Flow
- Policy Deployment
- BigFix MCM deploys the SCEP profile to the target device
- The profile contains:
- SCEP URL (pointing to MCM Proxy)
- Subject details
- Key configuration and more
- Challenge Password Retrieval
- BigFix MCM server requests a challenge password from the NDES
Admin endpoint through NDES
Proxy
http://<ndes-admin>/certsrv/mscep_admin - The challenge password is injected into the SCEP payload before being sent to the device.
- BigFix MCM server requests a challenge password from the NDES
Admin endpoint through NDES
Proxy
- Device Initiates Certificate Request
- The device generates a key pair (RSA 4096) locally.
- The device sends a SCEP request to the MCM
Proxy:
https://<mcm-server>/mscep_proxy
- MCM Proxy Forwards Request
- MCM Proxy forwards the request to the NDES Proxy.
- NDES Proxy Forwards Request
- NDES Proxy securely forwards the request to the NDES server.
- Provides isolation between external access and internal infrastructure.
- NDES Processes Request
-
NDES validates the challenge password.
-
Maps the request to the configured certificate template.
-
Submits the request to the Certificate Authority (CA).
-
- Certificate Authority Issues Certificate
- CA validates the request based on:
- Template configuration
- Permissions
- CA signs and issues the certificate.
- CA validates the request based on:
-
Certificate Response Flow
- CA → NDES → NDES Proxy → MCM Proxy → Device
- The issued certificate is returned back to the device
- Certificate Installation on Device
- The device installs the certificate
- The certificate can now be used for:
- Authentication
- Wi-Fi / VPN access
- Identity-based access control