Autentikasi dan sesi for Supabase
high5 checks
Authentication is the highest-value target on any site: credential stuffing, session fixation and CSRF all aim at the same door.
What Supabase must have
- Login forms post over HTTPS with a CSRF token
- Rate limiting and lockout on failed attempts
- MFA available for privileged accounts
- Passwords screened against known breach corpora
- No account enumeration through error messages
How to fix it
- 1Add per-account and per-IP throttling
- 2Enforce MFA for admins and screen passwords with a k-anonymity API
Supabase context
Postgres backend platform with auth, storage and auto-generated REST APIs.
Row Level Security is mandatory — a leaked anon key plus missing RLS exposes the whole database.