From b8ff392e8bf6aa2e05211f84bb9bee4f78dfefbb Mon Sep 17 00:00:00 2001 From: Anna Stuchlik Date: Thu, 14 Sep 2023 12:49:21 +0200 Subject: [PATCH] doc: add info - support for FIPS-compliant systems This commit adds the information that ScyllaDB Enterprise supports FIPS-compliant systems in versions 2023.1.1 and later. The information is excluded from OSS docs with the "only" directive, because the support was not added in OSS. This commit must be backported to branch-5.2 so that it appears on version 2023.1 in the Enterprise docs. Closes #15415 (cherry picked from commit fb635dccaac7b2ffc81e2aee1374faebee22acab) --- docs/operating-scylla/security/security-checklist.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/operating-scylla/security/security-checklist.rst b/docs/operating-scylla/security/security-checklist.rst index 1db8f81c4d..adcacd5fd8 100644 --- a/docs/operating-scylla/security/security-checklist.rst +++ b/docs/operating-scylla/security/security-checklist.rst @@ -31,7 +31,11 @@ Encryption on Transit, Client to Node and Node to Node Encryption on Transit protects your communication against a 3rd interception on the network connection. Configure Scylla to use TLS/SSL for all the connections. Use TLS/SSL to encrypt communication between Scylla nodes and client applications. -See: +.. only:: enterprise + + Starting with version 2023.1.1, you can run ScyllaDB Enterprise on FIPS-enabled Ubuntu, + which uses FIPS 140-2 certified libraries (such as OpenSSL, GnuTLS, and more) and Linux + kernel in FIPS mode. * :doc:`Encryption Data in Transit Client to Node `