From 57035d55b5574481d3e95d4fdefbca9334902bdc Mon Sep 17 00:00:00 2001 From: hc-github-team-secure-vault-core <82990506+hc-github-team-secure-vault-core@users.noreply.github.com> Date: Tue, 21 Nov 2023 11:01:17 -0500 Subject: [PATCH] backport of commit 66b3e439d80c7cb991ec31cd84d652c1001aa3f6 (#24220) Co-authored-by: Scott Miller --- website/content/docs/enterprise/fips/fips1402.mdx | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/website/content/docs/enterprise/fips/fips1402.mdx b/website/content/docs/enterprise/fips/fips1402.mdx index ce9fa9790..4d46dfa46 100644 --- a/website/content/docs/enterprise/fips/fips1402.mdx +++ b/website/content/docs/enterprise/fips/fips1402.mdx @@ -88,8 +88,12 @@ reasons: of say, a Root CA involves a concerted, non-Vault effort to accomplish and must be done thoughtfully. -Combined, we suggest leaving the existing cluster in place, and carefully -consider migration of specific workloads to the FIPS-backed cluster. +As such Hashicorp cannot provide support for workloads that are affected +either technically or via non-compliance that results from converting +existing cluster workloads to the FIPS 140-2 Inside binary. + +Instead, we suggest leaving the existing cluster in place, and carefully +consider migration of specific workloads to the FIPS-backed cluster. #### Entropy augmentation restrictions