aegis-baas-platform

Scope & Objectives

This module audits the managed platforms where modern products actually run. It is configuration-first: the platform vendor secures its infrastructure; the application owner secures everything configured on top of it, and on every platform below there is a default whose failure mode equals full-database compromise.

Shared-responsibility baseline. The vendor patches Postgres, scales Firestore, signs TLS, and operates the control plane. You own, without exception:

• Row Level Security (RLS) enablement and policy quality on every table.
• Security rules files (Firestore / Realtime Database / Storage).
• Network access lists and credential hygiene on connection-string databases.
• Which environment variables reach the browser and who can open preview deployments.
• Whether fulfillment logic verifies provider signatures before granting anything.
• CMS core/plugin/theme lifecycle and hardening constants.

In scope: Supabase; Firebase (Firestore, Realtime Database, Storage); connection-string-only platforms (Neon, Supabase-Postgres direct connections, Railway, Render, Upstash, MongoDB Atlas); serverless hosts (Vercel, Netlify and similar); Stripe-shaped payment webhooks; WordPress-class managed CMS.

Out of scope: cloud IAM deep dives (see the IAM module), TLS/certificate posture, DNS takeover (dedicated module), mobile-specific storage.

Objectives — produce a finding only when you can name the artifact: