TB
AND
0 M
RECORDS LEAKED DUE TO MISCONFIGURATIONS IN
0
SECURITY INCIDENTS (SO FAR)
0 TB
AND
0 M
RECORDS LEAKED DUE TO MISCONFIGURATIONS IN
0
SECURITY INCIDENTS (SO FAR)

Similarly to what I have done in 2022 and 2021, I am now collecting the incidents due to cloud misconfigurations and leading to the exposure of data. Unfortunately despite the growing risks and awareness this trend does not seem to slow down.

During both 2022 and 2021, AWS S3 accounted for roughly 60% of breaches. Let’s see if it will retain its leadership in this particular chart even in 2022. So far it looks like things are not going to change…

Leaky Services (Radial)

No Data Found

Leaky Services

No Data Found

Leaky Sectors

No Data Found

Enjoy the timeline, and thanks for sharing it, and supporting my work in spreading the risk awareness across the community. Also, don’t forget to follow @paulsparrows on Twitter, or even connect on Linkedin, for the latest updates.

SUPPORT MY WORK!

POPULAR POSTS
FOLLOW ME ON TWITTER

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.