Supabase security detection library
Customer-safe explanations of the security activity Defencecore monitors, what each detection means, what evidence a responder can expect, and the first steps to investigate it.
How to read this library
A Defencecore detection brings related Supabase activity into an investigation with the available context. A person still decides whether the cause is abuse, an application regression, or expected traffic.
| Detection | Area | What it covers |
|---|---|---|
| Repeated Supabase authentication failures | Authentication | How Defencecore helps identify suspicious patterns of failed Supabase sign-ins, what the alert means, and how to respond. |
| Brute-force attempts against a Supabase database | Database | How Defencecore surfaces suspicious rejected Supabase database logins, what the detection means, and how to investigate safely. |
| Supabase Row Level Security policy violations | Database | What a Supabase RLS policy violation means, how Defencecore surfaces suspicious rejected writes, and how to respond. |
What this library includes
Every page explains the security outcome, the context customers can expect, careful interpretation, and the first response. Detection engineering and implementation details remain private.