Nginx and HSM integration to hold private keys

Question

We are using Nginx and storing private keys in a file on the server. We would like to move our private keys to an HSM so that SSL keys are stored in the HSM and never leave the HSM. All crypto operations required during SSL termination can be done on the HSM.

After Heartbleed, we have seen a lot of articles suggesting the use of an HSM, but we were not able to find how this can be enabled/added to Nginx. We found a patch enabling engine Keyform to read private keys from the engine. Instead of reading keys from a PKCS#11 supported engine, we would like to use the HSM to do all crypto operations so SSL keys never leave the HSM.

Is there any existing Nginx/OpenSSL plugin/module/implementation which can help us achieve this? I have seen a lot of articles talking about SSL termination using an HSM, but couldn't find any implementation details. So before I start digging into Nginx/OpenSSL code, I would like to hear if anyone has some suggestion or recommendation for this problem.

Answer 1

I've never done this before. But here are some suggestive pointers. These points are NOT concrete steps to get it working. From the documentation for the new AWS CloudHSM (not classic) offering:

1. Setup CloudHSM and generate private key using the CLI utility.
2. Install and configure the CloudHSM OpenSSL library.
3. Check if engine works openssl engine -t cloudhsm
4. Configure Nginx. Since Nginx 1.7.9, you can specify an engine for the private keys

The value engine:name:id can be specified instead of the file (1.7.9), which loads a secret key with a specified id from the OpenSSL engine name.

So your nginx config would look something like this

ssl_certificate_key cloudhsm:<name>:<keyid>;

I'm not quite sure what the name would be or the keyID. I'll read-up a bit and edit this answer if I find something.

Note: Also, per documentation, you might have to set the ssl_engine to cloudhsm if you want to enable SSL acceleration (doing the crypto in the HSM).

ssl_engine cloudhsm;

4. test.

May I ask why you wouldn't want to offload your SSL at the Load Balancers using AWS ACM? That's the easiest way to do it and it's secure if you trust AWS to be secure.

---

edit: I read a bit and I'm more or less certain that the Key Handle in CloudHSM parlance - the 6-digit numeric Identifier - is the keyid here. I also think user name is the name part. So your Nginx config could be:

# something that looks like:
ssl_certificate_key cloudhsm:AWSUser:568900;

edit2: Nginx compilation is not necessary. We just have to make sure that the openssl engine is loadable. Once configured, this is what it looks like when verifying:

[root@ip-172-31-14-127 ~]# export n3fips_password=user_cu:Wzs8sukUp7FkVs4xQU
[root@ip-172-31-14-127 ~]# openssl engine -t cloudhsm
(cloudhsm) CloudHSM hardware engine support
     SDK Version: 2.03
[ available ]

edit3: Good news! According to this forum post, Amazon is working on better documentation for Nginx integration with CloudHSM.

edit4: AWS has updated their documentation to include instructions for Apache and Nginx. I seem to have got it slightly right! ;) So, apparently, you download a "fake private key" and use it in your Nginx config. The rest of the instructions hold well.

Regardless of which method you choose, you then export a private key handle from the HSMs and save it to a file. The file doesn't contain the actual private key. It contains a reference to the handle of the private key that is stored on the HSMs. The file's contents are known as a fake PEM format private key. Your web server software uses the fake PEM format private key file, along with the AWS CloudHSM software library for OpenSSL, to offload SSL or TLS processing to the HSMs in your cluster

Documentation here: https://docs.aws.amazon.com/cloudhsm/latest/userguide/ssl-offload.html

I haven't tested this yet. Will post an update once I do.

Answer 2

For the benefit of anyone else who found this post via Googling "cloudhsm nginx" like I did: the answer from @eternaltyro is almost correct. But instead of referencing the key ID in the cloudhsm:<name>:<keyid>; format, you use the getCaviumPrivKey function in CloudHSM's key_mgmt_util to export the key as a "fake" PEM file, then point the nginx ssl_certificate_key at that file. You should also set the ssl_engine to cloudhsm as stated.

Answer 3

As you are using Safenet (Now Gemalto)Luna HSM SA 7000. You could add an abstraction layer for Key Management Service. For Example -Gemalto's Key Secure Appliance (they do they virtual appliance).

KMS integrates with HSM. You need to register Key Management service with HSM then each of the transaction from KMS would be wrapped with a master key which is in one of the partitions registered on your HSM.

I worked on HSM and KeySecure But never did SSL termination. To start off if you could try SSL with KMS(w/without HSMs), I can help with rest of the integrations.