2 ms·
"reports revealing that attackers accessed personal information of nearly 7 million people — half of the company’s user base — in an October hack." Breaking in
by WalterBright 3y ago
"reports revealing that attackers accessed personal information of nearly 7 million people — half of the company’s user base — in an October hack."
Breaking into a system should never provide access to 7 million people. The database should be divided up into multiple "cells" each with its own separate access restrictions.
It's the same idea that spy networks use to prevent one compromised spy from bringing down the whole system. Or you can think of it like watertight compartments in a battleship.
- hmottestad 3y agoWhat if you want to run a query to compare your DNA to everyone else’s to see if you have any relatives that are registered already? Wouldn’t that need access to the entire database and essentially be a point of weakness?
- WalterBright 3y agoI am no expert on such systems. But it seems to me that the comparisons should only be run within the cells. The caller only passes the one to compare it to, and the only thing that comes back from each cell is any matches. That way, only the specific cell has access to its data.
- hmottestad 3y agoYou might be interested in homomorphic encryption. It allows for mathematical operations on encrypted data. I don't know if any database actually supports it, but it should allow for things like SUM operations on a column of encrypted numbers with a result that is also encrypted.