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