Protect your Azure Kubernetes cluster's TLS keys from leaking with our Ingress Controller. By offloading TLS termination to your Azure Key Vault or Azure Managed HSM, the keys stay secure, as required by FIPS 140-3 up to level 3.

Click the "Get It Now" button on the upper left to install the ingress into your cluster or create a new cluster for testing. We will get in contact with you shortly or you can reach out to us directly at info@strid.tech.

Key Benefits

No insecure secrets - By terminating TLS directly in the Key Vault we don't need to use the insecure secrets in Kubernetes to manage our private keys.

FIPS 140-3 - By offloading TLS termination to either Azure KeyVault Premium or Azure Managed HSM you can attain FIPS 140-3 level 3 compliance in your cluster ingress*.

Seamless Migration - The Ingress Controller is fully compatible with the open source nginx-ingress and can be configured the same ways for easy replacement of your current solution.

Installation

Extra Azure resources needed are:

• Azure Key Vault or Azure Managed HSM
• Service Account with access to the above

* To be FIPS compliant you must use non-exportable keys. Read more about Key Vault and FIPS compliance under "Learn more".