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