GaraSign For TLS

Transport Layer Security (TLS) is the industry standard protocol for securing data in transit. Two of the biggest challenges with TLS are protecting the TLS keys and managing their certificates. TLS keys are often stored in software directly on web servers, leaving them vulnerable to compromise. For large enterprises managing many servers, this creates serious risk and makes certificate lifecycle management difficult. 

With GaraSign, TLS keys are secured in a hardware security module (HSM), rather than in software or stored locally on servers. Avoiding outages with timely rotation of certificates is greatly simplified, as all keys, certificates & code signing solutions are centrally managed in the HSM.

TLS is ubiquitous throughout enterprise IT environments.

How do you securely manage all the TLS keys and certificates?

The industry standard for enterprise organizations is to encrypt all network traffic with Transport Layer Security (TLS). For enterprises, this presents two challenges: the TLS keys must be secured and the certificates must be renewed prior to expiration to avoid outages and downtime.

All too often, TLS keys and certificates are stored locally in software on servers. This doesn’t provide adequate security, nor does it enable easy certificate rotation, as the certificates are not centrally managed.

Minimal TLS Key Protection

Storing TLS keys in software on end-point devices and servers leaves them vulnerable to compromise by attackers.

Certificate Outages

Secure Sockets Layer (SSL/TLS) certificates must be renewed to avoid outages, but it's hard to do so when they aren't centrally managed by an HSM.

TLS Key Sprawl & Compliance

Many servers means many keys, making it difficult to remain compliant and meet TLS key management requirements.

With GaraSign, all TLS keys and certificates are centrally managed and secured in the Hardware Security Module (HSM).

Secure Access To The Hardware Security Module (HSM)-Protected TLS Keys

GaraSign is deployed on customer-managed infrastructure between the HSM and the servers, restricting those servers to proxied key access. 

The result is that TLS keys remain secured and non-exportable in the HSM, while servers can use the keys they need to perform Transport Layer Security (TLS) handshakes and protect network traffic. GaraSign further secures HSM keys via granular access controls and features, such as device authentication, IP address whitelisting, and more.

HSM Centrally-Managed Certificates

When you deploy GaraSign, all Transport Layer Security (TLS) certificates are centrally-managed in the Hardware Security Module (HSM) Software. This ensures easy certificate rotation to prevent outages and costly downtime. It’s also easy to perform other certificate lifecycle management tasks.

TLS Enterprise Key Management Made Easy

No matter how many TLS keys and TLS certificates in a given environment, GaraSign enables enterprises to manage and audit their infrastructure from a centralized Hardware Security Module (HSM) software location. Using this HSM as a service approach, administrators always maintain full visibility on all TLS keys. GaraSign creates a detailed log for each TLS key, making it easy to audit key usage to see when these TLS keys were used, at what time, and by which users.

Client TLS Certificate Authentication

GaraSign can also be used to manage the TLS keys and certificates used for client authentication (aka mutual TLS). This can be used to enable Privileged Access Management (PAM), via features like multi-factor and device authentication (MFA), without reconfiguring servers.

GaraSign for Transport Layer Security (TLS) FAQs

The main benefit is that the sensitive private Hardware Security Module (HSM) keys are never exported. There are additional benefits in that HSM certificate management can be automated and advanced security controls can be put in place on the HSM keys.

GaraSign supports both. Web applications should have their Transport Layer Security (TLS) keys protected by GaraSign to ensure attackers can't impersonate them by stealing the private TLS key. Clients that use Mutual TLS should have the client's private key protected by GaraSign to provide centralized auditing, automated TLS certificate management, and seamless deployment of additional security controls.

While there is an extra network hop added, the performance impact is minimal since this Hardware Security Module (HSM) key is only used during the initial Transport Layer Security (TLS) handshake. After the handshake is complete, GaraSign is no longer needed.

When using Mutual Transport Layer Security (TLS), GaraSign can proxy the client TLS key used to complete the challenge-response handshake. With the TLS key behind GaraSign's privileged access control, GaraSign can enforce additional security controls (e.g., MFA) before it allows the use of the HSM key. In other words, the web application delegates the additional security controls to GaraSign, and is not even aware that the additional privileged access controls are taking place.

Yes. GaraSign can transparently enforce privileged access security controls such as multi-factor authentication (MFA) without any new coding. Just turn on client-certificate authentication (either at your web server, load balancer, or some other proxy) and store the client private HSM keys in GaraSign. Then, for each of those TLS keys, set the policy to one that requires multi-factor authentication (or any other privileged access security control you would like to enforce).

GaraSign can automate the renewal process and make sure the clients and servers have the new Hardware Security Module (HSM) certificates they need. For extremely sensitive environments where HSM certificate automation is not permitted, GaraSign can alert administrators about certificates nearing expiration and they can decide what actions to take.

Give GaraSign a Try

Schedule a demo to see how GaraSign can improve the security and performance of cryptographic operations throughout your environment.