Why Identity Providers Aren't Enough to Secure Identities in the Cloud - Part One

permiso.io · 1,287 words · saved by 1 readers

In this two part series, we are going to analyze the role IdPs (identity providers) have played in some high-profile breaches over the last few years and perhaps, more specifically, the last few months. We will briefly look at the history of identity providers in on-premise environments, what they aimed to ultimately solve and how they have evolved in the cloud. We’ll then look at how the centralized convenience they offer, as well as the measures that have been put in place to secure their systems have ultimately been exploited by threat actors in the last few years. In the second part, we’ll review a timeline of breaches over the course of the last two years, why identity providers aren’t enough to secure identities across multiple layers of a cloud environment. We’ll also offer a few tips on steps you can take in order to better defend against common attacks orchestrated against identity providers. In the last six months, Azure AD, Okta and JumpCloud have been at the center of breac

Jared Elder | 31 Oct 2023 BACK TO BLOGS Why Identity Providers Aren't Enough to Secure Identities in the Cloud - Part One Credits: Wilma Miranda Hear Ye, Hear Ye Subscribe to Cloud Chronicles for the latest in cloud security! In this two part series, we are going to analyze the role IdPs (identity providers) have played in some high-profile breaches over the last few years and perhaps, more specifically, the last few months. We will briefly look at the history of identity providers in on-premise environments, what they aimed to ultimately solve and how they have evolved in the cloud. We’ll the

Why Identity Providers Aren't Enough to Secure Identities in the Cloud - Part One

related reading