777
submitted 9 months ago by [email protected] to c/[email protected]
all 44 comments
sorted by: hot top controversial new old
[-] [email protected] 48 points 9 months ago

Uh no

Go to the main breaker that feed the servers whatever. And pull the 600v switch off

The smartest layout for that situation is having the main breaker box close to the hooman IT operator room

No choice if it is very serious breach

[-] [email protected] 19 points 9 months ago

Nah. Rip that shit right out of the chassis. Destroy that RJ45 port. Make it so the security audit team has to resolder a jack to the mobo before they can even ssh to the box.

Trust me I run a security company. If you need help with your security please feel free to contact me! We are the best in the business!

[-] [email protected] 2 points 9 months ago

Yea but it take time !!!

How many shit you have to unhook from whatever to save the shit ?? 100 ?? That take minutes !!!!!

[-] [email protected] 1 points 9 months ago

Y'all... just... unhook the cable from the demarc...?

[-] darcy 1 points 8 months ago

just have a tub of water rigged above the server

[-] [email protected] 11 points 9 months ago

The advice I've always heard is disconnect network but leave powered for forensics/recovery. Some ransomware store the decryption key soley in memory, so it is lost upon power loss

[-] [email protected] 2 points 9 months ago

That actually makes sense. We had a ransomware attack once. We also disconnected the device but I cant remember if we powered it off. At the time it stopped encrypting due to that since our network drives were not reachable anymore.

Is there actually a way to spread the encryption process to a server?

[-] [email protected] 1 points 9 months ago

Im not a it expert at alll. But reallly ?

[-] [email protected] 1 points 9 months ago

Best I understand the encryption key is needed to encrypt and decrypt, so if the malware isn't written well enough it may well continue to store the encryption key in memory.

There's some old malware on archive.org that just pulls the FAT off the filesystem into memory and offers a dice roll to restore it

[-] [email protected] 6 points 9 months ago

Depending on where the breaker is relative to the UPS, of course.

[-] [email protected] 6 points 9 months ago

I vaguely remember the advice actually being to leave it running but disconnect it from the internet. Although maybe hard disconnect the backups if you can.

[-] [email protected] 5 points 9 months ago

And probably the intranet, too, just to be safe.

[-] [email protected] 1 points 9 months ago

Should be a trunk line disconnect switch that kills both power and data. And if your manager is cool, then it's a guillotine switch.

[-] [email protected] 1 points 9 months ago

No, have a Safety Control Rod Axe Man. The dropping rod hits the breakers and smashes it, cutting power!

[-] [email protected] 44 points 9 months ago

Break and pull now, those are a mess

[-] [email protected] 21 points 9 months ago

Only the ones added after initial install. The originals are nice and tidy.

[-] [email protected] 15 points 9 months ago

You are not invited to look at my setup then.

These are clearly put together with care.

[-] [email protected] 7 points 9 months ago

Ok but what about the door handle

[-] [email protected] 3 points 9 months ago

No, the instructions must be followed or it won't work. /j

[-] [email protected] 1 points 9 months ago

Hahahahahaahhahaha

[-] [email protected] 27 points 9 months ago

Great idea, and realize likely a joke, but wouldn’t you just need to pull the one or two that connect out to the internet?

[-] [email protected] 33 points 9 months ago* (last edited 9 months ago)

There could, in theory, be a malicious machine on the internal network that was previously infected, which is now acting as command and control. So if you didn't know which one it was...

[-] [email protected] 34 points 9 months ago

Turn of the power, no need to rip anything

[-] [email protected] 24 points 9 months ago

Use a bomb. No need to take out the lights.

[-] [email protected] 13 points 9 months ago* (last edited 9 months ago)

Nuke it from orbit. It's the only way to be sure.

[-] [email protected] 5 points 9 months ago

It's better to throw it away into a black hole.

[-] [email protected] 10 points 9 months ago

That's generally a good idea, however, there can be reasons not to do it.

The device could be infected in a way that it won't turn on again.

You might have an isolated management network that allows you to monitor the device and traffic (naturally ripping all cables also disconnects the management network).

And whatnot. But generally I agree.

[-] [email protected] 6 points 9 months ago

You two are overlooking the most important thing. It might be fun to crazily rip out the cables then make a junior guy go trace and repatch it all. The opportunity to legitimately do that doesn't come along often.

[-] [email protected] 2 points 9 months ago

Where's your sense of drama???

[-] [email protected] 12 points 9 months ago

Given that fucking rats nest of cables, even if you needed to only pull one: good luck finding it in a hurry and good luck pulling only that one.

[-] [email protected] 1 points 9 months ago

It is either the white one or the blue one so the odds are 50/50, right? /s

[-] [email protected] 3 points 9 months ago

Well the white ones look like they were somewhat cable managed.

God have pity on that mortal souls of its a blue one.

[-] [email protected] 8 points 9 months ago

Depends. If you're at home with a single endpoint, maybe.

But in cases like the image there's a lot of internal traffic and you'd want to stop the malware spreading internally. There might not even be internet connection at all.

Most serious infections are able to work within isolated internal network. You can stop data breaches by cutting external traffic but if you have ransomware you might want to cut internal connections too.

You might be able to stop the ransomware from triggering on some devices. That of course depends on the type of ransomware and whether it's triggered based on time, external command or something else.

[-] [email protected] 0 points 9 months ago

Who cares if it's ransomware, just restore your backups

[-] [email protected] 4 points 9 months ago

I think that's rather odd comment. Naturally nobody wants ransomware. And there are good reasons.

Backups may exist, but do they work properly? Or are the backups encrypted too?

How old are the backups? They might be less than a day old. But less than a day might still mean a lot of extra work and financial loss.

There might be a lot of work restoring the backups. You might have a lot of different systems.

In one of the largest ransomware cases in history, Maersk worked for months to get systems back up and running and data up to date. The insurance payout for it was 1,4 billions. Which is at least indicative of the cost.

And Maersk had recent and working backups.

[-] [email protected] 2 points 9 months ago

Don't tell me you'd try to continue using the compromised systems if you somehow aborted the drive encryption process

[-] [email protected] 1 points 9 months ago

Likely not, but definitely depends on the situation.

And how do you know the backup is not compromised?

I think it's not as clear cut. It's always a risk assessment and depends on context.

I have to say that I'm not a security expert, just an amateur with conceptual understanding of the topic and some opinions.

[-] [email protected] 3 points 9 months ago

Wait, we were taking backups?

[-] [email protected] 18 points 9 months ago

"Cut the hard line to the mainframe!"

[-] [email protected] 10 points 9 months ago

"uh all the cables are soft, i don't see any hard lines"

[-] [email protected] 2 points 9 months ago

seen too many times. But thank you for posting it on lemmy

[-] [email protected] 1 points 4 months ago
this post was submitted on 08 Oct 2023
777 points (98.6% liked)

Programmer Humor

31331 readers
14 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 4 years ago
MODERATORS