@@ -111,21 +111,49 @@ transport encryption.
111111
112112For details, see :ref:`rotate-encryption-keys`.
113113
114- Logging
115- ~~~~~~~
114+ Audit Log
115+ ~~~~~~~~~
116116
117- .. versionadded:: 3.4 Available in MongoDB Enterprise only
117+ Available in MongoDB Enterprise only.
118118
119- The log file is not encrypted as a part of MongoDB's encrypted storage engine.
120- A :binary:`~bin.mongod` running with :ref:`logging <monitoring-standard-loggging>`
121- may output potentially sensitive information to log files as a part of normal
122- operations, depending on the configured :ref:`log verbosity
123- <log-messages-configure-verbosity>`.
119+ .. _security-encryption-at-rest-audit-log:
124120
125- MongoDB 3.4 Enterprise provides the :setting:`security.redactClientLogData`
126- setting to prevent potentially sensitive information from entering the
127- :binary:`~bin.mongod` process log. :setting:`~security.redactClientLogData`
128- reduces detail in the log and may complicate log diagnostics.
121+ Use KMIP Server to Manage Keys for Encrypting the MongoDB Audit Log
122+ ```````````````````````````````````````````````````````````````````
123+
124+ Starting in MongoDB 5.3 Enterprise, you can use an external Key
125+ Management Interoperability Protocol (KMIP) server to securely manage
126+ the keys for encrypting the MongoDB audit log.
127+
128+ To use a KMIP server with audit log encryption, configure these settings
129+ and parameters:
130+
131+ - :setting:`auditLog.auditEncryptionKeyIdentifier` setting
132+ - :setting:`auditLog.compressionMode` setting
133+ - :parameter:`auditEncryptionHeaderMetadataFile` parameter
134+ - :parameter:`auditEncryptKeyWithKMIPGet` parameter
135+
136+ For testing audit log encryption, you can also use the
137+ :setting:`auditLog.localAuditKeyFile` setting.
138+
139+ Unencrypted Audit Log and Process Log
140+ `````````````````````````````````````
141+
142+ This section applies if you are not using an external Key Management
143+ Interoperability Protocol (KMIP) server to manage keys for encrypting
144+ the audit log as shown in the previous section.
145+
146+ The audit log file is not encrypted as a part of MongoDB's encrypted
147+ storage engine. A :binary:`~bin.mongod` running with :ref:`logging
148+ <monitoring-standard-loggging>` may output potentially sensitive
149+ information to log files as a part of normal operations, depending on
150+ the configured :ref:`log verbosity <log-messages-configure-verbosity>`.
151+
152+ Use the :setting:`security.redactClientLogData` setting to prevent
153+ potentially sensitive information from entering the
154+ :binary:`~bin.mongod` process log.
155+ :setting:`~security.redactClientLogData` reduces detail in the log and
156+ may complicate log diagnostics.
129157
130158See the :ref:`log redaction <monitoring-log-redaction>` manual entry for
131159more information.
0 commit comments