Cybersecurity

5687 readers

45 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

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

Notable mention to [email protected]

founded 1 year ago

MODERATORS

[email protected]

CISA Issues Emergency Directive After Midnight Blizzard Microsoft Hits (www.darkreading.com)

submitted 7 months ago by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

CISA has issued an emergency directive in response to Midnight Blizzard, or Cozy Bear, a Russian threat actor targeting Microsoft email accounts. The group is extracting information to access Microsoft customer systems. Strict security measures, including strong passwords and multi-factor authentication, are strongly recommended by CISA for all organizations (Microsoft included).

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 14 points 7 months ago (5 children)

Yeah, this story isn't over yet. It has all the hallmarks of drip feeding bad news.

First it was a legacy system.
Then it was internal Microsoft corporate email.
Then it was source code repositories.
Then it was emails between Microsoft and Government agencies
Now it's password credentials sent by Microsoft to those same agencies.

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?

[–] [email protected] 11 points 7 months ago (1 children)

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?

[–] [email protected] 5 points 7 months ago (2 children)

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.

[–] [email protected] 2 points 7 months ago (1 children)

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.

[–] [email protected] 6 points 7 months ago

im approaching zero trust as assume everything is compromised until you verify it is not

[–] [email protected] 1 points 7 months ago

Maybe cyber resilience? Quick identify, respond and recover from an incident.

load more comments (3 replies)