3 ms·
Not specific to the issue here: Please _never_ _ever_ put a production database on a system which is not permanently in office, preferably never on any desktop
by dathinab 3y ago
Not specific to the issue here:
Please _never_ _ever_ put a production database on a system which is not permanently in office, preferably never on any desktop system at all.
Not just unencrypted databases any production database no matter the state of encryption.
There is quite a large variety of reasons for this some security related, some liability (and similar legal reasons) related.
I know it's not very convenient, annoying and sucks. But as system administrators we have responsibilities to uphold (which is partially why I normally not work as a sysadmin, eh, also maybe just ignore me).
- andersa 3y agoWouldn't this exclude all cloud servers? Since they are not permanently in your office
- dathinab 3y agoI should have been more clear: Desktop systems at home, independent of weather they are owned by the company or a private person. EDIT: Or server system at home, or systems in a office which are not secured enough from physical access etc. etc. etc. The cloud can for most companies/use-cases generally be assumed to be a physically secure location where it's extremely unlikely that a warrant for something else also accidentally include the systems. Basically any location where the system is not either legally treated as company property and which is secur