certificate hub

Certificate
Enrollment Gateway
for Enterprise PKI

Simplify certificate enrollment across devices, applications and enterprise systems.Certificate Hub connects your existing Certificate Authorities with multiple enrollment protocols, enabling automated certificate provisioning without complex client integrations or replacing your existing PKI.

ACME · SCEP / NDES · EST · Microsoft CEP / CES · DCOM · LCEP
overview

What is CipherMail?

ID Security Certificate Hub, also referred to as Enrollment Hub, is a certificate enrollment platform that connects devices, applications and enterprise systems to Certificate Authorities through multiple enrollment protocols.

It provides protocol-specific frontends that behave like a Certificate Authority from the client's perspective, while shielding clients from differences between backend CA interfaces.

By supporting ACME, SCEP/NDES, EST, Microsoft CEP/CES, DCOM and LCEP, Certificate Hub helps organizations automate certificate provisioning, improve compatibility and maintain centralized control over enrollment policies.

the problem

Different devices. Different protocols. One certificate enrollment challenge.

Enterprise environments contain devices, applications and systems that rely on different certificate enrollment protocols.

However, Certificate Authorities often expose a limited set of interfaces that do not match every client's technical requirements.

These compatibility gaps can lead to manual workarounds, complex integrations and failed certificate enrollment, making PKI operations harder to scale.

WHY CERTIFICATE HUB

Why Certificate Hub for Enterprise Certificate Enrollment?

Certificate Hub bridges the gap between certificate consumers and Certificate Authorities. It provides multiple enrollment interfaces, supports automated certificate provisioning and helps organizations integrate heterogeneous devices without replacing their existing PKI.

01

Multiple enrollment protocols

Support ACME, SCEP/NDES, EST, MicrosoftCEP/CES, DCOM and LCEP.

02

Integrate existing CAs

Connect certificate consumers with supported internal, external and Trust Center Certificate Authorities.

03

Automated certificate provisioning

Reduce manual enrollment tasks through protocol-based certificate issuance.

04

Client compatibility

Connect systems that require different certificate enrollment interfaces.

05

CA isolation

Separate Certificate Authorities from direct client access to strengthen infrastructure protection.

06

Multi-tenant architecture

Support separation of tenants and centralized policy administration.

07

Flexible certificate policies

Use standard or customized certificate templates to meet organizational requirements

08

Scalable operations

Support clustering, auditing and certificate lifecycle notifications.

ENROLLMENT PROTOCOLS

One enrollment platform. Multiple certificate enrollment protocols.

Certificate Hub provides protocol-specific frontends that allow different devices, applications and enterprise systems to request certificates from connected Certificate Authorities.

Each frontend addresses particular client requirements, helping organizations support heterogeneous PKI environments without developing custom enrollment interfaces for every system.

01

ACME Frontend

Automate certificate enrollment using the ACME protocol and supported domain or resource ownership validation methods.

02

SCEP & NDES Frontend

Enable certificate provisioning for SCEP-compatible clients, including environments using Microsoft's NDES approach.

03

EST Frontend

Support certificate enrollment over secure TLS connections, including supported authentication and bootstrap methods.

04

Microsoft CEP & CES Frontend

Provide Microsoft certificate enrollment policy and enrollment service interfaces for supported enterprise auto-enrollment scenarios.

05

Microsoft DCOM Frontend

Support selected Microsoft DCOM interfaces for remote certificate requests and status queries on Windows.

06

LCEP Frontend

Enable certificate enrollment for supported Android and iOS applications using the intelliCard Mobile KeyStore library.

use cases

What can you use Certificate Hub for?

Certificate Hub enables automated certificate provisioning across different client technologies, enrollment protocols and Certificate Authority environments.It helps organizations connect devices and applications to existing PKI infrastructure, reduce enrollment compatibility issues and standardize certificate provisioning.

Device & Application Certificate Enrollment

Automate certificate enrollment across different devices and applications.Support certificate provisioning for network devices, web services and mobile applications using compatible enrollment protocols.

Network Device Certificate Enrollment

Provision certificates for compatible network devices using SCEP and EST enrollment interfaces.

Automated TLS Certificate Enrollment

Automate certificate requests for supported web servers and TLS services using ACME.

Mobile Application Certificate Enrollment

Enable certificate provisioning for supported Android and iOS applications using LCEP and the intelliCard Mobile

Microsoft & Enterprise PKI Integration

Connect Microsoft environments and existing Certificate Authorities. Simplify certificate enrollment across enterprise systems while retaining your existing PKI infrastructure.

Microsoft Certificate Auto-Enrollment

Support Microsoft certificate enrollment scenarios using CEP, CES and selected DCOM interfaces.

Multi-CA Certificate Provisioning

Connect supported certificate consumers to internal, external and Trust Center Certificate Authorities through compatible enrollment frontends.

Enrollment Standardization & Automation

Standardize certificate enrollment across heterogeneous infrastructure.Reduce protocol compatibility challenges and manual administration through a centralized enrollment layer.

Enterprise Enrollment Standardization

Provide consistent certificate enrollment interfaces across diverse devices, applications and organizational environments.

Enrollment Policy & Template Management

Apply supported standard or customized certificate templates and configured enrollment policies to meet organizational requirements.

hOW CERTIFICATE HUB WORKS

How does Certificate Hub work?

Certificate Hub sits between certificate consumers and connected Certificate Authorities, providing enrollment interfaces that match the technical requirements of different clients.

Devices and applications submit certificate requests through supported protocols. Certificate Hub processes those requests through its configured frontend and backend integration, allowing certificates to be issued through the connected CA infrastructure.

From the client's perspective, the frontend behaves like a Certificate Authority, reducing the need for direct integration with each backend CA.

01

Protocol-Based Enrollment

Accept certificate requests through supported enrollment interfaces including ACME, SCEP, EST and Microsoft protocols.

02

CA Connectivity

Connect supported certificate consumers to existing internal, external or Trust Center Certificate Authorities.

03

Enrollment Policy Control

Apply configured enrollment policies and standard or customized certificate templates.

04

Auditing & Notification

Support operational oversight through auditing and certificate lifecycle event notifications

DEPLOYMENT

Deploy Certificate Hub within your enterprise infrastructure.

Certificate Hub supports deployment of its protocol-specific frontends on supported Linux and Windows servers, depending on the frontend.

The supplied product information also describes clustering, tenant separation and a hardened software stack to support enterprise operational and security requirements.

Linux

Linux-based deployment

Deploy supported Certificate Hub enrollment frontends on Linux servers, depending on protocol and configuration requirements.

Best for: Organizations using Linux infrastructure for certificate enrollment services.
Windows

Windows-based deployment

Run supported enrollment frontends in Windows environments, including Windows-specific certificate enrollment interfaces.

Best for: Microsoft-oriented enterprise environments and Windows-based enrollment workflows.
Enterprise Scale

Built for enterprise operations

Support enterprise requirements through clustering capabilities, tenant separation and a hardened software stack.

Best for: Organizations requiring scalable, multi-tenant certificate enrollment infrastructure.
CERTIFICATE HUB IN PRACTICE

Simplify certificate enrollment across your PKI.One enrollment layer. Multiple protocols. Existing CAs.

Certificate Hub connects different certificate consumers to supported Certificate Authorities through protocol-specific enrollment interfaces.

By bridging differences between client requirements and CA interfaces, it helps organizations automate certificate provisioning without replacing their existing PKI infrastructure.

certificate hub FAQ

Frequently asked questions about Certificate Hub

Answers to common questions about Certificate Hub, certificate enrollment protocols, CA compatibility, automation and enterprise deployment.

What is Certificate Hub?

Certificate Hub, also called Enrollment Hub, is an ID Security certificate enrollment platform that connects devices, applications and enterprise systems to Certificate Authorities through protocol-specific frontends. It helps overcome differences between client enrollment requirements and CA interfaces, enabling more consistent certificate provisioning across heterogeneous PKI environments.

What certificate enrollment protocols does Certificate Hub support?

Certificate Hub supports ACME, SCEP/NDES, EST, Microsoft Certificate Enrollment Policy (CEP) and Certificate Enrollment Service (CES), Microsoft DCOM and the proprietary Lightweight Certificate Enrollment Protocol (LCEP). Each frontend addresses different client technologies and certificate enrollment requirements.

Does Certificate Hub work with existing Certificate Authorities?

Yes. Certificate Hub is designed to connect compatible certificate consumers with existing internal, external and Trust Center Certificate Authorities. It provides an enrollment layer between clients and supported CA interfaces, reducing the need to replace existing PKI infrastructure.

What is the difference between Certificate Hub and CEMA?

Certificate Hub focuses on certificate enrollment and protocol compatibility between clients and Certificate Authorities. CEMA is an enterprise Certificate Lifecycle Management platform designed for broader certificate lifecycle automation, centralized visibility, administration and governance across PKI environments. The products address different, potentially complementary requirements.

Does Certificate Hub support automated certificate enrollment?

Yes. Certificate Hub supports automated certificate provisioning through its protocol-specific frontends. Compatible clients can request certificates using supported enrollment protocols, reducing the need for manual certificate requests and custom client-side integrations. The available automation depends on the frontend, connected CA and configuration.

Does Certificate Hub support ACME?

Yes. Certificate Hub includes an ACME frontend for automated certificate enrollment using supported domain or resource ownership validation methods. ACME is commonly used for automating TLS certificate provisioning for web servers and compatible infrastructure.

Does Certificate Hub support SCEP and Microsoft NDES?

Yes. Certificate Hub provides a SCEP frontend supporting certificate enrollment for compatible clients, including environments using Microsoft's Network Device Enrollment Service (NDES) approach. SCEP is commonly used for network devices and managed endpoints.

Can Certificate Hub support Microsoft certificate auto-enrollment?

Yes. Certificate Hub provides Microsoft CEP and CES frontends and a selected implementation of Microsoft DCOM certificate enrollment interfaces. These support compatible Microsoft certificate enrollment and auto-enrollment scenarios. Specific capabilities depend on the frontend and deployment configuration.

Can Certificate Hub enroll certificates for mobile applications?

Yes. Certificate Hub includes an LCEP frontend for supported Android and iOS applications using the intelliCard Mobile KeyStore library. LCEP provides a proprietary certificate enrollment interface designed for applications integrated with that library.

Does Certificate Hub support multiple tenants?

Yes. The Certificate Hub product information describes tenant separation as an enterprise security capability. This supports separating enrollment environments for different organizational requirements. The exact tenant configuration and isolation model should be confirmed for the intended deployment.

Can organizations configure certificate enrollment policies?

Yes. Certificate Hub supports configurable enrollment policies and standard or customized certificate templates. These help organizations control certificate provisioning according to their requirements. Available policy settings depend on the supported frontend and connected Certificate Authority.

Where can Certificate Hub be deployed?

Certificate Hub supports deployment of protocol-specific enrollment frontends on supported Linux and Windows servers, depending on the frontend. The product information also describes clustering capabilities and a hardened software stack. Supported operating systems, versions and configurations should be confirmed before deployment.

READY TO GET STARTED?

Simplify certificate enrollment with Certificate Hub.

Connect your devices, applications and enterprise systems to existing Certificate Authorities through flexible enrollment interfaces.Discuss your infrastructure, protocol requirements and certificate provisioning challenges with the ID Security team.