this post was submitted on 24 Jul 2024
40 points (95.5% liked)

Cybersecurity

5626 readers
102 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Community Rules

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] kid@sh.itjust.works 5 points 3 months ago (2 children)
[–] sugar_in_your_tea@sh.itjust.works 6 points 3 months ago (1 children)

Local developer testing

Hmm, didn't think of that one...

staggered deployment strategy

Also a novel idea...

It's like they're catching up to best practices from 10 years ago, good job team!

[–] mosiacmango@lemm.ee 3 points 3 months ago

Listening to literally any sysadmin would have had these practices already in play.

I wonder if any are in the building, of if it's all devs and "platform engineers."

[–] PlutoniumAcid@lemmy.world 1 points 3 months ago

Systems in scope include Windows hosts running sensor version 7.11 and above that were online between Friday, July 19, 2024 04:09 UTC and Friday, July 19, 2024 05:27 UTC and received the update.

Definitely incorrect. My machine was powered off by physical switch at that time. It was powered off at 17:00 the day before and powered up at 08:00 CEST / 06:00 UTC and promptly bluescreened.