scottk/vault
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/vault.git synced 2025-10-30 02:02:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document additional FIPS restrictions (#16208)

Browse Source 
Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
This commit is contained in:
Alexander Scheel
2022-06-30 17:14:07 -04:00
committed by GitHub
parent 3587d43f72
commit dd92ccb729
1 changed files with 25 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
website/content/docs/enterprise/fips/fips1402.mdx
View File

@@ -70,6 +70,8 @@ from the following sources:
### Usage Restrictions ### Usage Restrictions
#### Migration Restrictions
Hashicorp **does not** support in-place migrations from non-FIPS Inside Hashicorp **does not** support in-place migrations from non-FIPS Inside
versions of Vault to FIPS Inside versions of Vault, regardless of version. versions of Vault to FIPS Inside versions of Vault, regardless of version.
A fresh cluster installation is required to receive support. We generally A fresh cluster installation is required to receive support. We generally
@@ -89,11 +91,34 @@ reasons:
Combined, we suggest leaving the existing cluster in place, and carefully Combined, we suggest leaving the existing cluster in place, and carefully
consider migration of specific workloads to the FIPS-backed cluster. consider migration of specific workloads to the FIPS-backed cluster.
#### Entropy Augmentation Restrictions
Entropy Augmentation **does not** work with FIPS 140-2 Inside. The internal Entropy Augmentation **does not** work with FIPS 140-2 Inside. The internal
BoringCrypto RNG is FIPS 140-2 certified and does not accept entropy from BoringCrypto RNG is FIPS 140-2 certified and does not accept entropy from
other sources. Attempting to use Entropy Augmentation will result in failures other sources. Attempting to use Entropy Augmentation will result in failures
at runtime such as `panic: boringcrypto: invalid code execution`. at runtime such as `panic: boringcrypto: invalid code execution`.
#### TLS Restrictions
Vault Enterprise's FIPS modifications include restrictions to supported TLS
cipher suites and key information. Only the following cipher suites are
allowed:
- `TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`,
- `TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`,
- `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`,
- `TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`,
- `TLS_RSA_WITH_AES_128_GCM_SHA256`, and
- `TLS_RSA_WITH_AES_256_GCM_SHA384`.
Additionally, only the following key types are allowed in TLS chains of trust:
- RSA 2048, 3072, 4096, 7680, and 8192-bit;
- ECDSA P-256, P-384, and P-521.
Finally, only TLSv1.2 or higher is supported in FIPS mode. These are in line
with recent NIST guidance and recommendations.
## Technical Details ## Technical Details
Vault Enterprise's FIPS 140-2 Inside binaries rely on a special version of the Vault Enterprise's FIPS 140-2 Inside binaries rely on a special version of the