Row-level security

Row-Level Security

• Row-Level Security in Postgres, Explained
• Writing RLS Policy Tests for Every Role and Tenant
• Connecting to Postgres as the Right Role: Pooling and RLS
• Row-Level Security Policy Patterns for Multi-Tenant Agent Access
• When RLS Slows Queries: Tenant Filter Plan Checks

Tenant isolation

Tenant Isolation

• An Isolation Test Suite for Every Agent That Acts for a User
• Fixtures That Fail: Seeding Two Tenants to Prove Isolation
• Tenant Isolation Beyond RLS: Schemas, Databases, Checks
• Testing Tenant Isolation With an Agent's Service Account

Testing for data exposure

Testing for Data Exposure

• Fixture Files for a Verification Hop
• Testing Agent Tool Permissions With Negative Cases
• Reviewing the Fixtures a Teammate Added: A Short Checklist
• Seeding a Test Database With Payloads Your Agent Sees
• Snapshot Testing for API Responses: Data Exposure
• Testing Tool Access Control: Fixtures, Mocks and Negative Cases
• The Cost of a Full Fixture Replay: Measuring What Each Test Runs
• Writing Database Fixtures That Expose Row-Level Leaks

Data minimization for AI

Data Minimization for AI

• Turning Support Ticket Edits Into a Fine-Tuning Set
• Data Minimization for AI Features: What Not to Send to the Model
• Logging Model Inputs and Outputs Without Keeping Too Much

Access reviews and auditing

Access Reviews and Auditing

• How to Run a Quarterly Access Review for a Small Team
• An Access Review Query: Who Still Holds a Scope and Why
• Contractor Accounts in the Same Directory as Staff
• Detecting Stale Service Accounts Before They Become Backdoors
• How to Review an AI Agent's Access After a Staff Change
• How to Tie Access Reviews to Your Agent's Tool-Call Logs
• Reading an Action Log to Answer 'Who Did What'
• What a Service Account's Owner Should Be Asked to Confirm
• All of Access reviews and auditing