Where should I be encrypting my data
summary
Compares one-way hashing versus two-way encryption, recommends SHA3 for hashes and AES-256 for data, warns salted encryption breaks indexing and increases storage and dedupe (reported dedupe drop from ~70% to ~10%), measures CPU cost tradeoffs (TDE adds ~0.1–0.5% CPU; heavy encryption can force large CPU increases), demonstrates options: Always Encrypted (worked in a client without app changes), database-side encryption, TDE, backup encryption, IPSec/SSL for wire encryption, and explains key-rotation complexity requiring re-encryption.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:25Encryption vs Hashing
- 10:49Salted Hashes
- 18:05Application Layer
- 21:08Database Layer
- 26:57Backup Encryption
- 32:09Data on the Wire
- 40:29Always Protect Your Keys
- 45:11Colossal Data Security Failures
related talks
51mWhere should I be encrypting my data
48mGetting To Know SQL Server Encryption Capabilities
30mSecuring the Connected World - Detangling Encryption and Decryption
47mData at Rest Encryption Going Beyond the Basics to Address Modern Attacks
32mEncryption - A Deeper Review
41mKeeping Secrets: Emerging Practice in Database Encryption
59mDatabase Encryption in a GDPR World
51mDon’t Throw Away the Key: What Developers Should Know about Encryption