this post was submitted on 07 Jun 2024
200 points (96.7% liked)

Asklemmy

43896 readers
985 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago
MODERATORS
200
deleted (sh.itjust.works)
submitted 5 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]
 

deleted

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 20 points 5 months ago (1 children)

I don't have advice, just a worthless anecdote.

I work at a large tech company. We had a Windows XP system on our network get hacked. They used that to jump to our servers. IT had to quarantine off the whole lab, because they didn't know where the hacker had hopped next. So then IT had to do a post-mortem and figure out how they got in and what was affected. That process took 3 months. In the meantime, any team with servers in that lab couldn't use them. The team directly responsible for this couldn't work at all for the full 3 months.

[โ€“] [email protected] 6 points 5 months ago* (last edited 5 months ago)

We lost 2 months of local Windows servers in a smash and grab ransomware. we were lucky that our PROD servers were Linux. And this was a place with an active Windows 10 upgrade plan, gateways and air gapping for non-compliant systems. Our luck/planning was the backups system allow for two months of roll back to remove the malware. For the sysadmins, the character limit on the file paths meant we lost a bit of deep dive information 8/10 folders deep. (Over 64 characters or something like that.)