From 3150bbf7a72c4bc38cd9c364a5727c93a57cd09e Mon Sep 17 00:00:00 2001 From: Daniel Hougaard Date: Mon, 17 Nov 2025 10:40:51 -0800 Subject: [PATCH] Update production-hardening.mdx --- docs/self-hosting/guides/production-hardening.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/self-hosting/guides/production-hardening.mdx b/docs/self-hosting/guides/production-hardening.mdx index 5e63f2b6e..8982d6b62 100644 --- a/docs/self-hosting/guides/production-hardening.mdx +++ b/docs/self-hosting/guides/production-hardening.mdx @@ -698,7 +698,7 @@ For enterprise deployments requiring compliance certifications: Infisical is compliant with FIPS 140-3, meeting U.S. and Canadian government cryptographic standards through validated cryptographic modules. This certification is designed for organizations that require government-approved encryption implementations. -To deploy a FIPS-compliant instance, use the `infisical/infisical-fips` Docker image, available to Enterprise customers. +To deploy a FIPS-compliant instance, use the [infisical/infisical-fips](https://hub.docker.com/r/infisical/infisical-fips) Docker image, available to Enterprise customers. Our FIPS 140-3 attestation letter is available in the [Infisical Trust Center](https://trust.infisical.com/). #### SOC 2 Compliance