#buckete — Public Fediverse posts

More good news: #BucketE, hospital Data from South Korea, got closed. I guess the fame goes to the #CERT

Tonight it's time for an update, a rather frusrating one I have to admit:

#BucketE and #BucketG just have been reported to #AWS #security tonight

Both where reported to their corresponding CERTs, but those did not even answer.

#BucketF was reported to the australian "Office of the Australian Information Commissioner" #OAIC on the 8th of September. Today I got the answer, that they will not be able to help, as they do not know how is responsible and also do not have any possibility to find it out. The email was sent from "noreply@..." so they also do NOT want any help in this regard.

sad update Update tonight:
#BucketD, more than 6 000 000 voice recordings of #pizza orders: still online. No response from the company yet.
#BucketE, Korean dentist clinic: still online. No repsonse from the Korean #CERT
#BucketF, resumes from Australia: still online. No response from #AWS #Security.

After a little less then 24h I asked the #cert for an update on #s3 #BucketE. No response so far. I guess next step would be to involve #Amazon #Security, even though this involves long standard mails from their side explaining why they are not the problem.

Funfact: KISA Korea Internet & Security Agency, https://www.kisa.or.kr/EN/5, does not have an email id in their contact info. #BucketE

Todays most exciting buckets has the string "병원자료" in it - "patient data" in korean. The files contain: 3D images of tooths. As I do not speak Korean i send a mail to the Korean #cert: https://www.first.org/members/teams/kn-cert sadly their PGP key is not valid for the provided mailadress.
In case, the cert does not react, who could help? #followerpower #BucketE