You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/core/security-encryption-at-rest.txt
+18-1Lines changed: 18 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,24 @@ Standard in Cipher Block Chaining mode) via OpenSSL. AES-256 uses a
49
49
symmetric key; i.e. the same key to encrypt and decrypt text. MongoDB
50
50
Enterprise for Linux also supports authenticated encryption
51
51
``AES256-GCM`` (or 256-bit Advanced Encryption Standard in
52
-
Galois/Counter Mode). FIPS mode encryption is also available.
52
+
Galois/Counter Mode).
53
+
54
+
The Encrypted Storage Engine uses the certified cryptography provider
55
+
of the underlying operating system to perform cryptographic operations.
56
+
For example, a MongoDB installation on a Linux operating system
57
+
uses the OpenSSL ``libcrypto`` FIPS-140 module.
58
+
59
+
To run MongoDB in a FIPS-compliant mode:
60
+
61
+
#. Configure the operating system to run in FIPS-enforcing mode.
62
+
63
+
#. Configure MongoDB to enable the :setting:`net.tls.FIPSMode` setting.
64
+
65
+
#. Restart the ``mongod`` or ``mongos``.
66
+
67
+
#. Check the server log file to confirm that FIPS mode is enabled. If FIPS mode is enabled, the message ``FIPS 140-2 mode activated`` appears in the log file.
68
+
69
+
For more information, see :ref:`configure-mdb-for-fips`.
0 commit comments