Initial SaaS Security Challenges
Prior to implementing Valence’s SaaS Security Platform in 2021, Riskified struggled with limited, fragmented visibility into their SaaS applications. Like many organizations, Riskified has distributed administration of SaaS applications across various business units, and each unit had previously managed its own critical tools without centralized oversight. This decentralization placed a greater burden on the security team, limiting their visibility into application configurations and usage while making it harder to proactively mitigate risks such as misconfigurations, excessive privileges, identity-related risks (both human and non-human), and data exposure.
Identity security was a significant challenge, as local accounts in certain SaaS applications weren’t linked to the company’s identity provider—potentially bypassing single sign-on (SSO) and remaining unmanaged by the security team. Over time, as users left the company or changed roles, their accounts and access credentials could remain active, creating a need for more robust lifecycle management processes. Fragmented offboarding led to excessive access, and the manual deprovisioning process across a vast SaaS environment was both time-consuming to manage and prone to errors.
Additionally, the rapid growth of SaaS-to-SaaS integrations made monitoring increasingly difficult. With business teams directly connecting applications, tracking and managing OAuth permissions across platforms like Google Workspace and GitHub became a challenge. Riskified wanted to future-proof its SaaS security strategy with a unified security approach that could identify and remediate risks across the organization, and continue to scale with the evolving risk landscape and internal decentralization.