Serverless security modeling in Firebase
summary
Shopping app uses Cloud Firestore, Firebase Authentication (including Anonymous Auth), and Cloud Functions; default security rules are permissive for Storage and must be locked or narrowed, and Anonymous Auth requires rule awareness. Test rules and functions locally with the Firebase Emulator Suite and use unit tests and CI. API keys are public identifiers, use the Admin SDK for trusted server actions, set function concurrency/timeouts, monitor via Cloud Logging, scan deps with Snyk, batch triggers with Pub/Sub, and consider GCIP for MFA.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:39Open source SDKs
- 3:35DOS protection
- 6:39API key management
- 8:11Security Rules
- 12:23Firebase Authentication
- 14:54Anonymous Authentication
- 16:12Limiting Team Access
- 17:27Open source dependencies
- 18:58Function Safety
- 20:34Wrap up
related talks
25mFive tips to secure your app
51mServerless with Firebase in the wild
14mYour guide to server side authentication with Firebase
55mServerless Applications with Firebase
58mEasy, scalable serverless backend for mobile/web app
01mCloud Storage Security Rules update from Firebase Summit #Shorts
36mWhat you can build with Cloud Functions
26mHow to go serverless in a post-GDPR world
