3 ms·
I get the point you are trying to make, but usually the holding is on the servers. Most mail and communications servers allow for this.. (ie, don't actually de
by briffle 4y ago
I get the point you are trying to make, but usually the holding is on the servers. Most mail and communications servers allow for this.. (ie, don't actually delete any emails that mention the company ACME because of a legal hold number 123434).
And I (A sysadmin) have literally been tasked with overnighting employee laptops to foresnic groups, and issuing them a brand new one. (typically, they just image the drives, and send them back, we would wipe the system, and put it back in our 'spare pool'.)
- kridsdale1 4y agoBefore I quit Meta, we were actually told we had to do this. We could not delete files from SOURCE CODE anymore.
- 1letterunixname 4y agoWhich role / pillar organization?
- 1letterunixname 4y agoUnfortunately, your experience differs in ways that don't apply categorically to the points I made from my perspective and experience. We have hooks into the fleet of endpoints (corporate with some 10k BYODs), servers, and various vendor apps. This is realized by data legal provides reduced to a boolean per user because there's no need to convey excess detail. When an employee visits Help Desk, they are limited by the possible actions HD can take if they are under a legal hold. The same applies to certain OS upgrades, whether HD or DIY. It would be impossible to manage VDI or "throwaway" servers at scale without a centralized legal hold inquiry API. Google has (or had) a far greater corporate tech staff / employee ratio in the industry than similar companies, so there's no excuse for them not to have a comprehensive legal hold program throughout their technical organization.
- gopher_space 4y agoWere you with your company when they became large enough to worry about legal holds? If so, was there a conversation about the transition you were privy to?