posthog-security-basics
Apply PostHog security best practices for secrets and access control.Use when securing API keys, implementing least privilege access,or auditing PostHog security configuration.Trigger with phrases like "posthog security", "posthog secrets","secure posthog", "posthog API key security".
When & Why to Use This Skill
This Claude skill provides a comprehensive framework for securing PostHog implementations. It guides users through managing API keys, implementing least privilege access, rotating secrets, and setting up audit logs to protect sensitive analytics data and maintain compliance with industry security standards.
Use Cases
- Securing API keys and secrets by migrating them to environment variables and configuring .gitignore to prevent accidental exposure in version control.
- Implementing a systematic secret rotation workflow to minimize the security impact of potentially compromised credentials.
- Enforcing the principle of least privilege by defining environment-specific access scopes (read/write) for development, staging, and production environments.
- Verifying PostHog webhook signatures using HMAC SHA-256 to ensure the authenticity and integrity of incoming data payloads.
- Establishing an automated audit logging system to track sensitive API calls and user actions for security monitoring and compliance reporting.
| name | posthog-security-basics |
|---|---|
| description | | |
| allowed-tools | Read, Write, Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
PostHog Security Basics
Overview
Security best practices for PostHog API keys, tokens, and access control.
Prerequisites
- PostHog SDK installed
- Understanding of environment variables
- Access to PostHog dashboard
Instructions
Step 1: Configure Environment Variables
# .env (NEVER commit to git)
POSTHOG_API_KEY=sk_live_***
POSTHOG_SECRET=***
# .gitignore
.env
.env.local
.env.*.local
Step 2: Implement Secret Rotation
# 1. Generate new key in PostHog dashboard
# 2. Update environment variable
export POSTHOG_API_KEY="new_key_here"
# 3. Verify new key works
curl -H "Authorization: Bearer ${POSTHOG_API_KEY}" \
https://api.posthog.com/health
# 4. Revoke old key in dashboard
Step 3: Apply Least Privilege
| Environment | Recommended Scopes |
|---|---|
| Development | read:* |
| Staging | read:*, write:limited |
| Production | Only required scopes |
Output
- Secure API key storage
- Environment-specific access controls
- Audit logging enabled
Error Handling
| Security Issue | Detection | Mitigation |
|---|---|---|
| Exposed API key | Git scanning | Rotate immediately |
| Excessive scopes | Audit logs | Reduce permissions |
| Missing rotation | Key age check | Schedule rotation |
Examples
Service Account Pattern
const clients = {
reader: new PostHogClient({
apiKey: process.env.POSTHOG_READ_KEY,
}),
writer: new PostHogClient({
apiKey: process.env.POSTHOG_WRITE_KEY,
}),
};
Webhook Signature Verification
import crypto from 'crypto';
function verifyWebhookSignature(
payload: string, signature: string, secret: string
): boolean {
const expected = crypto.createHmac('sha256', secret).update(payload).digest('hex');
return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}
Security Checklist
- API keys in environment variables
-
.envfiles in.gitignore - Different keys for dev/staging/prod
- Minimal scopes per environment
- Webhook signatures validated
- Audit logging enabled
Audit Logging
interface AuditEntry {
timestamp: Date;
action: string;
userId: string;
resource: string;
result: 'success' | 'failure';
metadata?: Record<string, any>;
}
async function auditLog(entry: Omit<AuditEntry, 'timestamp'>): Promise<void> {
const log: AuditEntry = { ...entry, timestamp: new Date() };
// Log to PostHog analytics
await posthogClient.track('audit', log);
// Also log locally for compliance
console.log('[AUDIT]', JSON.stringify(log));
}
// Usage
await auditLog({
action: 'posthog.api.call',
userId: currentUser.id,
resource: '/v1/resource',
result: 'success',
});
Resources
Next Steps
For production deployment, see posthog-prod-checklist.