exa-security-basics
Apply Exa security best practices for secrets and access control.Use when securing API keys, implementing least privilege access,or auditing Exa security configuration.Trigger with phrases like "exa security", "exa secrets","secure exa", "exa API key security".
When & Why to Use This Skill
This Claude skill provides a comprehensive framework for securing Exa API integrations by implementing industry-standard security best practices. It helps developers and security teams manage API secrets, enforce least privilege access control, and establish robust audit logging to protect sensitive data and prevent unauthorized access.
Use Cases
- Secure Secret Management: Moving Exa API keys to environment variables and configuring .gitignore to prevent accidental exposure in version control.
- Least Privilege Implementation: Configuring environment-specific access scopes (e.g., read-only for development, restricted write for production) to minimize the impact of potential breaches.
- Automated Key Rotation: Executing a safe, multi-step process for rotating API keys and secrets to maintain a high security posture without service interruption.
- Webhook Signature Verification: Implementing cryptographic HMAC verification for Exa webhooks to ensure data integrity and authenticity from the source.
- Security Auditing and Logging: Setting up structured audit trails to monitor API interactions and resource access for compliance and incident response.
| name | exa-security-basics |
|---|---|
| description | | |
| allowed-tools | Read, Write, Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Exa Security Basics
Overview
Security best practices for Exa API keys, tokens, and access control.
Prerequisites
- Exa SDK installed
- Understanding of environment variables
- Access to Exa dashboard
Instructions
Step 1: Configure Environment Variables
# .env (NEVER commit to git)
EXA_API_KEY=sk_live_***
EXA_SECRET=***
# .gitignore
.env
.env.local
.env.*.local
Step 2: Implement Secret Rotation
# 1. Generate new key in Exa dashboard
# 2. Update environment variable
export EXA_API_KEY="new_key_here"
# 3. Verify new key works
curl -H "Authorization: Bearer ${EXA_API_KEY}" \
https://api.exa.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 ExaClient({
apiKey: process.env.EXA_READ_KEY,
}),
writer: new ExaClient({
apiKey: process.env.EXA_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 Exa analytics
await exaClient.track('audit', log);
// Also log locally for compliance
console.log('[AUDIT]', JSON.stringify(log));
}
// Usage
await auditLog({
action: 'exa.api.call',
userId: currentUser.id,
resource: '/v1/resource',
result: 'success',
});
Resources
Next Steps
For production deployment, see exa-prod-checklist.