@@ -146,7 +146,7 @@ form on both the server and the network. While all clients have access
146
146
to the non-sensitive data fields, only appropriately-configured CSFLE
147
147
clients are able to read and write the sensitive data fields.
148
148
149
- The following diagram is a list of MongoDB security features offered
149
+ The following diagram is a list of MongoDB security features offered
150
150
and the potential security vulnerabilities that they address:
151
151
152
152
.. image:: /figures/CSFLE_Security_Feature_Chart.png
@@ -287,8 +287,8 @@ the same MongoDB replica set as the encrypted data.
287
287
your data encryption keys remotely.
288
288
289
289
To learn how to use a KMS in your CSFLE implementation, read the
290
- `Client-Side Field Level Encryption: Use a KMS to Store the Master Key
291
- </use-cases/client-side-field-level-encryption-local-key-to-kms>`_
290
+ :doc: `Client-Side Field Level Encryption: Use a KMS to Store the Master Key
291
+ </use-cases/client-side-field-level-encryption-local-key-to-kms/>`
292
292
guide.
293
293
294
294
To begin development, MedcoMD engineers generate a master key and save it
@@ -1046,9 +1046,9 @@ your data encryption keys would be readable by anyone that gains direct
1046
1046
access to your master key, we **strongly recommend** that you use a more
1047
1047
secure storage location such as a Key Management System (KMS).
1048
1048
1049
- For more information on securing your master key, see our `step-by-step
1049
+ For more information on securing your master key, see our :doc: `step-by-step
1050
1050
guide to integrating with Amazon KMS
1051
- </use-cases/client-side-field-level-encryption-local-key-to-kms>`_ .
1051
+ </use-cases/client-side-field-level-encryption-local-key-to-kms/>` .
1052
1052
1053
1053
Further Reading
1054
1054
~~~~~~~~~~~~~~~
0 commit comments