replit-security-basics

应用 Replit 安全最佳实践于密钥和访问控制。用于保护 API 密钥、实施最小权限访问或审计 Replit 安全配置。触发条件:Replit 安全,Replit 密钥,保护 Replit,Replit API 密钥安全。

📖 中文导读:应用 Replit 安全最佳实践于密钥和访问控制。用于保护 API 密钥、实施最小权限访问或审计 Replit 安全配置。触发条件:Replit 安全,Replit 密钥,保护 Replit,Replit API 密钥安全。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

name: replit-security-basics description: | Apply Replit security best practices for secrets and access control. Use when securing API keys, implementing least privilege access, or auditing Replit security configuration. Trigger with phrases like "replit security", "replit secrets", "secure replit", "replit API key security". allowed-tools: Read, Write, Grep version: 1.0.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io

Replit Security Basics

Overview

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

Prerequisites

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

Instructions

Step 1: Configure Environment Variables

# .env (NEVER commit to git)
REPLIT_API_KEY=sk_live_***
REPLIT_SECRET=***

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

Step 2: Implement Secret Rotation

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

# 3. Verify new key works
curl -H "Authorization: Bearer ${REPLIT_API_KEY}" \
  https://api.replit.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 ReplitClient({
    apiKey: process.env.REPLIT_READ_KEY,
  }),
  writer: new ReplitClient({
    apiKey: process.env.REPLIT_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 Replit analytics
  await replitClient.track('audit', log);

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

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

Resources

Next Steps

For production deployment, see replit-prod-checklist.