From d783db16674094578ba45deb491e18b8ef0c0cfc Mon Sep 17 00:00:00 2001 From: Scott Miller Date: Thu, 27 Jan 2022 15:30:55 -0600 Subject: [PATCH] Clarify that backend authors can specify that all or no values are sealwrapped (#13813) * Clarify that backend authors can specify that all or no values are sealwrapped rather than the vague statement that all values _may_ be seal wrapped * typo --- website/content/docs/enterprise/sealwrap.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/enterprise/sealwrap.mdx b/website/content/docs/enterprise/sealwrap.mdx index fe72e894ba..d4621ea6e1 100644 --- a/website/content/docs/enterprise/sealwrap.mdx +++ b/website/content/docs/enterprise/sealwrap.mdx @@ -74,8 +74,8 @@ backend with the `seal_wrap` configuration value set to `true`. (This value cannot currently be changed later.) A given backend's author can specify which values should be seal-wrapped by -identifying where CSPs are stored. If no specific CSPs are identifiable, all -data for the backend may be seal-wrapped. +identifying where CSPs are stored. They may also choose to seal wrap all or none +of their values. To see the current list of seal-wrapped data per backend type, see the latest audit letter and updates in the FIPS 140-2 Compliance section above.