26
CISA Issues Emergency Directive After Midnight Blizzard Microsoft Hits
(www.darkreading.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Apr 2024
26 points (96.4% liked)
Cybersecurity
5687 readers
22 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
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
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
Yeah, this story isn't over yet. It has all the hallmarks of drip feeding bad news.
What's unclear is the source of those credentials emails. Are they from employees at Microsoft sending credentials to clients, or is it automatically generated password reset emails that were exfiltrated?
They've apparently known about this since early January, but it appears that the infiltration has been ongoing since November. It's still happening today.
That's nearly SIX MONTHS of access to internal Microsoft systems.
Just spit balling, but here's a question that nobody is asking:
How do you know when they're no longer in your system?
Here's another:
How do you know that nothing extra was left behind?
Or this one:
Why should anyone ever trust Microsoft ever again?
Or:
What guarantees can Microsoft ever make from here on out?
For your last two questions, the counterpoint is, if even Microsoft can’t stop a dedicated nation state, how can any other major service provider say they haven’t been compromised?
The standard now is, assume breach. While unfortunate, the industry average for MTTD is in months. Microsoft was at least good enough to detect it within six.
Can Broadcom or Palo Alto say the same? Amazon, Google, Apple, Cisco?
It's why I think it's a shame the zero-trust is kinda a buzzword. this is exactly the type of situation where an actual zero trust architecture would be extremely useful.
I think that zero trust is not enough.
I think that you need to assume that you are going to be compromised and put processes and procedures in place before that happens to ensure business continuity.
im approaching zero trust as assume everything is compromised until you verify it is not
Maybe cyber resilience? Quick identify, respond and recover from an incident.