A former Twitter employee, Gary Rooney, won about $600,000 for unfair dismissal after Twitter assumed he resigned by not responding to Elon Musk’s “hardcore” work email.
The case highlighted the importance of clear communication between employers and employees, especially regarding significant changes in employment terms.
Rooney’s private Slack messages, where he discussed leaving, were used as evidence by Twitter, underscoring that internal communication on platforms like Slack is not always private and can be used in legal disputes.
That’s common sense, frankly.
But people don’t understand it.
Hell, no email sent or received is yours and likely can never be truly deleted off your company’s exchsnge. Same with files etc.
It’s not common knowledge, let’s not pretend it is and educate people.
True that. I have to tell employees regularly to not send any chat or email they don’t want read in court. That usually gets the point across.
I hope I get to read mine someday, I really wanna say
Most companies have a strict policy to delete everything off of exchange after a few months unless there is a reason to keep it longer. You can’t bring up in court anything that wan daleted before you looked.
I don’t think that’s true. We archive all email within the company as soon as it arrives. This is done to prevent an employee from deleting any evidence for many reasons that they may have. We are also on litigation hold which requires all data to be saved and since we can’t trust everyone to do this we are required to back up everything until we are told not to. We have used restored data many times for legal cases in the past.
No he’s actually right, it’s a SOX thing. Not all companies do it but big ones with good legal departments generally do. Especially if they’re into shady s***.
The concept rules like this: we delete all emails over 90 days old. If someone subpoena’s emails over 90 days old we simply say they don’t exist we delete emails over 90 days old and show them the policy. From there it gets a little more dicey if people cram stuff into local stores.
From a corporate standpoint there’s a strong advantage to deleting all of your old emails and not keeping backups over 90 days especially for anything that might be legally questionable.
That said with the advent of SAAS, there’s a hell of a lot of data out there that doesn’t ever go away even if you do your best to make it happen.
Where I work there is a data retention policy, and emails and other forms of communication (internal emails and slack, but even customer calls, etc) are deleted after a set amount of time, which varies depending on the rationale for storing that data.
There’s many reasons to do this - limit disclosure issues in case of litigation, reduce storage costs, comply with PII rules around the world, etc. The guys in Legal have us file these loong ass forms about all this, including where the data is kept, security measures, etc etc etc.
I’m shocked this isn’t common practice everywhere.
There are two main types of data retention policy:
It’s a little more nuanced than that, of course, but in broad strokes that’s how I’ve seen it play out. Does the company want to pin the blame on somebody or shrug and say “we have no idea how that can have happened, guess we need to forget about it.”
I think that’s an understandable position but IT is ruled in a cost benefit analysis for many small to medium sized businesses, so I am sure if it’s as common practice there
I’ve contracted for companies with email policies that nuke anything older than 30 days.
I typically learn it the hard way when I go back to look for an email I need and…it has been deleted.
When I worked as a US FedGov contractor, I was greeted with a long warning banner every time I logged into my computer. The tl;dr version of it is “fuck your privacy”. Being that I was part of cybersecurity for the site I was working at, I was one of the people doing the fucking. While we didn’t read everything from everyone all the time, we were logging it and could pull it up, if we were performing an investigation. We also had some automated stuff scanning for patterns and keywords on a regular basis, which could trigger an investigation.
While I’m no longer in the FedGov space (thank the gods), I still assume that everything I do on my work system or with work accounts is being logged. Also, I’m still working in cybersecurity and am often still the one doing the privacy fucking. Yes, everything is being logged. We may not look at it today, we may not look at it tomorrow. But, when HR and Legal ask us about a user’s activity, we can usually be pretty detailed. Act accordingly.
My company is better than most I’ve worked for. They tell you, upfront, anything on their equipment can be monitored for any reason with no warning.
But then, as part of the HR and acceptable use policy, no one will monitor your activities without just cause and investigation. Meaning in practice, “We’re not going to look over your shoulder while you watch YouTube videos but if we notice you’re watching a lot of or you start visiting porn sites, we’re going to start monitoring you.”
Now all that said, I still assume that my company knows every key I type on their laptop.
I would assume they have some basic stuff running 24x7. I can’t imagine a network which doesn’t have Endpoint Detection and Response (EDR) running 24x7 these days. There’s also things like firewall logs, which are almost certainly being captured (or at least netflow). Stuff like screen recording and mouse monitoring is probably saved for extreme cases. That said, my own experience has been pretty close to:
Quite frankly, no one’s got time for that shit. I work at an organization with a bit north of 25,000 employees, and we have less than a dozen security analysts. While I could run a search against our firewall logs and see evidence of folks dicking around. I have much better things to do, like running down abnormal processes and writing up reports on users who got their systems infected while dicking around. And that’s really the way it comes to our attention, most of the time. Someone is out trying to download movies or software on their work laptop (you’d think people would know better…) and they pickup malware. We get an alert and start investigating. While trying to determine the source, we pull browser history and see the user out on “SketchyMovieSite[.]xyz”. And then their dicking around becomes our problem, mostly because the site had a malicious redirect, which is where the infection came from.
So ya, they may not be looking, but I’d always bet they are recording. Logging isn’t useful if it isn’t recording at the time of the compromise.
Mines the same way. It’s actually kind of difficult to get approval to monitor someone. Has to be approved by two VPs.
What made you leave gov space?
Remote work and pay. I was already interested in getting a remote gig when COVID hit. We went to a hybrid schedule and I realized that I really liked working from home. Also that my job was pretty much built for it. While many of the folks I used to work with are still hybrid, fully remote was never an option. I worked with Classified systems and I could never convince them to put a SIPR drop in my home. I guess you need to get elected President for that.
As the world was opening back up, many companies saw remote work as a carrot to offer cybersecurity folks and I started to see a lot more job postings with it as an option. So, I put my LinkedIn profile to “looking for work” and started getting recruiters messaging me on a regular basis. One hit me up with “REMOTE WORK OPPORTUNITY” (yes, all in caps) as the lead for an offer. What followed that sounded interesting and I started talking with him. A few week later, I put in my notice and started working in the private sector. Got a pay bump in the move as well.
My time in the FedGov space was overall a positive thing. I learned a lot and got to see systems locked down in a way that actually mattered (I never thought I would miss STIGs). At the same time, I don’t see myself ever going back. The bureaucratic nature of everything is soul crushing. And sitting in an OSS all day long sucks. It especially sucks when you’re the only one in the container and need to go out and take a piss. Clear the room, arm the alarm, spin the lock, sign the sheet, go piss. Open the lock, sign the sheet, disarm the alarm, get back to wishing for the sweet, sweet embrace of death.
OMG the OSS at my first job was like that, but they wouldn’t give contractors the lock code. So after I was waiting 30 min to go pee I spun the lock, went pee, came back and waited an hour outside the door. We both got a talking to, him by his command and me by my company. I snapped back and pay, hours, and lack of trust and that if they tried to gig me for this I was walking out and not coming back. That was back in 2012 and I have changed jobs multiple times. I like the team and what I do, openshift and kuberneties is awesome to get teams to update their code. But as you said,no remote, except for development.
It’s not OP, but when I left it was because the money and resources were better.
Federal purchasing is fairly rigged you don’t end up with decent hardware to do anything. Projects are constantly as complicated and strenuously pushed as possible. Everything has an angle there are too many people with essentially tenure. Don’t get me wrong, I liked a lot of the people that I worked with and around, but leaving Federal work for Enterprise was really refreshing.
Thanks, I have been looking and I see pay is better for outside government for the work I do.