Translucent Databases
by Peter Wayner · first published 2002
31mentions
8recommended by
13HN commenters
2008–2024first – last mentioned
62% recommend31% neutral8% critical
Why HN recommends it
Covers protecting database contents from an attacker who already has full access, using field-level encryption and hashing to keep data useful while scrambled. It is a classic for developers' bookshelves.
Summarised by Claude from recommending comments
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
…can always use self-signed certs. If you want to go deeper down the rabbit hole check out SRP: http://srp.stanford.edu/ In terms of dealing more securely with data on your server, check out the book, Translucent Databases ( http://www.amazon.com/Translucent-Databases-Peter-Wayner/dp/... )
on “Ask YC: Best Practices for User Authentication” ↗Many of the techniques can be done at application level. A great example of this that most of us already use in the database is the hashed password. Wayner's translucent databases book is one of those classic DB works that should be on every dev's bookshelf. I'm not affiliated with Peter Wayner at all but I've added a separate story to get the word out about his work: http://news.ycombinator.com/item?id=3373947…
on “CryptDB - Encrypted MySQL” ↗I think it was on here that someone recommended this - http://www.wayner.org/node/46 > Translucent databases provide better, deeper protection by scrambling the data with encryption algorithms. The solutions use the minimal amount of encryption to ensure that the database is still functional. In the best applications,…
on “Ask HN: Protecting database information?” ↗Many years ago I bought and read "Translucent Databases" by Peter Wayner. I liked it very much and I would like a refresher - there is a 2nd edition but it came out in 2010 (and costs 75$ on Amazon). Is this still relevant? Are there newer books on the same…
on “Ask HN: “Translucent Databases” – still worth it?” ↗Valid concern. Translucent Databases covers this. http://wayner.org/node/46 http://a.co/97iqrM5 TL;DR: Various clever ways to encrypt records, organized for fast & easy retrieval, uncoverable if the key is lost (or deleted). Also: We…
on “GDPR: sorting the fact from the fiction” ↗The database or file system is likely (hopefully) encrypted. I'm referring to record and field level encryption. Like this: Translucent Databases http://a.co/d/5855TYO http://wayner.org/node/46 Think of how password databases don't actually store passwords. Instead they (should) be storing salted and hashed passwords. --- Please see my other…
on “Equifax IT staff had to rerun hackers' queries to work out what was nicked” ↗…I've slogged thru the maths and algos, I'm always left befuddled. I'm just not clever enough to figure out all the attack vectors. (I'd make a terrible criminal.) -- re: Privacy by Design That means Translucent Databases. Where all data at rest is encrypted. Just like you salt and hash password files. This book details clever applications of that strategy to real world problems: https://www.amazon.com/Translucent-Databases-Peter-Wayner/dp...…
on “Privacy by Design Foundation” ↗All PII must be encrypted at all times. At the field level. Translucent Databases explains how. https://www.amazon.com/Translucent-Databases-Peter-Wayner/dp... http://wayner.org/node/46 Source: Was once an insider. Created and ran electronic medical record exchanges.
on “Leaked Document Says Google Fired Dozens of Employees for Data Misuse” ↗…source identity. BUT: This is entirely moot if original (now fuzzed) data set can be correlated with another data set. 2) All PII should be encrypted at rest, at the field level. I really wish Wayner's Translucent Databases was more well known. TLDR: Wayner shows clever ways of using salt+hash to protect identity. Just like how properly protected password files should be salt+hash protected. Again, entirely moot if protected…
on “Big data may not know your name, but it knows everything else” ↗…at rest (in storage) as well as in-transit is the way to go. All PII must be encrypted at rest at the field level. Just like how passwords are properly stored. This is not rocket science. The book Translucent Databases demonstrates this technique for common use cases. Highest recommendation. https://www.amazon.com/Translucent-Databases-Peter-Wayner/dp...
on “BlackCat ransomware group implodes after apparent payment by Change Healthcare” ↗…rest at the field level is an important missing piece from the future perfect privacy stack. Just like how proper password vaults work. Salt, hash, encrypt. Never store the actual password. The book Translucent Databases details clever examples of this strategy for misc use cases. Never store PII as plaintext. Translucent databases and differential privacy are orthogonal. I have no ideas on how to productize (or SaaS-atize)…
on “Launch HN: Sarus (YC W22) – Work on sensitive data with differential privacy” ↗Exactly. Just like a password wallet. Store the hash of passwords, not the actual passwords. Then disallow password resets. Then you effectively "forget" your account if you lose your password. The book Translucent Databases (2nd ed) [2009] explains clever strategies for applying this technique to protect sensitive data. It's brilliant. https://www.wayner.org/node/39 https://www.amazon.com/gp/product/1441421343 Meta: I…
on “Immutable Databases” ↗…checks and version/configuration control). http://www.amazon.com/Cryptography-Database-Defense-Symantec... Another book that may help with keeping the data away from hackers (and rogue employees) is Translucent Databases. I have the 1st edition, and the 2nd just came out last month: http://www.amazon.com/Translucent-Databases-2nd-authenticati... In support of #1, check out NIST's 800 series of standards. When we were…
on “Ask HN: rules for storing banking info?” ↗There's a book series "Translucent Databases" with a lot of interesting use cases, where the assumption is that an adversary has gained access to the entire database. I've only read the first edition, and it's some years ago, but I'd recommend…
on “Ask HN: Securely store sensitive data in the DB?” ↗Agree on importance of correlating records across heterogenous systems. AND: All PII field level data must be encrypted at rest. UUIDs unlock both the record linking and privacy achievements. The book Translucent Databases shows how. Hide sensitive data with salt + hash, just like with proper password files. Use UUIDs as opaque pointers for linking.
on “Personal Information of More Than 1.5B Facebook Users Sold on Hacker Forum” ↗