liveBook · Manning

Data at rest

Data at rest is digital information stored on persistent or nonvolatile media rather than actively transmitted across a network.

How 4 Manning books explain it

Spring Security in Action, Second Edition

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

How it is used
Protects persisted application data and retained secrets as part of application security.
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 you can do after
Evaluate whether stored or retained sensitive values require encryption, hashing, vault storage, or reduced memory lifetime.

Read how Spring Security in Action, Second Edition explains data at rest →

Fundamentals of Cybersecurity

Data at rest is data stored on a device or medium rather than actively moving across a network or being processed.

How it is used
Uses data states to distinguish stored information from data being transmitted or processed when choosing protection strategies.
How deep it goes
Defines stored data, identifies unauthorized access as a risk, and names encryption and access controls without detailing their implementation.
Examples
Uses databases and device hard drives as storage examples, including encrypting a database of customer records.
What you can do after
Evaluate stored-data exposure and select encryption and access controls as protections.

Read how Fundamentals of Cybersecurity explains data at rest →

Data-Driven Cybersecurity

Data at rest is data stored on a persistent medium rather than actively moving across a network or being processed.

How it is used
Frames stored information as an asset requiring encryption, access control, integrity monitoring, and continuous security maintenance.
How deep it goes
Details storage locations, encryption models, key roles, integrity checks, access controls, and algorithm obsolescence.
Examples
Uses on-premises servers, cloud storage, off-site backups, and a physical-vault analogy.
What you can do after
Operate/configure: protect stored information with encryption, restricted access, integrity checks, and current security protocols.

Read how Data-Driven Cybersecurity explains data at rest →

AI-Powered Developer: Build software with ChatGPT and Copilot

Data at rest is data stored on persistent or nonvolatile media rather than actively moving across a network.

How it is used
Protects stored sensitive information from unauthorized reading or alteration during secure application development.
How deep it goes
Explains risks, demonstrates Python and SQLite3 encryption, and stops short of prescribing a complete production architecture.
Examples
Uses a Fernet Python snippet, a SQLite3 database workflow, and the Ashley Madison breach as concrete examples.
What you can do after
Apply it via Python's cryptography library to encrypt sensitive values before storing them in SQLite3.

Read how AI-Powered Developer: Build software with ChatGPT and Copilot explains data at rest →

Also covered in

What to know first

Related concepts

Questions about data at rest

What is data at rest?

Data at rest is digital information stored on persistent or nonvolatile media rather than actively transmitted across a network.

Which Manning books explain data at rest?

Spring Security in Action, Second Edition, Fundamentals of Cybersecurity, Data-Driven Cybersecurity and AI-Powered Developer: Build software with ChatGPT and Copilot.

What should I know before learning data at rest?

Manning books that teach data at rest usually introduce authorization, encryption, HTTPS and security first.

What is the difference between data at rest and data transfer?

Data at rest is digital information stored on persistent or nonvolatile media rather than actively transmitted across a network. Data transfer is the movement of digital information between memory locations, computing components, systems, or network endpoints.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.