this post was submitted on 17 Jul 2025
120 points (97.6% liked)
Cybersecurity
7839 readers
99 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 !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub
Notable mention to !cybersecuritymemes@lemmy.world
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is light on one detail: who was running the compromised infrastructure?
Because the US military doesn't do its own IT anymore. It's all outsourced to Microsoft and other cloud providers to the tune of tens of billions of dollars. And here, the report conveniently doesn't mention who let the hackers in.
I'd like to know which sloppy cloud contractor is responsible.
It's a hell of a lot wider than one specific sloppy contractor. They basically compromised everybody (Verizon, AT&T, T-Mobile, Spectrum, Lumen, Consolidated Communications, Windstream, the system for CALEA requests, routers made by Cisco, phones belonging to Trump and Vance... basically, everything.) Viasat is on that list, but they're no more particularly sloppy than any other contractor in that space. Basically it would have been truly remarkable if some Guard agency had managed to hire a cloud contractor that was able to resist it.