Symmetric vs. asymmetric encryption, AES operating modes in cloud platforms, envelope encryption as the cloud standard, encrypting data across all three states, and the post-quantum cryptographic standards NIST finalised in 2024.
Sign in to mark this article as read and track your progress.
Perimeter controls fail. Credentials get stolen. Insider threats are real. Encryption is the control that makes stolen data useless — without the key, ciphertext is computationally irretrievable. In cloud environments where you share physical infrastructure with unknown tenants, encryption is not optional.
Symmetric encryption uses the same key for encryption and decryption. It is fast and efficient, making it ideal for encrypting large volumes of data (files, database records, storage volumes).
AES (Advanced Encryption Standard) is the universal symmetric standard:
The mode determines how AES processes data blocks — and the wrong mode choice breaks security even with a perfect key.
| Mode | Full Name | Cloud Use | Security Note |
|---|---|---|---|
| ECB | Electronic Codebook | Almost never | Identical plaintext blocks produce identical ciphertext — never use for structured data |
| CBC | Cipher Block Chaining | Legacy TLS, file encryption | Requires IV; vulnerable to padding oracle attacks (POODLE) |
| CTR | Counter | High-performance streaming | Converts AES to stream cipher; IV must never repeat |
| GCM | Galois/Counter Mode | TLS 1.3, AWS, GCP default | Provides both encryption AND authentication (AEAD); strongly recommended |
AWS KMS, GCP Cloud KMS, and Azure Key Vault all use AES-256-GCM as their default encryption mode. Use it.
Asymmetric encryption uses a mathematically related key pair: a public key (encrypt/verify) and a private key (decrypt/sign).
P-256 and P-384 curves preferred. Basis for ECDH key exchange in TLS 1.3.In cloud, asymmetric encryption is used for:
Directly encrypting large datasets with KMS master keys is expensive and limited (KMS operations have rate limits and cost per call). The solution is envelope encryption:
1. Generate a unique Data Encryption Key (DEK) locally
2. Encrypt the data with the DEK (fast, local AES-GCM)
3. Encrypt (wrap) the DEK with the KMS Master Key (KMS API call)
4. Store the encrypted data alongside the encrypted DEK
5. On decryption: call KMS to unwrap the DEK, then decrypt the data locally
This pattern means the KMS master key never leaves the KMS hardware — only the wrapped DEK is transmitted. Every S3 SSE-KMS encryption, every EBS volume encryption, and every RDS encrypted snapshot uses this pattern.
| State | What It Means | Cloud Implementation |
|---|---|---|
| At Rest | Data stored on disk, object storage, databases | S3 SSE-KMS, EBS encryption, RDS encrypted storage |
| In Transit | Data moving between components | TLS 1.2+ for all API calls; VPN/Direct Connect for hybrid |
| In Use | Data being processed in memory | AWS Nitro Enclaves, Azure Confidential Computing — Trusted Execution Environments |
Data in use (in memory during processing) is the hardest to protect. Confidential computing using Trusted Execution Environments (TEEs) encrypts data even while it is being processed by the CPU.
Current asymmetric algorithms (RSA, ECC) are vulnerable to cryptographically relevant quantum computers running Shor algorithm. NIST standardised three post-quantum algorithms in 2024:
| Standard | Algorithm | Purpose |
|---|---|---|
| FIPS 203 | ML-KEM (Module-Lattice KEM) | Key encapsulation, replacing RSA/ECDH |
| FIPS 204 | ML-DSA (Module-Lattice Digital Signature) | Digital signatures, replacing RSA/ECDSA |
| FIPS 205 | SLH-DSA (Stateless Hash-Based DSA) | Hash-based signatures, alternative to FIPS 204 |
Crypto-agility — designing systems to swap cryptographic algorithms without redesigning the entire architecture — is now a mandatory design principle. Start planning your migration from RSA and ECC to post-quantum algorithms today.
Encryption protects data when every other control has failed. Use AES-256-GCM for data at rest, TLS 1.3 for data in transit, envelope encryption via KMS for key management, and start planning your post-quantum migration now — not when quantum computers arrive.