Timeline for Detecting/preventing rollback of encrypted data on a server
Current License: CC BY-SA 4.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 15, 2020 at 23:12 | history | edited | kelalaka | CC BY-SA 4.0 |
polish
|
Jan 15, 2020 at 22:57 | comment | added | kelalaka | @JosephSible-ReinstateMonica One design the Merkel tree over all rows of the table not individually for one row! The general research about this; the DB is deployed into the cloud and application servers are on the site. One can also use HSM on the application server to store the Merkle root hash. Then we can talk about what if the attackers played with equality. Anyway, if there is a complicated attack that you fear, then stop using the internet! The Op asked for detecting the DB changes, so this is a solution. | |
Jan 15, 2020 at 22:51 | comment | added | Joseph Sible-Reinstate Monica | But a Merkle root is the same size as the result of an HMAC. | |
Jan 15, 2020 at 22:49 | comment | added | kelalaka | @JosephSible-ReinstateMonica do you ever know about the Merkle Tree? It only stores one value hash! | |
Jan 15, 2020 at 22:49 | comment | added | Joseph Sible-Reinstate Monica | If the application servers can store state more securely than the database, then why even have a database? And in that case, again, why do you need a Merkle tree? | |
Jan 15, 2020 at 22:48 | comment | added | kelalaka | @JosephSible-ReinstateMonica Storing the value on the application servers. If the database has been changed then it can be detected. If you are talking about the complex attack that the attackers attacked both the application servers and the database server than you may need a third party to store the value for you, too. | |
Jan 15, 2020 at 22:45 | comment | added | Joseph Sible-Reinstate Monica | This doesn't seem to address the problem at hand. What's stopping the attacker from rolling the Merkle tree back too exactly? | |
Jan 15, 2020 at 21:40 | history | answered | kelalaka | CC BY-SA 4.0 |