Re:Millions of accounts compromised because there is no spec...
by bagels on Tuesday April 21, 2015 @11:50PM
(#9418583)
Right, there's a few classes of data that can see that would do well to separate from the database that a website may have unfettered access to.
1) Authentication data
(login id?, password)
2) Personal data that is not used in an online manner (depends on the site of course)
(full name, email address, etc.)
3) Data that shows up on the site
If this data is segregated in to separate silos with no 'read everything' apis exposed to the web servers, you might stand a chance of not leaking all of your users data when the web servers are compromised. This of course will not help you if the authentication servers are also compromised.
1) Authentication data (login id?, password) 2) Personal data that is not used in an online manner (depends on the site of course) (full name, email address, etc.) 3) Data that shows up on the site
If this data is segregated in to separate silos with no 'read everything' apis exposed to the web servers, you might stand a chance of not leaking all of your users data when the web servers are compromised. This of course will not help you if the authentication servers are also compromised.