Security
Controls you can inspect before rollout
Authentication through Clerk, Pam Pod isolation through Supabase RLS, hashed API keys, webhook signatures, and audit events. See also the Security Policy and security documentation.
Authentication
Clerk provides user and organization authentication. Signed-in routes require a valid session. Organization membership determines Pam Pod access.
Tenant isolation
Every tenant table enforces pod_id through Supabase row-level security. API keys are scoped to one Pam Pod. Cross-Pam Pod queries are denied at the database layer.
API keys and secrets
API keys use the pam_ prefix, are hashed at rest, and display only once at creation. Webhook subscriptions verify HMAC signatures. Connector credentials are encrypted per Pam Pod.
Audit and logging
Security-sensitive actions append to an audit log. Mail, agent, and API events record lifecycle metadata for operator review. Logs exclude raw secrets.
AI and automation controls
Pam AI and Pam Agent operate under customer-configured approval gates and sending policy. Automated sends require explicit policy allowance.
Reporting vulnerabilities
Email cs@pamphlet.io with vulnerability details. Include affected routes, reproduction steps, and suggested severity. Pamphlet coordinates fixes before public disclosure when appropriate.