firecrawl-security-basics
Apply FireCrawl security best practices for secrets and access control.Use when securing API keys, implementing least privilege access,or auditing FireCrawl security configuration.Trigger with phrases like "firecrawl security", "firecrawl secrets","secure firecrawl", "firecrawl API key security".
When & Why to Use This Skill
This Claude skill provides comprehensive security best practices for FireCrawl, focusing on API key protection, secret rotation, and least privilege access. It helps developers secure their web scraping infrastructure by providing actionable steps for environment configuration, webhook verification, and audit logging to prevent data leaks and unauthorized access.
Use Cases
- Securing API keys using environment variables and .gitignore to prevent accidental exposure in public repositories.
- Implementing secret rotation workflows to maintain long-term security and mitigate the impact of compromised credentials.
- Enforcing least privilege access by configuring environment-specific API scopes for development, staging, and production.
- Verifying webhook signatures to ensure data integrity and authenticity from FireCrawl events.
- Setting up audit logging and security checklists to maintain compliance and monitor API usage patterns.
| name | firecrawl-security-basics |
|---|---|
| description | | |
| allowed-tools | Read, Write, Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
FireCrawl Security Basics
Overview
Security best practices for FireCrawl API keys, tokens, and access control.
Prerequisites
- FireCrawl SDK installed
- Understanding of environment variables
- Access to FireCrawl dashboard
Instructions
Step 1: Configure Environment Variables
# .env (NEVER commit to git)
FIRECRAWL_API_KEY=sk_live_***
FIRECRAWL_SECRET=***
# .gitignore
.env
.env.local
.env.*.local
Step 2: Implement Secret Rotation
# 1. Generate new key in FireCrawl dashboard
# 2. Update environment variable
export FIRECRAWL_API_KEY="new_key_here"
# 3. Verify new key works
curl -H "Authorization: Bearer ${FIRECRAWL_API_KEY}" \
https://api.firecrawl.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 FireCrawlClient({
apiKey: process.env.FIRECRAWL_READ_KEY,
}),
writer: new FireCrawlClient({
apiKey: process.env.FIRECRAWL_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 FireCrawl analytics
await firecrawlClient.track('audit', log);
// Also log locally for compliance
console.log('[AUDIT]', JSON.stringify(log));
}
// Usage
await auditLog({
action: 'firecrawl.api.call',
userId: currentUser.id,
resource: '/v1/resource',
result: 'success',
});
Resources
Next Steps
For production deployment, see firecrawl-prod-checklist.