secure the channel.
I will protect data in transit
. I also need to protect data at rest
. Either is not sufficient.
The database files are encrypted using a key known only to the server:
Security regulations (e.g. like this
) require protection against insider threats to make sure data does not escape, e.g. when backed up. To have a (symmetric) key and the data on the same server is out of question.
I would advocate avoiding use of deterministic encryption altogether, because I do not think it will ever provide the data-security and data-integrity that you need.
I would normally agree, but in this case I feel the disadvantage of a less secure encryption model is probably outweighted by the advantages of not having the (symmetric) key and the data on the same server.
There are apparently advances in cryptography research (e.g.
here) that suggests that deterministic asymmetric encryption is becoming increasingly secure. It takes of course a long time for new algorithms to find its way into actual, usable implmentations.
This is hardly an atypical or novel requirement.
I would compare it with to store data encrypted on your server that a root user does not have access to
. I would be glad to use an of-the-shelf solution. Do such exist?
Thanks for your feedback.
No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them.