liveBook · Manning

Data at rest

As explained in Spring Security in Action, Second Edition

Data at rest is persisted information stored in computer storage rather than being transmitted between systems.

Data at rest is persisted information held in computer storage rather than exchanged between systems. It includes application records, credentials, and private keys. section 1.2

Protect persisted and retained sensitive data by:

  • Encrypting data with a private key or hashing it instead of storing every value in readable form. section 1.2
  • Storing secrets such as credentials and private keys carefully, usually in a secrets vault. section 1.2
  • Considering sensitive values retained in application memory: a heap dump can expose credentials or private keys. section 1.2

How Spring Security in Action, Second Edition covers it

How deep it goes
Defines persisted data, recommends encryption, hashing, and vault storage, but stops short of implementation procedures.
Examples
Uses persisted records, credentials, private keys, secrets vaults, and heap dumps as concrete security examples.
What it assumes
Introduces the distinction between persisted and exchanged data without assuming prior security terminology.
What you can do after
Evaluate whether stored or retained sensitive values require encryption, hashing, vault storage, or reduced memory lifetime.
How it connects
Contrasts with data in transition and connects to secrets vaults, application memory, heap dumps, and application security.
Cover of Spring Security in Action, Second Edition
liveBookmanning.com
Read Spring Security in Action, Second Edition on liveBook Get the book at manning.com

Also explained in

Compare how 3 books explain data at rest →

Related concepts

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