Auto-Enrollment Protocols

AppViewX CLM enables certificate auto-enrollment by automating all the steps involved, including CSR generation, domain ownership verification, certificate download, and provisioning, making the process efficient, scalable, and secure. AppViewX CLM supports all major auto-enrollment protocols including – ACME, EST, SCEP, Native Windows Auto-enrollment, and Microsoft Intune. Automating certificate enrollment reduces human error, outages, and security compromises, while improving productivity.

Auto-enrollment protocols are standardized enrollment mechanisms accepted across a wide range of enterprise systems for device and application certificate enrollment. Systems leveraging auto-enrollment protocols typically expect minimum to no admin intervention. Network devices such as routers-switches, DevOps tools, and Enterprise Mobility Management platforms are typical examples of such systems. If the deployment mode is:
  • SaaS or Managed Kubernetes, deploying a cloud connector enables auto-enrollment.
  • SaaS deployments where cloud connectors are unavailable, users should provide the AppViewX host information, which includes the IP address and port of the URL or endpoint. If their devices support auto-enrollment to a public URL, auto-enrollment is available as part of the tenant, and configuration details are provided in the documentation.

The cloud connector is advised for DMZ-based deployments or for enrollment through your cloud connector. This is especially useful in scenarios where endpoints cannot communicate with a public URL for auto-enrollment through a private channel, necessitating the use of the cloud connector.

AEP Certificate Inventory Behavior

By default, certificates enrolled through auto-enrollment protocols are placed in Monitored status in the CLM inventory. For new customers provisioned from the 2026.3.0 release onward, an instance-level flag (AEP_CERTS_DEFAULT_TO_MANAGED_STATUS) may be enabled, which causes all AEP-enrolled certificates to be placed directly into Managed status.

When this flag is enabled:
  • Certificates enrolled through any AEP protocol (EST, ACME, SCEP, CMP, MS Intune, WAEP) are placed in Managed status upon enrollment.
  • Certificates issued via AppViewX PKI (native CA) are placed in Managed status but are not counted toward CLM license consumption.
  • Certificates issued via third-party CAs continue to count toward CLM license consumption as applicable.
Existing customers are not affected by default. To enable this behavior for an existing instance, the SRE or TAC team must execute a DB script manually.

Auto-Enrollment Protocol Selection

Choose the right auto-enrollment protocol to issue, distribute, and renew certificates seamlessly across your infrastructure.

Selecting the correct auto-enrollment protocol at the start of a deployment prevents certificate lifecycle failures and reduces operational overhead. AppViewX supports five protocols, each designed for a specific infrastructure type and use case.
Table 1. Supported auto-enrollment protocols
Protocol Primary use
SCEP Network devices and MDM-managed endpoints
EST Agent-based endpoint enrollment with mutual TLS
ACME Web servers and cloud workloads requiring domain validation
CMP Telecom infrastructure and constrained embedded devices
WAEP Windows environments using Active Directory and Group Policy

Use the decision matrix to match your environment to a protocol, or work through the discovery questions during customer onboarding.

SCEP (Simple Certificate Enrollment Protocol)

Use SCEP to issue certificates to network devices and MDM-managed endpoints such as routers, switches, and corporate laptops.

When to use SCEP
SCEP is the right choice when your environment includes:
  • Network devices such as routers, switches, access points, and printers.
  • An MDM solution (Microsoft Intune or Jamf) that handles certificate distribution.
  • IoT or embedded devices with limited protocol support.
When not to use SCEP
Avoid SCEP in the following scenarios:
  • No MDM in place SCEP depends on an MDM solution to push and manage certificates. Without one, certificate distribution fails.
  • Telecom or highly constrained embedded devices Use CMP instead for environments governed by ETSI or 3GPP standards.
Example

An organization with 500 employees uses SCEP through Microsoft Intune to automatically issue certificates to all Windows and macOS laptops. The certificates enable devices to authenticate to the corporate Wi-Fi network.

EST (Enrollment over Secure Transport)

Use EST to enroll and renew certificates on managed endpoints where you can deploy a certificate agent, using mutual TLS authentication.

When to use EST
EST is the right choice when your environment includes:
  • Endpoint devices (laptops, desktops, or servers) where you can deploy agents.
  • A requirement for TLS mutual-authentication-based enrollment.
  • Mixed device fleets that use modern certificate management workflows.
When not to use EST
Avoid EST in the following scenarios:
  • No agent deployment on endpoints EST requires a certificate agent or client on each device. If you can't deploy agents, use SCEP or CMP instead.
  • Pure network device environments SCEP has broader native support on network hardware such as routers and switches.
Example

An organization deploys a certificate agent on all Windows and macOS laptops. EST automatically enrolls and renews TLS client certificates on each device without requiring user interaction.

ACME (Automatic Certificate Management Environment)

Use ACME to automate public TLS certificate issuance and renewal for web servers and cloud workloads through HTTP-01 or DNS-01 domain validation.

When to use ACME
ACME is the right choice when your environment includes:
  • A need for HTTP-01 or DNS-01 challenge-based domain validation.
  • Public-facing web servers or cloud workloads that require automated TLS certificate issuance.
  • DevOps pipelines that use tools such as Certbot for certificate automation.
When not to use ACME
Avoid ACME in the following scenarios:
  • Internal PKI use cases Challenge-based validation doesn't apply to internal certificate authorities. Use EST or SCEP instead.
  • Network or telecom devices Devices without HTTP or DNS challenge capability can't complete ACME validation.
  • Endpoint agent deployments EST is better suited for managed endpoints where a certificate agent is already installed.
Example

An organization runs 50 public-facing web services. It uses ACME with DNS-01 challenges to automatically renew certificates across all domains, eliminating the need for manual certificate management.

CMP (Certificate Management Protocol)

Use CMP to enroll certificates on telecom infrastructure and constrained embedded devices that require a standards-based PKI protocol per ETSI or 3GPP specifications.

When to use CMP
CMP is the right choice when your environment includes:
  • Telecom infrastructure such as base stations, gateways, and core network elements.
  • A requirement for a standards-based PKI protocol that conforms to ETSI or 3GPP specifications.
  • Constrained devices that need a robust, lightweight enrollment protocol.
When not to use CMP
Avoid CMP in the following scenarios:
  • Standard enterprise endpoint or network device deployments SCEP and EST are simpler and better supported in these environments.
  • Web or cloud workloads Use ACME for public-facing services that require domain validation.
Example

A telecom operator deploys 5G base stations. It uses CMP to automatically enroll each network element with a device certificate, meeting the requirements of 3GPP TS 33.310.

WAEP (Windows Auto-Enrollment via Group Policy)

Use WAEP to automatically issue certificates to domain-joined Windows devices through Active Directory and Group Policy Objects (GPOs).

When to use WAEP
WAEP is the right choice when your environment includes:
  • A Windows-only environment that uses Active Directory and Group Policy for device management.
  • Certificate issuance through Active Directory Certificate Services (AD CS) or AppViewX PKI.
  • Certificate templates that your team manages through Group Policy.
When not to use WAEP
Avoid WAEP in the following scenarios:
  • Non-Windows environments WAEP doesn't support macOS, Linux, or network devices. Use EST, SCEP, or ACME for cross-platform deployments.
  • No Active Directory or AD CS infrastructure WAEP requires domain membership and an AD CS or AppViewX PKI hierarchy to function.
Example

An organization has 2,000 domain-joined Windows machines. It uses Group Policy to automatically enroll all devices with computer certificates from an internal AD CS hierarchy or AppViewX PKI, with no manual steps required.

Protocol Decision Matrix

Use this table to match your infrastructure or requirements to the recommended auto-enrollment protocol.
Table 2. Auto-enrollment protocol recommendations by scenario
Scenario or environment Recommended protocol Reason
Endpoints (laptops, desktops) with agent deployment EST or ACME Designed for automated certificate lifecycle management on managed endpoints.
Network devices (routers, switches, printers) SCEP Lightweight protocol with broad native support on network hardware.
Telecom or embedded devices CMP Purpose-built for constrained telecom environments per ETSI and 3GPP standards.
No MDM solution (no Intune or Jamf) EST or CMP SCEP requires an MDM solution to distribute certificates. EST and CMP work independently.
HTTP or DNS challenge-based domain validation required ACME Native support for ACME HTTP-01 and DNS-01 domain validation challenges.
Windows environment with GPO-based certificate issuance WAEP Integrates natively with AD CS and AppViewX PKI for Group Policy auto-enrollment.

Identify the right protocol during customer onboarding

Ask these questions during onboarding or scoping to determine which auto-enrollment protocol best fits a customer's environment. Work through each question in order and stop when you reach a clear recommendation.

  1. Are you planning to deploy certificate agents or software on endpoints such as laptops, desktops, or servers?
    • Yes Consider EST or ACME.
    • No EST and ACME are likely not the right fit. Continue to the next question.
  2. Do you have network devices such as routers, switches, or printers that need certificates?
    • Yes SCEP is likely the right fit.
    • No Continue to the next question.
  3. Do you have an MDM solution in place, such as Microsoft Intune or Jamf?
    • No SCEP is not suitable. Consider EST or CMP.
    • Yes SCEP remains a viable option. Continue to confirm other requirements.
  4. Do you have telecom infrastructure such as base stations, gateways, or core network elements?
    • Yes CMP is purpose-built for this environment.
    • No Continue to the next question.
  5. Do you need HTTP or DNS challenge-based domain validation for public certificates?
    • Yes ACME is the right choice.
    • No Continue to the next question.
  6. Are you in a Windows-only environment that uses Active Directory and Group Policy?
    • Yes WAEP (GPO-based auto-enrollment) is the right fit.
    • No Review the decision matrix with the customer to confirm the best option.

After completing these questions, you should have a clear protocol recommendation. Refer to the relevant protocol section above for detailed guidance on supported environments and deployment examples.