https://store-images.s-microsoft.com/image/apps.7356.b7c72bc1-2906-4066-b672-cfe9e1878ad8.145f2a88-c88e-4264-88c9-23c4c17d66b9.9095965c-cbe3-4816-be90-558759d12fb7
HSM Ingress Controller by Strid Tech
Strid Tech
HSM Ingress Controller by Strid Tech
Strid Tech
HSM Ingress Controller by Strid Tech
Strid Tech
Ingress that integrates with AKV or mHSM to handle TLS offload in AKS for FIPS 140-3 compliance
The Ingress Controller that makes AKS cluster comply with FIPS 140-3. By offloading TLS termination to Azure KeyVault (with non-exportable keys) or Azure Managed HSM, the keys stay secure as required by FIPS 140-3 up to level 3.
Extra Azure resources needed are:- Azure KeyVault or Azure Managed HSM
- Service Account with access to the above
- A AKS cluster
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.
To be FIPS compliant you must use non-exportable keys. Read more about Key Vault and FIPS compliance in the links.