This guide is part of the support provided by Utimaco. Additional documentation produced to support your Utimaco u.trust General Purpose (GP) Hardware Security Module (HSM) product can be found in the document directory of the Utimaco u.trust GP HSM product bundle.
All Utimaco u.trust GP HSM product documentation is available from Utimaco’s website at https://utimaco.com/.
About This Guide
This guide describes how to integrate a Utimaco u.trust GP HSM with Cloudflare Keyless SSL. The Utimaco HSM securely stores the private key used for TLS/SSL and performs all cryptographic signing operations within the hardware, ensuring that the private key never leaves the HSM. Cloudflare Keyless SSL enables secure delivery of web traffic through Cloudflare’s global network while allowing the private key to remain under the customer’s control.
In this integration, Cloudflare handles the majority of the TLS handshake at the edge. Whenever a private key operation is required, Cloudflare securely forwards the request to a customer-managed key server running the GoKeyless service. This service interacts with the Utimaco HSM via the PKCS#11 interface to perform cryptographic operations such as signing. This approach ensures that sensitive key material is protected within the HSM at all times, while still leveraging Cloudflare’s CDN, DDoS protection, and performance optimizations.
Target Audience
This guide is intended for Cloudflare Keyless SSL and Utimaco HSM administrators.
Purpose of the Integration
The integration of Cloudflare Keyless SSL with u.trust GP HSM serves a critical role in enhancing the security, compliance, and performance of TLS/SSL operations by ensuring that private keys are securely stored within the HSM while leveraging Cloudflare’s global edge network for handling client connections and traffic optimization.
Abbreviations
|
Abbreviation |
Meaning |
|---|---|
|
HSM |
Hardware Security Module |
|
PKCS#11 |
Public-Key Cryptography Standards #11 (Cryptographic Token Interface) |
|
SSL |
Secure Sockets Layer |
|
TLS |
Transport Layer Security |
|
CSR |
Certificate Signing Request |
|
CA |
Certificate Authority |
|
DNS |
Domain Name System |
|
FQDN |
Fully Qualified Domain Name |
|
HTTP |
Hypertext Transfer Protocol |
|
HTTPS |
Hypertext Transfer Protocol Secure |
|
API |
Application Programming Interface |
|
mTLS |
Mutual Transport Layer Security |
|
SKI |
Subject Key Identifier |
|
PEM |
Privacy-Enhanced Mail (Base64 encoded certificate format) |
|
URI |
Uniform Resource Identifier |
|
IP |
Internet Protocol |
|
VM |
Virtual Machine |
|
CDN |
Content Delivery Network |
|
DDoS |
Distributed Denial of Service |
|
RHEL |
Red Hat Enterprise Linux |
|
MBK |
Master Backup Key |
|
SO |
Security Officer |
|
LAN |
Local Area Network |
|
PCIe |
Peripheral Component Interconnect Express |
|
DNF |
Dandified YUM (package manager for RHEL-based systems) |
|
DN |
Distinguished Name |
|
CN |
Common Name |
|
EPEL |
Extra Packages for Enterprise Linux |
Abbreviations
Document Conventions
The following conventions are used in this guide:
|
Convention |
Use |
Example |
|---|---|---|
|
Bold |
Items of the Graphical User Interface (GUI), e.g., menu options |
Select Details and click on Properties button |
|
|
Code that is given for explanation or as an example, file paths |
|
|
Italic |
References and important terms |
Operating system listed in Tested Versions |
Document conventions
We use special icons to highlight the most important notes and information.
Here you will find important safety information that should be followed.
Here you will find additional notes or supplementary information.
This message indicates the expected result after the successful execution of an instruction.