Encryption at rest protects stored backup data on disk or in object storage. Encryption in transit protects data while it moves between systems, such as during transfer or sync. In-app encryption protects the data before it becomes readable inside the application layer, reducing exposure through interfaces, clone operations, or internal access paths.
How the three encryption layers differ for backups
These three terms describe different protection points in the backup lifecycle. Encryption at rest protects a backup after it has been written to storage. Encryption in transit protects the backup while it is moving between systems. In-app encryption protects the content before the application can expose it in readable form, which is why it changes exposure through APIs, restores, clone operations, and internal operator paths.
The practical difference is not just where encryption happens, but what can still see plaintext. At-rest encryption mainly reduces exposure if storage is stolen, misread, or accessed outside the intended storage boundary. In-transit encryption mainly protects against interception and tampering on the network path. In-app encryption reduces trust in the surrounding platform by keeping sensitive data encrypted until the application explicitly unwraps or decrypts it.
For backup designs, those layers are complementary rather than interchangeable. A backup can be encrypted on disk yet still be exposed during transfer, or encrypted on the wire yet land in readable form once imported. In-app encryption is usually the strongest of the three for limiting application-layer visibility, but it also shifts more responsibility to key handling, application design, and restore workflow.
Where backup risk changes depending on the layer
The main risk distinction is blast radius. If at-rest encryption is the only control, anyone who can read the stored object and access the decryption path may still recover the backup. If in-transit encryption is missing, the data can be exposed before it even reaches backup storage. If in-app encryption is absent, administrators, connectors, or cloned environments may see more plaintext than the business expects.
Backup teams also need to think about operational failure modes. Restore jobs, test clones, and migration tooling often create extra places where decrypted data appears temporarily. That makes encryption at the storage layer useful, but insufficient on its own if the application or restore process routinely materialises plaintext in staging, logs, or downstream copies.
For organisations that want a deeper treatment of storage-side controls and key handling, NHIMG’s Encryption Guide is the most direct reference for the broader encryption model around backups.
Which control point matters most when designing backup protection
The right control point depends on what you are trying to protect against. If the concern is media theft, lost disks, or object storage exposure, at-rest encryption is the core control. If the concern is network interception, replication paths, or backup sync traffic, in-transit encryption is the core control. If the concern is privileged insider visibility, clone leakage, or application-side exposure, in-app encryption is the more discriminating control.
In practice, backup security is strongest when these controls are aligned with the same key ownership model. A backup that is encrypted at rest but decrypted by many services, or encrypted in app but synced over weak channels, still leaves avoidable exposure. The question is not which encryption mode sounds stronger in isolation, but which layer removes the plaintext from the weakest trust boundary in your backup flow.
Backup operations also benefit from a clear policy on when plaintext is permitted to exist at all. That includes restore testing, helpdesk recovery, analytics copies, and troubleshooting exports, because those are the moments when encryption design is most likely to be bypassed for convenience.
For teams making procurement or architecture choices, NHIMG’s Encryption Buyer's Guide helps compare encryption choices, while the Encryption Policy Template is useful when you need to define which data state gets which control.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and OWASP ASVS set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | SC-28 — Protection of Information at Rest | Directly addresses protecting stored backup data on disk or object storage. |
| SC-8 — Transmission Confidentiality and Integrity | Directly addresses protecting backup data while it moves between systems. | |
| SC-13 — Cryptographic Protection | Supports the broader cryptographic design needed when applications protect data before exposure. | |
| Recommendation — Apply SC-28 to encrypt backup data stored at rest and protect the media or object store. Apply SC-8 to encrypt backup transfer and replication paths in transit. Use SC-13 to enforce cryptographic protection for backup data wherever plaintext exposure must be minimized. | ||
| OWASP ASVS | V11 — Cryptography | Applies to choosing where encryption is enforced within application flows and data handling. |
| V12 — Secure Communication | Applies to securing the transfer channel used for backup movement and sync. | |
| Recommendation — Use V11 to verify that sensitive backup data is encrypted at the appropriate application boundary. Use V12 to require protected channels for backup transport and replication. | ||
Practitioner Guidance
What to verify: Confirm whether the backup is encrypted only when stored, only while moving, or before the application can expose it. That distinction determines whether the real control boundary is storage, network, or application logic.
Decision rule: If you cannot tolerate plaintext appearing in clone, restore, or operator workflows, treat in-app encryption as the preferred design and do not rely on at-rest encryption alone.
What practitioners underestimate: The restore path is often where the protection model breaks down. A backup can be perfectly encrypted and still become broadly readable once keys, privileges, or application context are restored too early.
Practitioner takeaway: Use the encryption layer that matches the exposure you are actually trying to eliminate, then validate the restore and clone workflow as carefully as the backup job itself.
Related resources from NHI Mgmt Group
- What is the difference between encryption at rest and encryption in transit?
- What is the difference between end-to-end encryption and Salesforce-style at-rest and in-transit encryption for file sharing?
- How should security teams implement encryption across data at rest and data in transit?
- What is the difference between encryption at rest and encryption in transit under NYDFS Part 500?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org