How to Adapt to Security Changes in Cloud SaaS Transformation
summary
Claim: major SaaS clouds deliver faster patching, global DevSecOps and 24/7 threat monitoring at scale — one provider builds from source ~200 times a day and shares real‑time threat intel with peers — while audits and evidence collection run continuously. Practical requirements: collect and retain application and identity logs daily, enforce MFA for all users (99% of observed breaches involve no MFA), automate permission review and remove high‑privilege access monthly, avoid shared‑stack hosts, and treat custom front‑end code and test/staging instances as attack surfaces.
AI-written summary · about
chapters (14)
- 0:00Start
- 3:19Applications are all moving to the Cloud How to make the best decisions for Security
- 5:21The Advantages
- 7:03Speed of Technology and Attacks
- 17:05Regulations and Audits at Scale
- 19:33Best Practices: Role Ownership
- 21:20Best Practices: Monitoring
- 23:20Best Practices: Security Controls
- 26:46Best Practices: Compliance
- 28:22Best Practices: Multi-Cloud
- 30:18The Most Common Cloud Risks
- 37:57Summary Verdict
- 39:23Recommend Next Steps
- 42:09RSAConference2023
related talks
48mTwo Steps Forward for SaaS Adoption, One Step Back for Security
39mCan Saas Ever Be Secure?
50mArchitecting a secure cloud framework
01h 09mCloud Safeguarding: View from Cloud Providers
25mSecurity, Identity - Back to the Drawing Board?
58mCloud Attack Surface Management
05mWhy cloud-native enterprise security matters
51mCloudSec Hero to Zero: Self-Obsolescing Through Prolific Efficiency