Technical requirementsUnderstanding PostgREST’s OpenAPI Schema exposurePreventing schema exposureRemoving schemas from usage via APISpecifically exposing a schema to the APIBeing careful with current_user usage and understanding auth.role()Generating new Anonymous Keys, Service Role Keys, and database passwordsBenefiting from Supabase VaultCreating secrets in the Vault and reading themUsing the secret in the business logic/within your applicationUtilizing silent resets to avoid data manipulationEnabling column-level security/working with rolesUnderstanding security on views and manually created tablesChanging the max_rows configurationUnderstanding safe-guarded API updates or deletionAdding middleware inside Postgres for each API requestAdding middleware for PostgRESTUsing the Security AdvisorAllowing a listing of IPs for database connectionsEnforcing SSL on direct database connectionsSummary