perplexity-security-basics
Apply Perplexity security best practices for secrets and access control.Use when securing API keys, implementing least privilege access,or auditing Perplexity security configuration.Trigger with phrases like "perplexity security", "perplexity secrets","secure perplexity", "perplexity API key security".
When & Why to Use This Skill
This Claude skill provides a comprehensive framework for implementing Perplexity security best practices. It guides users through securing API keys, managing environment variables, implementing secret rotation, and enforcing least privilege access to protect sensitive AI integration credentials and maintain system integrity.
Use Cases
- Securing Perplexity API keys and secrets using environment variables and proper .gitignore configurations to prevent accidental exposure in version control.
- Implementing automated secret rotation workflows, including generating new keys, verifying connectivity, and revoking legacy credentials to minimize breach windows.
- Applying the principle of least privilege by configuring environment-specific access scopes, ensuring development and production environments have only the necessary permissions.
- Enhancing infrastructure security through webhook signature verification and comprehensive audit logging to track API usage and detect unauthorized access.
| name | perplexity-security-basics |
|---|---|
| description | | |
| allowed-tools | Read, Write, Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Perplexity Security Basics
Overview
Security best practices for Perplexity API keys, tokens, and access control.
Prerequisites
- Perplexity SDK installed
- Understanding of environment variables
- Access to Perplexity dashboard
Instructions
Step 1: Configure Environment Variables
# .env (NEVER commit to git)
PERPLEXITY_API_KEY=sk_live_***
PERPLEXITY_SECRET=***
# .gitignore
.env
.env.local
.env.*.local
Step 2: Implement Secret Rotation
# 1. Generate new key in Perplexity dashboard
# 2. Update environment variable
export PERPLEXITY_API_KEY="new_key_here"
# 3. Verify new key works
curl -H "Authorization: Bearer ${PERPLEXITY_API_KEY}" \
https://api.perplexity.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 PerplexityClient({
apiKey: process.env.PERPLEXITY_READ_KEY,
}),
writer: new PerplexityClient({
apiKey: process.env.PERPLEXITY_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 Perplexity analytics
await perplexityClient.track('audit', log);
// Also log locally for compliance
console.log('[AUDIT]', JSON.stringify(log));
}
// Usage
await auditLog({
action: 'perplexity.api.call',
userId: currentUser.id,
resource: '/v1/resource',
result: 'success',
});
Resources
Next Steps
For production deployment, see perplexity-prod-checklist.