Menu

HIPAA compliance evidence for the database layer on Supabase: RLS, functions, triggers and audit logs
📰

HIPAA compliance evidence for the database layer on Supabase: RLS, functions, triggers and audit logs

DEV Community: postgres·Munaf Khatri·18 days ago
#eI2XT7PM
#devtopostgresql#devto#dev#supabase#hipaa
Reading 0:00
15s threshold

Supabase signs a BAA and has a High Compliance setting for projects that store PHI, which handles the platform. The database layer built on it is a separate matter. RLS policies, functions, triggers and audit tables are written by the project team, and a HIPAA review expects evidence that they protect PHI. Supabase’s shared responsibility model puts them on the customer’s side.

What Supabase covers

Encryption at rest and in transit, the BAA, and project settings. The HIPAA guide asks for these to be on:

Point in Time Recovery

SSL enforcement

network restrictions

connection logging

MFA on every account with access

The Security Advisor warns when any of them is off, and the linter flags patterns like a table in public with RLS off. Neither one runs the policies.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.