Two Steps Forward for SaaS Adoption, One Step Back for Security
summary
Industry spends six times more on SaaS than on cloud and companies often discover 1,241 SaaS apps after a discovery scan, producing surprising telemetry like 900,000 shared files (about 70 shares per employee, 99% untouched after 90 days). Attack vectors include info‑stealers harvesting OAuth tokens, a CircleCI/OBS malware incident, and Drizly’s long‑lived Github credential that leads to a CEO sanction for 20 years. SSPM tools use APIs for configuration and governance but don’t read file contents or operate inline like CASBs.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:05SaaS rise and importance
- 3:56SaaS vs cloud defined
- 7:30SaaS adoption vs security
- 9:40What SSPM does
- 12:57SaaS discovery approaches
- 16:53What SSPM does not cover
- 21:54Two steps forward for SaaS
- 24:59Why vendors deprioritize security
- 27:27Shadow IT in departments
- 29:10SaaS attacks and breaches
- 35:12Data oversharing risks
- 36:38Logs in SaaS security
- 38:27Governance in SSPM
- 40:15The future of SaaS Security Posture Management
- 41:19Need SSPM now?
- 44:41Adjacent security tools
- 45:03Q&A
related talks
46mHow to Adapt to Security Changes in Cloud SaaS Transformation
39mCan Saas Ever Be Secure?
46mCritical SaaS, Critical Blind Spots: A Detection Engineer's Field Guide to SaaS Attacks
47mPain in the Apps — Three Attack Scenarios Attackers Are Using to PWN SaaS
29mMapping the SaaS Attack Surface
50mThe Application Security State of the Union
01h 02mThe New Realities of SaaS: Why Building is Harder Than Ever
45mAnticipate and Defend Against Advanced Adversaries Targeting SaaS and IaaS