brightdata-security-basics
Apply Bright Data security best practices for secrets and access control. Use when securing API keys, implementing least privilege access, or auditing Bright Data security configuration. Trigger with phrases like "brightdata security", "brightdata secrets", "secure brightdata", "brightdata API key security".
claude-code
Allowed Tools
ReadWriteGrep
Provided by Plugin
brightdata-pack
Claude Code skill pack for Bright Data (18 skills)
Installation
This skill is included in the brightdata-pack plugin:
/plugin install brightdata-pack@claude-code-plugins-plus
Click to copy
Instructions
Bright Data Security Basics
Overview
Security best practices for Bright Data API keys, tokens, and access control.
Prerequisites
- Bright Data SDK installed
- Understanding of environment variables
- Access to Bright Data dashboard
Instructions
Step 1: Configure Environment Variables
# .env (NEVER commit to git)
BRIGHTDATA_API_KEY=sk_live_***
BRIGHTDATA_SECRET=***
# .gitignore
.env
.env.local
.env.*.local
Step 2: Implement Secret Rotation
# 1. Generate new key in Bright Data dashboard
# 2. Update environment variable
export BRIGHTDATA_API_KEY="new_key_here"
# 3. Verify new key works
curl -H "Authorization: Bearer ${BRIGHTDATA_API_KEY}" \
https://api.brightdata.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 BrightDataClient({
apiKey: process.env.BRIGHTDATA_READ_KEY,
}),
writer: new BrightDataClient({
apiKey: process.env.BRIGHTDATA_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 Bright Data analytics
await brightdataClient.track('audit', log);
// Also log locally for compliance
console.log('[AUDIT]', JSON.stringify(log));
}
// Usage
await auditLog({
action: 'brightdata.api.call',
userId: currentUser.id,
resource: '/v1/resource',
result: 'success',
});
Resources
Next Steps
For production deployment, see brightdata-prod-checklist.