Data spends its life in two main states: sitting still on a disk, in a database, or in cloud storage, and moving across networks between devices, apps, and servers. Each state faces different threats. A stolen laptop or leaked backup exposes stored data. A compromised Wi-Fi network or intercepted API call exposes data on the move. Understanding encryption at rest vs in transit makes it clear why protecting one state is never enough, and why regulators and auditors ask about both.
I have designed and reviewed encryption setups for laptops, cloud storage, databases, and web applications, and this guide explains the difference in practical terms. It is written for IT managers, developers, compliance teams, and business owners who want to know what each type protects, how it works, which tools deliver it, what the regulations require, and how the third state, data in use, fits in.
Quick Answer
Encryption at rest protects stored data, such as files on a laptop, database records, backups, and cloud storage, so it is unreadable if the storage is stolen or accessed without authorisation. Examples include BitLocker, FileVault, database transparent data encryption, and cloud storage encryption.
Encryption in transit protects data while it moves between systems, such as web traffic, email, and API calls, so it cannot be read or altered if intercepted. Examples include TLS (HTTPS), VPNs, and SSH. You need both, plus strong key management and access controls.
The Three States of Data
Security professionals describe data in three states, each needing its own protection:
| State | Description | Example | Main Protection |
|---|---|---|---|
| Data at rest | Stored and not actively moving | Files on a disk, database tables, backups | Encryption at rest |
| Data in transit | Moving across a network | Web requests, email, file uploads, API calls | Encryption in transit (TLS, VPN) |
| Data in use | Being processed in memory | A spreadsheet open in RAM, a database query running | Access control, confidential computing |
What Is Encryption at Rest?
Encryption at rest is the encryption of data while it is stored on any medium: laptop and phone drives, servers, databases, USB drives, backup tapes, and cloud object storage. Its goal is to make stored data unreadable to anyone who gains physical or low-level access without the key.
How Encryption at Rest Works
Encryption at rest typically uses symmetric encryption, most often AES-256, because it is fast enough to encrypt and decrypt large volumes of data transparently. When an authorised user or application reads data, it is decrypted automatically; when data is written, it is encrypted before being saved.
Types of Encryption at Rest
- Full-disk encryption: encrypts entire drives, such as BitLocker on Windows, FileVault on macOS, LUKS on Linux, and the built-in encryption on iPhone and Android devices.
- File and folder encryption: encrypts specific files or containers, using tools such as VeraCrypt, 7-Zip, or Windows EFS.
- Database encryption: transparent data encryption (TDE) in SQL Server, Oracle, and cloud databases encrypts database files, while column-level or field-level encryption protects specific sensitive values.
- Cloud storage encryption: Amazon S3 has encrypted all new objects by default since January 2023, and Azure Storage and Google Cloud Storage also encrypt stored data by default.
- Application-level encryption: the application encrypts data before storing it, so even database administrators cannot read the raw values.
What Encryption at Rest Protects Against
Encryption at rest protects against lost or stolen devices, stolen backup media, improperly disposed drives, unauthorised access to storage infrastructure, and some cloud storage exposures. It does not protect against attackers who log in with valid credentials, because the system decrypts data for authenticated users.
What Is Encryption in Transit?
Encryption in transit, also called encryption in motion, protects data as it travels between devices, applications, and networks, whether across the public internet or inside a private network. Its goal is to prevent eavesdropping and tampering during transmission.
How Encryption in Transit Works
Encryption in transit usually relies on hybrid encryption. Protocols such as TLS use asymmetric cryptography to authenticate the server with a certificate and securely agree on a session key, then use fast symmetric encryption such as AES-GCM or ChaCha20-Poly1305 for the data. TLS also provides integrity checks, so any tampering is detected.
Common Encryption in Transit Protocols
| Protocol | Protects | Best For |
|---|---|---|
| TLS 1.3 / 1.2 (HTTPS) | Web traffic, APIs, app connections | Websites, SaaS, mobile apps |
| SSH | Remote administration and file transfer (SFTP) | Server management |
| IPsec and WireGuard | Whole network connections | VPNs and site-to-site links |
| SMTP with STARTTLS and MTA-STS | Email between mail servers | Email delivery |
| WPA2 / WPA3 | Wireless connections to access points | Wi-Fi networks |
| Mutual TLS (mTLS) | Service-to-service traffic with two-way authentication | Microservices and zero trust |
What Encryption in Transit Protects Against
Encryption in transit protects against eavesdropping on public Wi-Fi, man-in-the-middle attacks, interception on compromised network equipment, and tampering with data during transfer. Our guide to man-in-the-middle attacks explains how attackers try to get between users and services, and why TLS and certificate validation matter.
Encryption at Rest vs in Transit: Key Differences
| Factor | Encryption at Rest | Encryption in Transit |
|---|---|---|
| Protects | Stored data | Data moving across networks |
| Main threats | Stolen devices, leaked backups, storage breaches | Eavesdropping, interception, tampering |
| Typical algorithms | AES-256 (symmetric) | Hybrid: ECDHE and certificates plus AES-GCM or ChaCha20 |
| Common tools | BitLocker, FileVault, TDE, cloud KMS | TLS/HTTPS, VPNs, SSH |
| Key lifespan | Long-lived keys, rotated periodically | Short-lived session keys per connection |
| Visibility to users | Usually invisible | Visible as HTTPS padlock or VPN status |
| Main weakness | Decrypted for anyone who authenticates | Data is decrypted at each endpoint |
| Best For | Protecting data where it is stored | Protecting data as it moves |
Why You Need Both
Encryption at rest and in transit protect different moments in the same data’s journey, so each covers a gap the other leaves. Consider a customer submitting a payment form: TLS protects the card number as it travels from their browser to your server, and database encryption or tokenization protects it once stored. Remove either layer and the data is exposed at that stage.
Regulations reflect this. PCI DSS 4.0 requires strong cryptography for card data both when stored and when transmitted over open, public networks. The HIPAA Security Rule treats encryption of electronic protected health information as an addressable safeguard both at rest and in transmission. GDPR Article 32 names encryption as an appropriate measure, and India’s DPDP Rules list encryption among reasonable security safeguards.
What About Data in Use?
Data in use is the hardest state to protect, because data is normally decrypted in memory while being processed. Malware on an endpoint, a compromised administrator account, or a malicious insider can access data at this stage even when at-rest and in-transit encryption are perfect.
Protections include strong access control and multi-factor authentication, endpoint detection and response (EDR), data masking in applications, and confidential computing. Confidential computing uses hardware-based trusted execution environments, such as Intel TDX, AMD SEV-SNP, and Arm CCA, to keep data encrypted in memory; confidential virtual machines are now available from major cloud providers. Homomorphic encryption, which allows computation on encrypted data, is an emerging option for specialised uses.
Encryption at Rest and in Transit Best Practices
- Enable full-disk encryption on every laptop, desktop, and mobile device, and store recovery keys securely.
- Encrypt databases, backups, and cloud storage, using customer-managed keys for highly sensitive data.
- Require TLS 1.2 or 1.3 everywhere, disable older SSL and TLS versions, and enable HTTP Strict Transport Security (HSTS) on websites.
- Encrypt internal traffic too, not just internet-facing connections, following zero trust principles.
- Manage keys separately from data using AWS KMS, Azure Key Vault, Google Cloud KMS, or hardware security modules.
- Rotate keys and certificates and automate certificate renewal to avoid outages.
- Encrypt backups and protect backup keys with separate access controls.
- Combine encryption with MFA and least privilege to cover the data-in-use gap.
Encryption at Rest and in Transit in Major Cloud Platforms
Most major cloud and SaaS platforms provide both types by default, with options for stronger control:
| Platform | At Rest (Default) | In Transit (Default) | Extra Control Options |
|---|---|---|---|
| Microsoft 365 | BitLocker and service encryption on Microsoft servers | TLS for client and service connections | Customer Key, Purview sensitivity labels, Double Key Encryption |
| Google Workspace | AES-256 encryption of stored data | TLS for connections | Client-side encryption on eligible plans |
| AWS S3 | SSE-S3 encryption for all new objects since 2023 | TLS for API and console access | SSE-KMS with customer-managed keys, bucket policies requiring TLS |
| Azure Storage | Storage Service Encryption with AES-256 | TLS, with minimum TLS version settings | Customer-managed keys in Key Vault |
How to Check Whether Your Data Is Encrypted
- Laptops: on Windows, check Settings for Device encryption or the BitLocker control panel; on a Mac, check FileVault in Privacy & Security.
- Websites: look for HTTPS and use a free scanner such as Qualys SSL Labs to confirm TLS 1.2 or 1.3 and strong ciphers.
- Cloud storage: review encryption settings and key types in your AWS, Azure, or Google Cloud console.
- Databases: confirm transparent data encryption or equivalent is enabled and that connections require TLS.
- Backups: verify backup jobs encrypt data and that keys are stored separately.
- Email: check that your mail provider enforces TLS and consider MTA-STS to prevent downgrade attacks.
Common Encryption Mistakes
- Storing keys next to the data, such as in the same server, bucket, or configuration file.
- Allowing old protocols such as TLS 1.0 and 1.1 for compatibility.
- Forgetting backups and exports, which often sit unencrypted in file shares.
- Ignoring certificate expiry, causing outages or pressure to disable encryption temporarily.
- Assuming encryption replaces access control, when it only works alongside strong authentication.
What Auditors Ask About Encryption at Rest and in Transit
If you are preparing for an ISO/IEC 27001, SOC 2, PCI DSS, or HIPAA audit, expect questions like these:
- Which systems store sensitive data, and how is that data encrypted at rest?
- Which encryption algorithms and key lengths are used, and are any deprecated?
- Who manages encryption keys, where are they stored, and how often are they rotated?
- Are all external connections protected with TLS 1.2 or higher, and is internal traffic encrypted?
- Are backups and removable media encrypted?
- How do you detect and respond to expired certificates or weak cipher configurations?
Keeping a simple encryption register, listing each system, its encryption method, key owner, and rotation schedule, makes these questions quick to answer and highlights gaps before an auditor finds them.
Does HTTPS Mean Data Is Encrypted at Rest?
No. HTTPS only protects data while it travels between your browser and the website’s server. Once the data arrives, how it is stored depends entirely on the organisation’s own systems. A website can show a perfect padlock and still store your details in an unencrypted database. When assessing a vendor, ask separately about encryption in transit, encryption at rest, and who controls the keys, and look for evidence such as SOC 2 reports or ISO/IEC 27001 certification rather than relying on the padlock alone.
Frequently Asked Questions
What is the difference between encryption at rest and in transit?
Encryption at rest protects stored data, such as files, databases, and backups, while encryption in transit protects data moving across networks, such as web traffic and email. At rest guards against stolen or exposed storage; in transit guards against interception and tampering.
Is encryption at rest necessary if data is encrypted in transit?
Yes. Encryption in transit only protects data while it moves. Once stored, data needs encryption at rest to stay protected if a device is stolen, a backup is leaked, or storage is accessed without authorisation.
What is an example of encryption in transit?
HTTPS is the most common example of encryption in transit. It uses TLS to encrypt data between your browser and a website. VPNs, SSH, and encrypted email connections are other examples.
What is an example of encryption at rest?
BitLocker on Windows and FileVault on macOS are common examples of encryption at rest, encrypting entire drives. Database transparent data encryption and default encryption in AWS S3, Azure Storage, and Google Cloud Storage are other examples.
What is data in use encryption?
Data in use encryption protects data while it is being processed in memory. It is achieved mainly through confidential computing, which uses hardware-based trusted execution environments, and emerging techniques such as homomorphic encryption.
Conclusion: Encryption at Rest vs in Transit
Encryption at rest and in transit are complementary layers, not alternatives. To recap:
- At rest: protects stored data with tools such as BitLocker, FileVault, database TDE, and cloud storage encryption.
- In transit: protects moving data with TLS, VPNs, SSH, and mTLS.
- In use: the remaining gap, addressed by access control, EDR, and confidential computing.
- Compliance: PCI DSS, HIPAA, GDPR, and India’s DPDP Rules all expect encryption of sensitive data.
- Key to success: strong key management and identity controls alongside encryption.
Pro Tip
Map one sensitive data flow end to end, for example a customer signing up on your website, and mark every point where the data is stored or transmitted. Any point without encryption, including internal hops and backups, is your next fix.


