home / skills / jeremylongshore / claude-code-plugins-plus-skills / posthog-security-basics
/plugins/saas-packs/posthog-pack/skills/posthog-security-basics
This skill helps you secure PostHog API keys and enforce least privilege with rotation, audit logs, and environment-based access.
npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill posthog-security-basicsReview the files below or copy the command above to add this skill to your agents.
---
name: posthog-security-basics
description: |
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".
allowed-tools: Read, Write, Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---
# 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
```bash
# .env (NEVER commit to git)
POSTHOG_API_KEY=sk_live_***
POSTHOG_SECRET=***
# .gitignore
.env
.env.local
.env.*.local
```
### Step 2: Implement Secret Rotation
```bash
# 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
```typescript
const clients = {
reader: new PostHogClient({
apiKey: process.env.POSTHOG_READ_KEY,
}),
writer: new PostHogClient({
apiKey: process.env.POSTHOG_WRITE_KEY,
}),
};
```
### Webhook Signature Verification
```typescript
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
- [ ] `.env` files in `.gitignore`
- [ ] Different keys for dev/staging/prod
- [ ] Minimal scopes per environment
- [ ] Webhook signatures validated
- [ ] Audit logging enabled
### Audit Logging
```typescript
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
- [PostHog Security Guide](https://docs.posthog.com/security)
- [PostHog API Scopes](https://docs.posthog.com/scopes)
## Next Steps
For production deployment, see `posthog-prod-checklist`.This skill applies PostHog security best practices for managing API keys, secrets, and access control across environments. It helps you store keys safely, implement rotation, enforce least-privilege scopes, and add audit logging for security visibility. Use it to reduce blast radius from exposed credentials and to harden webhook and service-account patterns.
The skill inspects and enforces patterns: environment variable usage for secrets, .gitignore hygiene, scoped API keys per environment, automated rotation steps, and webhook signature verification. It provides concrete code examples for service accounts and audit logging, and outlines detection and mitigation steps for common security issues like exposed keys or excessive scopes.
How often should I rotate PostHog API keys?
Rotate keys on a schedule that fits your risk profile—every 90 days is common—or immediately if a key is exposed.
What scopes should production keys have?
Production keys should have only the scopes required for the application. Remove write or admin scopes unless explicitly needed; follow least-privilege principles.