Serverless Security 101: Everything you need to know
summary
Explains why cloud platforms handle OS patching, DDoS resistance and immutable runtimes but leave application risks to developers, and introduces the CLAD: code, libraries, access, data model with concrete examples: vulnerable npm dependencies, overly broad IAM that only grows, and session state moved to external stores. Recommends automation and DevSecOps, using tools like Snyk to scan both repo and deployed functions against a vulnerability DB and to enforce least-privilege policies.
AI-written summary · about
chapters (7)
- 0:00Intro
- 2:02What is Serverless
- 4:15Cloud Security
- 7:18Security Concerns
- 13:20Access and Data
- 16:20Final Thoughts
- 18:55Questions
related talks
57mServerless Security: Attack and Defense
24mServerless security: how to protect what you don't see?
30mServerless Security Top 10
33mServerless Security: New Risks Require New Approaches
29mPragmatic Security Automation and DevSecOps in the Cloud
18mA First Look at the Security of Serverless Applications
25mDeep Dive: Serverless Security (STAG Presentation)
34mCloud Native Security 101: Building Blocks, Patterns and Best Practices