this post was submitted on 19 Feb 2024
256 points (97.4% liked)

Cybersecurity

5392 readers
28 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
 

For the first time in the history of Microsoft, a cyberattack has left hundreds of executive accounts compromised and caused a major user data leak as Microsoft Azure was attacked.

According to Proofpoint, the hackers use the malicious techniques that were discovered in November 2023. It includes credential theft through phishing methods and cloud account takeover (CTO) which helped the hackers gain access to both Microsoft365 applications as well as OfficeHome.

you are viewing a single comment's thread
view the rest of the comments
[–] virtueisdead@lemmy.dbzer0.com 13 points 6 months ago (4 children)

every day i lose my mind a little more at how much trust hundreds of thousands of companies across the world place in third parties like microsoft to handle literally all of their sensitive data, as if that could be a good idea in any universe

[–] filcuk@lemmy.zip 13 points 6 months ago (1 children)

While I don't disagree it's dangerous, most companies handling their own data would likely do a lot worse, just with smaller chance of being targeted.

[–] virtueisdead@lemmy.dbzer0.com 2 points 1 month ago

That's a fair point to be honest but it would mean more job openings for me, so... /j

load more comments (2 replies)