Secure your Firebase app from the start
summary
A simple game called Furdle suffers name collisions, deleted scores, and impossible high scores written directly to the backend; the session shows concrete fixes: Firebase Authentication maps scores to unique user IDs, Firebase Security Rules restrict creates/updates/deletes, validate fields, and use reusable functions plus a 30‑day test mode, and Firebase App Check uses reCAPTCHA/Play Integrity/App Attest to block unauthorized clients. Setup steps, enforcement timing, and monitoring metrics are shown so the cheats are prevented.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:52Firebase Authentication
- 2:32Setting Up Firebase Authentication
- 3:04Firebase Ui Auth
- 3:21Firebase Authentication Sdk
- 5:51Security Rules
- 6:17Permissions and Conditions
- 6:43Validate User Data
- 7:06Functions
- 8:52Firebase App Check
- 9:40Configure Appcheck
- 11:32Summary
related talks
25mFive tips to secure your app
45mFirebase and Android, a real-time match synced in heaven
40mThree New Ways to Secure Your App with Firebase Authentication
21mServerless security modeling in Firebase
24mFirebase for Games
41m[REDACTED]: How to keep your app's secrets, secret
39mWhat's new in Firebase (Opening Keynote)
37mBuilding simple and secure account systems on Android