3 ms·
Has this actually happened? Implementing zero downtime transparent encryption on any moderately complex codebase above the database layer sounds like a big eng
by londons_explore 7y ago
Has this actually happened?
Implementing zero downtime transparent encryption on any moderately complex codebase above the database layer sounds like a big engineering challenge. Even moreso if you're trying to do it without the sysadmin noticing. Even moreso if there is no persistence for the encryption key so every user request ends up having to fire a request to the attackers server - that'll kill performance. I doubt many attackers would attempt it.
- ipython 7y agoIf I’ve learned anything in decades of working in infosec, it’s to never underestimate the ingenuity of a determined attacker. Read through any modern multi stage remote exploit. The amount of engineering required to pull these stunts off - reliably no less - is truly staggering, and yet attackers continue to innovate and develop new techniques and even more complex exploits. And you overestimate the competency of the defenders: sysadmin? What small business has a dedicated sysadmin? It’s not like we are talking about running a global hosted chat service like slack here. (Oh wait...) BTW Persistence for the key in memory is trivial: create a shared memory segment and store the key there, with a ttl.