Cybersecurity

7556 readers

165 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 !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

kid@sh.itjust.works

Lanky_Pomegranate530@midwest.social

Google Cloud incident report (status.cloud.google.com)

submitted 17 hours ago by kid@sh.itjust.works to c/cybersecurity@sh.itjust.works

2 comments fedilink hide all child comments

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

[–] kid@sh.itjust.works 3 points 17 hours ago

The incident occurred on June 12, 2025, due to a policy change that contained blank fields, causing 503 errors in Google Cloud and Google Workspace APIs. The root cause was:

A new feature added to Service Control on May 29, 2025, without adequate error handling.
The policy change with blank fields was globally replicated and caused Service Control binaries to crash.