Loading...
Loading...
MANDATORY when touching auth tables, tenant isolation, RLS policies, or multi-tenant database code - enforces Row Level Security best practices and catches common bypass vulnerabilities
npx skill4agent add troykelly/claude-skills postgres-rls| Pattern | Examples |
|---|---|
| migrations/001_add_tenant_id.sql |
| migrations/005_enable_rls.sql |
| migrations/010_create_policies.sql |
| db/policies.sql |
| src/auth/context.ts |
| lib/tenant.ts, services/tenantService.ts |
| docs/multi-tenant-architecture.md |
git diff --name-only HEAD~1 | grep -iE '(tenant|rls|policy|auth.*sql|multi.?tenant)'BYPASSRLS-- DANGEROUS: Testing as superuser shows RLS "working" when it's bypassed
SET ROLE postgres;
SELECT * FROM orders; -- Returns ALL rows, RLS ignored
-- CORRECT: Test as application role
SET ROLE app_user;
SELECT * FROM orders; -- Returns only permitted rowsBYPASSRLSFORCE ROW LEVEL SECURITY-- INCOMPLETE: Owners bypass this
ALTER TABLE orders ENABLE ROW LEVEL SECURITY;
-- COMPLETE: Everyone including owners must obey policies
ALTER TABLE orders ENABLE ROW LEVEL SECURITY;
ALTER TABLE orders FORCE ROW LEVEL SECURITY;-- DANGEROUS: View owned by superuser bypasses RLS
CREATE VIEW all_orders AS SELECT * FROM orders;
-- SAFE (PostgreSQL 15+): Security invoker respects caller's RLS
CREATE VIEW user_orders
WITH (security_invoker = true)
AS SELECT * FROM orders;security_invoker = trueUSINGWITH CHECKWITH CHECK-- INCOMPLETE: User can INSERT rows they can't SELECT
CREATE POLICY tenant_isolation ON orders
USING (tenant_id = current_setting('app.tenant_id')::uuid);
-- COMPLETE: Both read and write protected
CREATE POLICY tenant_isolation ON orders
USING (tenant_id = current_setting('app.tenant_id')::uuid)
WITH CHECK (tenant_id = current_setting('app.tenant_id')::uuid);-- DANGEROUS: Context persists across pooled connections
SET app.tenant_id = 'tenant-123';
-- SAFE: Use SET LOCAL inside transaction (auto-resets)
BEGIN;
SET LOCAL app.tenant_id = 'tenant-123';
-- ... queries ...
COMMIT; -- Context automatically cleared// DANGEROUS: Leaks between requests
await db.query(`SET app.tenant_id = '${tenantId}'`);
// SAFE: Transaction-scoped context
await db.transaction(async (trx) => {
await trx.raw(`SET LOCAL app.tenant_id = ?`, [tenantId]);
// ... queries ...
});SET LOCALSET-- DANGEROUS: If current_tenant() uses user input unsafely
CREATE POLICY tenant_isolation ON orders
USING (tenant_id = current_tenant());
-- The function itself must be injection-safe:
CREATE OR REPLACE FUNCTION current_tenant()
RETURNS uuid AS $$
BEGIN
-- SAFE: Casts to UUID, not string concatenation
RETURN current_setting('app.tenant_id')::uuid;
END;
$$ LANGUAGE plpgsql STABLE;-- DANGEROUS: Contains ALL tenants' data
CREATE MATERIALIZED VIEW order_stats AS
SELECT tenant_id, count(*) FROM orders GROUP BY tenant_id;
-- Background jobs with superuser access can export all data-- Without index: Sequential scan on every query
CREATE POLICY tenant_isolation ON orders
USING (tenant_id = current_setting('app.tenant_id')::uuid);
-- Add index for policy column
CREATE INDEX idx_orders_tenant_id ON orders(tenant_id);-- SLOW: Function called per row
CREATE POLICY access_check ON documents
USING (user_has_access(auth.uid(), id));
-- FASTER: Evaluated once, cached
CREATE POLICY access_check ON documents
USING ((SELECT auth.uid()) = owner_id);-- SLOW: RLS on permissions table also evaluated
CREATE POLICY access_check ON documents
USING (id IN (SELECT document_id FROM permissions WHERE user_id = auth.uid()));
-- FASTER: Bypass RLS chain with SECURITY DEFINER
CREATE OR REPLACE FUNCTION user_document_ids(uid uuid)
RETURNS SETOF uuid AS $$
SELECT document_id FROM permissions WHERE user_id = uid;
$$ LANGUAGE sql STABLE SECURITY DEFINER;
CREATE POLICY access_check ON documents
USING (id IN (SELECT * FROM user_document_ids(auth.uid())));-- SLOW: Must join to get tenant context
CREATE POLICY order_items_policy ON order_items
USING (order_id IN (
SELECT id FROM orders WHERE tenant_id = current_setting('app.tenant_id')::uuid
));
-- FAST: Direct column check
ALTER TABLE order_items ADD COLUMN tenant_id uuid;
CREATE POLICY order_items_policy ON order_items
USING (tenant_id = current_setting('app.tenant_id')::uuid);-- Step 1: Add column (if needed)
ALTER TABLE orders ADD COLUMN IF NOT EXISTS tenant_id uuid;
-- Step 2: Backfill data (batched for large tables)
UPDATE orders SET tenant_id = (
SELECT tenant_id FROM customers WHERE customers.id = orders.customer_id
) WHERE tenant_id IS NULL;
-- Step 3: Add NOT NULL constraint
ALTER TABLE orders ALTER COLUMN tenant_id SET NOT NULL;
-- Step 4: Create index
CREATE INDEX CONCURRENTLY idx_orders_tenant_id ON orders(tenant_id);
-- Step 5: Enable RLS (both statements!)
ALTER TABLE orders ENABLE ROW LEVEL SECURITY;
ALTER TABLE orders FORCE ROW LEVEL SECURITY;
-- Step 6: Create policies
CREATE POLICY tenant_isolation ON orders
FOR ALL
USING (tenant_id = current_setting('app.tenant_id')::uuid)
WITH CHECK (tenant_id = current_setting('app.tenant_id')::uuid);
-- Step 7: Grant appropriate permissions
GRANT SELECT, INSERT, UPDATE, DELETE ON orders TO app_role;describe('RLS Policies', () => {
it('tenant A cannot see tenant B data', async () => {
// Insert as tenant A
await setTenantContext('tenant-a');
await db('orders').insert({ id: 1, tenant_id: 'tenant-a', amount: 100 });
// Switch to tenant B
await setTenantContext('tenant-b');
// Should not see tenant A's data
const orders = await db('orders').select();
expect(orders).toHaveLength(0);
});
it('cannot insert data for other tenant', async () => {
await setTenantContext('tenant-a');
await expect(
db('orders').insert({ tenant_id: 'tenant-b', amount: 100 })
).rejects.toThrow(/violates row-level security/);
});
it('superuser role is not used in application', async () => {
const result = await db.raw('SELECT current_user');
expect(result.rows[0].current_user).not.toBe('postgres');
});
});# Create test role
CREATE ROLE test_app_user;
GRANT app_role TO test_app_user;
# Run tests as this role
psql -U test_app_user -d testdb -f tests/rls_tests.sql<!-- RLS_IMPLEMENTATION:START -->
## Row Level Security Implementation
### Tables with RLS Enabled
| Table | ENABLE | FORCE | Policies | Index |
|-------|--------|-------|----------|-------|
| orders | ✅ | ✅ | tenant_isolation | idx_orders_tenant_id |
| order_items | ✅ | ✅ | tenant_isolation | idx_order_items_tenant_id |
| customers | ✅ | ✅ | tenant_isolation | idx_customers_tenant_id |
### Policy Details
| Table | Policy | USING | WITH CHECK |
|-------|--------|-------|------------|
| orders | tenant_isolation | tenant_id = current_tenant() | tenant_id = current_tenant() |
### Security Verification
- [ ] Application connects as non-superuser role
- [ ] All RLS tables have FORCE ROW LEVEL SECURITY
- [ ] All policies have WITH CHECK clause
- [ ] Context uses SET LOCAL (transaction-scoped)
- [ ] Views use security_invoker = true
- [ ] Policy columns are indexed
- [ ] Cross-tenant tests written and passing
### Application Role
- Role name: `app_service`
- BYPASSRLS: `false`
- Superuser: `false`
**Verified At:** [timestamp]
<!-- RLS_IMPLEMENTATION:END -->security-reviewdatabase-architecturelocal-service-testing