Thousands of Organizations Are Exposing Sensitive Data Via Google Groups Lists, Researchers Find (krebsonsecurity.com)
Brian Krebs reports: Google is reminding organizations to review how much of their Google Groups mailing lists should be public and indexed by Google.com. The notice was prompted in part by a review that KrebsOnSecurity undertook with several researchers who've been busy cataloging thousands of companies that are using public Google Groups lists to manage customer support and in some cases sensitive internal communications. Google Groups is a service from Google that provides discussion groups for people sharing common interests. Because of the organic way Google Groups tend to grow as more people are added to projects -- and perhaps given the ability to create public accounts on otherwise private groups -- a number of organizations with household names are leaking sensitive data in their message lists. Many Google Groups leak emails that should probably not be public but are nevertheless searchable on Google, including personal information such as passwords and financial data, and in many cases comprehensive lists of company employee names, addresses and emails. Google has outlined instructions on how to secure the discussion boards.
No, it is not the USENET of old. So get ready to bail out, before too many secrets get leaked.
No thanks, Castro fag.
And I really do hate what google did to deja news. What a bunch of utter tossers.
"Google has outlined instructions on how to secure the discussion boards" from google...
Go to the cloud!
It's more secure and safer than your own server!
Google experts know more about security than anyone you could afford to hire!!!
CLOUD! CLOUD! CLOUD!
CLLOOOOOOOUUUUUUUUUDDDD!
Fucking idiots.
Every other email service provider offers a way to create alias accounts that forward to specific mailboxes suck as invoices, info, billing, etc. G-Suite doesn't offer this basic functionality. Users that want this have to create a group and it isn't exactly straight forward on how to do it.
I've made lots of Google API projects for dealing with this info, and the OAuth 2.0 token stuff was very fragile. If you don't implement every possible error condition, you'll end up in a state unable to refresh the token, and the google account that is authenticating and keeping the data private will have to log back in and create new tokens. Google seems to intentionally throw errors a ton to keep you on your toes, and they constantly change the specs. After years of development, I think I've finally got a framework that is bulletproof. Most people are just going to say fuck it and just make things private and trust no one will find the URL. Same thing with Amazon S3 buckets.
Configuring settings for groups is horrible. There are a whole bunch of settings, which do not really align with google's recommendations. And there is also no option to check if any of the groups which exist are readable from the "internet". You have to check every single group, and then 4 different sections, etc.