Say one has to export database data to use in another tool, such as an Excel Spreadsheet or for use as a csv file with some other program.
There's a problem with this, and that's that it ends up in an unencrypted form on the disk, where it can be forgotten about, snatched up by phishing, etc.
So when storing / using / getting rid of this sort of data, is there some sort of OS level solution (LUKS) for working with then getting rid of these sorts of temporary files?
I know when one uses SSH-agent the keys can be given a time limit to be stored in memory, before it's deleted, is it possible to do the same thing with an encrypted directory or encrypted volume, that can be "scrubbed" automatically, after a certain period of time?
Also, it would be crazy to do something like upload such a csv file stored encrypted on the disk to a web application that runs over HTTP and thus leave such things moving over a network encrypted when it moves across the network, that would destroy the point of encrypting it, even if it was encrypted on disk.
And also what about allowing an approved running process to access the information but not allowing it to be copied elsewhere? That sort of thing sounds in the domain of permissions / ACLs to me.
Is it best to have a designated machine for doing this and limiting it's access to the outside world using a separate subnet / firewall / proxy or some combination there of?