liveBook · Manning

Atlas In-Use Encryption

As explained in MongoDB 8.0 in Action, Third Edition

Atlas In-Use Encryption is a MongoDB security feature that keeps sensitive data encrypted on the client while it is processed and stored by the database.

Atlas In-Use Encryption keeps sensitive fields encrypted on the client before database processing and storage, so Atlas never receives plaintext. Authorized clients decrypt results only after retrieval. section 20.5.4

Key implementation characteristics:

  • Uses client-side field-level encryption (CSFLE) or Queryable Encryption for protected application data. section 20.5.4
  • Keeps decryption keys exclusively accessible to the application, preventing database administrators from viewing protected values. section 20.5.4
  • Supports external key management through AWS KMS, Azure Key Vault, GCP KMS, KMIP-compliant managers, or HashiCorp Vault. section 20.5.4

Encrypted customer field

An application encrypts a customer's Social Security number before sending the document. MongoDB stores a binary encrypted value instead of the plaintext field.

How MongoDB 8.0 in Action, Third Edition covers it

How deep it goes
Explains client-side encryption, key custody, encrypted documents, and query processing without detailing configuration steps.
Examples
Uses a customer document containing a Social Security number and an encrypted binary replacement.
What it assumes
Assumes an application client and customer-provisioned encryption keys while explaining field protection from the document level.
What you can do after
Evaluate how applications can keep sensitive fields hidden from MongoDB and database administrators.
How it connects
Connects client-side field-level encryption, Queryable Encryption, external key management, KMS, KMIP, and HashiCorp Vault.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of MongoDB 8.0 in Action, Third Edition. The section links point to the parts of the book it draws on.