implicit security guarantees of most popular encrypted databases Review recent advances & breaks in database encryption techniques Look at emerging methods around data in-use & blind admin models Provide architects and defenders with practical guidance for high-sensitivity workloads
- Breaking next-gen crypto in 2018 with 9th century frequency analysis Inference attacks on property-preserving encrypted databases Wright, Naveed, Kamara - Logs, diagnostics, in-memory structures, oh my! Why your database is not secure Grubbs, Ristenpart, Shmatikov
& Amazon scaling AWS key management service (KMS): Handling cryptographic bounds for use of AES-GCM Campagna & Gueron (Amazon) Achieving high availability in the internal Google key management system Kanagala, et al (Google)
is not your game over - RAM is the achilles heel of confidentiality - Snapshot attackers will usually win, but you probably already lost - Thinking through zero knowledge
policy." — Cryptographers "We need to give all of Finance, Accounting, HR, and Helpdesk the key." — Senior Management "This web app has [select * from *] & a hard-coded HSM API token." — Production Ops
Column-Mode Transparent Data Encryption • Deterministic & randomized encryption modes • Guidelines for Using the CryptDB System Securely (Popa et al) • Outsourcing the Decryption of ABE Ciphertexts • Searchable Symmetric Encryption. Kamara & Moataz • Inference Attacks on Property-Preserving Encrypted Databases (MSR) • Adrian Colyer analysis on Grubbs et al • Searchable Symmetric Encryption Implementation: Clusion (Kamara Lab)
are weak/underspecified - Encrypted DB disks protect against eBay & Craigslist attacks, not Amazon, Microsoft, Google (and, only minimally, their customers) - You may have to think about: court orders/discovery and motivated advanced attackers - You do have to think about key surface/exposures, AppSec, SQLi, bearer tokens, API intercepts, backups, logs, sysadmins, DBAs...