- Security >
- Encryption >
- In-Use Encryption >
- Introduction >
- Reference >
- Server-Side Schema Enforcement
Server-Side Schema Enforcement¶
On this page
In ()-enabled client applications, you
can use schema validation
to have your MongoDB instance enforce encryption of specific fields.
To specify which fields require encryption, use the
automatic encryption rule keywords
with the $jsonSchema
validation object. The server rejects any write operations to that collection
where the specified fields are not Binary (BinData)
subtype 6 objects.
To learn how a -enabled client configured to use automatic encryption behaves when it encounters a server-side schema, see Server-Side Field Level Encryption Enforcement.
- To learn how a -enabled client configured to use
- behaves when it encounters a server-side schema,
see Server-Side Field Level Encryption Enforcement.
Example¶
Consider an hr
database with an employees
collection.
Documents in the employees
collection have the following form:
You want to enforce the following behavior for client applications using your collection:
- When encrypting the
age
field, clients must follow these encryption rules:- Use the with an
_id
ofUUID("e114f7ad-ad7a-4a68-81a7-ebcb9ea0953a")
. - Use the randomized encryption algorithm.
- The
age
field must be an integer.
- Use the with an
- When encrypting the
name
field, clients must follow these encryption rules:- Use the with an
_id
ofUUID("33408ee9-e499-43f9-89fe-5f8533870617")
. - Use the deterministic encryption algorithm.
- The
name
field must be a string.
- Use the with an
The following mongosh
code uses the
collMod
command to update the hr.employees
collection to include a validator
to enforce the
preceding behavior:
Learn More¶
To learn more about the encryption algorithms supports, see Fields and Encryption Types.
To learn more about encryption schemas and encryption rules, see Encryption Schemas.