Where should I be encrypting my data
summary
Explains when to use one-way hashing versus two-way encryption, recommends AES-256 for strong encryption and modern hashing (SHA3), warns that encrypted columns cannot be indexed and that encryption bloats column size; shows TDE as a quick compliance checkbox that encrypts storage and backups and makes tempdb encrypted, and that a client saw dedup drop from ~70% to ~10% after encrypting tables. Covers Always Encrypted (SQL Server 2019) and secure enclaves to avoid app rewrites, certificate backup/restore needs, IPsec/SSL (TLS) for wire encryption, and key rotation costs.
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
48mProtecting the confidentiality and integrity of your high value data with Azure SQL and SQL Server 2
47mData at Rest Encryption Going Beyond the Basics to Address Modern Attacks
32mDesigning secure Azure SQL Database solutions
40mUnderstanding the cryptographic controls in Azure SQL Database
41mKeeping Secrets: Emerging Practice in Database Encryption
43mConfidential development with Always Encrypted using enclaves