How to do a security audit of a Firebase Studio app?

Why a Firebase Studio-specific audit (not a generic web audit)

A generic OWASP audit will tell you your Firebase Studio app "needs CSP headers." A Firebase Studio-aware audit tells you that your specific Firebase Studio app has an RPC function callable without auth or a service key in a client bundle — the issues that actually appear when Firebase Studio apps get compromised. The difference in output value is why the audit should be scoped to Firebase Studio's real failure modes.

Step 1 — Fingerprint the deployment

Confirm the Firebase Studio stack components: database (firebase, postgres), hosting, auth provider, third-party integrations. For Firebase Studio apps this is often visible in the Firebase endpoint URL in network requests. Document every component — each is an independent audit target.

Step 2 — Automated scan with Firebase Studio-aware rules

Run VAS against the deployed URL. The scan probes the specific issue classes found in Firebase Studio apps: security rules, auth config, functions audit, secrets scan. This is the 80/20 — most critical and high findings surface here. Fix anything critical before continuing to manual steps.

Step 3 — Manual Firestore Security Rules review

Open the Firebase Console → Firestore → Rules. Every match path needs explicit `allow read/write: if request.auth.uid == resource.data.userId` (or similar ownership check). Storage rules require the same. Use the Firebase Emulator to test: a `firebase emulators:exec` with a write attempt as an anonymous user must fail.

Step 4 — Authentication & authorization probing

Test every endpoint with no session (expect 401), with a valid session for a different user (expect 403 on user-owned resources), and with session tokens that have been tampered with (expect 401 if signatures are enforced). For Firebase Studio specifically, watch for weak auth configuration — firebase auth setup may skip email verification, allow disposable emails, or miss rate limiting.

Step 5 — Re-scan to verify

Fix findings in severity order (critical → high → medium → low), re-scan after each batch of fixes. "I applied the fix" is not evidence — the fix might not have been deployed, might have been partial, or might have been reverted. Only the scan output proves the gap is closed. Log each finding + fix + verification scan for compliance records.

Firebase Studio-specific checks often missed

• Overly Permissive Firebase Security Rules
• Unsecured Cloud Functions
• Firebase Storage Exposure
• Weak Auth Configuration