That's actually a direction I was thinking about myself. Make myself a restful decryption webservice, Communicating by backchannel private ip to the webserver. When I need a number for monthly billing, submit it to the web service.
I also had the idea of some dummy security trigger database entries, so if somebody actually camps out on my server, using my own webservice to decrypt the database, eventually they hit one of my trigger entries, and my webserver reboots and my cell phone starts ringing.
If it's monthly billing, why not keep that computer off (plugged out if you're worried about wake-on-LAN attacks), and manually turn it on once a week/month for 10 minutes to process everything?
Comments
That's actually a direction I was thinking about myself. Make myself a restful decryption webservice, Communicating by backchannel private ip to the webserver. When I need a number for monthly billing, submit it to the web service.
I also had the idea of some dummy security trigger database entries, so if somebody actually camps out on my server, using my own webservice to decrypt the database, eventually they hit one of my trigger entries, and my webserver reboots and my cell phone starts ringing.
If it's monthly billing, why not keep that computer off (plugged out if you're worried about wake-on-LAN attacks), and manually turn it on once a week/month for 10 minutes to process everything?