remofirst-security-basics

Apply RemoFirst security best practices for secrets and access control. Use when securing API keys, implementing least privilege access, or auditing RemoFirst security configuration. Trigger with phrases like "remofirst security", "remofirst secrets", "secure remofirst", "remofirst API key security".

claude-code
3 Tools
remofirst-pack Plugin
saas packs Category

Allowed Tools

ReadWriteGrep

Provided by Plugin

remofirst-pack

Claude Code skill pack for RemoFirst (12 skills)

saas packs v1.0.0
View Plugin

Installation

This skill is included in the remofirst-pack plugin:

/plugin install remofirst-pack@claude-code-plugins-plus

Click to copy

Instructions

RemoFirst Security Basics

Overview

Security best practices for RemoFirst API keys, tokens, and access control.

Prerequisites

  • RemoFirst SDK installed
  • Understanding of environment variables
  • Access to RemoFirst dashboard

Instructions

Step 1: Configure Environment Variables


# .env (NEVER commit to git)
REMOFIRST_API_KEY=sk_live_***
REMOFIRST_SECRET=***

# .gitignore
.env
.env.local
.env.*.local

Step 2: Implement Secret Rotation


# 1. Generate new key in RemoFirst dashboard
# 2. Update environment variable
export REMOFIRST_API_KEY="new_key_here"

# 3. Verify new key works
curl -H "Authorization: Bearer ${REMOFIRST_API_KEY}" \
  https://api.remofirst.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 RemoFirstClient({
    apiKey: process.env.REMOFIRST_READ_KEY,
  }),
  writer: new RemoFirstClient({
    apiKey: process.env.REMOFIRST_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
  • [ ] .env files 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 RemoFirst analytics
  await remofirstClient.track('audit', log);

  // Also log locally for compliance
  console.log('[AUDIT]', JSON.stringify(log));
}

// Usage
await auditLog({
  action: 'remofirst.api.call',
  userId: currentUser.id,
  resource: '/v1/resource',
  result: 'success',
});

Resources

Next Steps

For production deployment, see remofirst-prod-checklist.

Ready to use remofirst-pack?