home / skills / jeremylongshore / claude-code-plugins-plus-skills / perplexity-security-basics

This skill helps you secure Perplexity API keys and enforce least-privilege access with rotation, auditing, and environment-specific controls.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill perplexity-security-basics

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.5 KB
---
name: perplexity-security-basics
description: |
  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".
allowed-tools: Read, Write, Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# 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
```bash
# .env (NEVER commit to git)
PERPLEXITY_API_KEY=sk_live_***
PERPLEXITY_SECRET=***

# .gitignore
.env
.env.local
.env.*.local
```

### Step 2: Implement Secret Rotation
```bash
# 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
```typescript
const clients = {
  reader: new PerplexityClient({
    apiKey: process.env.PERPLEXITY_READ_KEY,
  }),
  writer: new PerplexityClient({
    apiKey: process.env.PERPLEXITY_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 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
- [Perplexity Security Guide](https://docs.perplexity.com/security)
- [Perplexity API Scopes](https://docs.perplexity.com/scopes)

## Next Steps
For production deployment, see `perplexity-prod-checklist`.

Overview

This skill teaches Perplexity security best practices for protecting API keys, secrets, and access control. It provides concrete steps for safe storage, rotation, least-privilege configuration, webhook verification, and audit logging. Use it to reduce blast radius and meet basic compliance goals.

How this skill works

The skill inspects common risk areas and prescribes practical mitigations: environment-based key management, scheduled rotation, scoped credentials, and audit trails. It includes patterns for service accounts, webhook signature verification, and error handling guidelines to detect and remediate exposed keys or excessive permissions.

When to use it

  • Securing Perplexity API keys before deployment
  • Implementing least-privilege access across dev/staging/prod
  • Auditing Perplexity-related access and usage
  • Responding to a suspected key leak or credential exposure
  • Designing webhook integrations that require signature verification

Best practices

  • Never commit keys to source control; keep .env files in .gitignore
  • Store secrets in environment variables or a managed secrets store
  • Use separate keys per environment and per service account
  • Grant the minimum scopes required for each environment or service
  • Rotate keys on a regular schedule and immediately after exposure
  • Enable and persist audit logs for API calls and administrative actions

Example use cases

  • CI pipeline uses a Perplexity read-only key for test data retrieval in staging
  • Production service uses a scoped write key limited to required endpoints
  • Automated rotation script updates env var, verifies health endpoint, then revokes old key
  • Webhook endpoint validates incoming signatures with a timing-safe HMAC check
  • Audit pipeline aggregates Perplexity events to local and remote logs for compliance

FAQ

How often should I rotate Perplexity API keys?

Rotate keys on a regular cadence based on risk level—commonly every 30–90 days—and immediately after any suspected exposure.

What is the minimum scope to grant to production services?

Grant only the exact scopes required for the service to function; avoid broad read:* or write:* scopes unless absolutely necessary.