procore-security-basics

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

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

Allowed Tools

ReadWriteGrep

Provided by Plugin

procore-pack

Claude Code skill pack for Procore (24 skills)

saas packs v1.0.0
View Plugin

Installation

This skill is included in the procore-pack plugin:

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

Click to copy

Instructions

Procore Security Basics

Overview

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

Prerequisites

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

Instructions

Step 1: Configure Environment Variables


# .env (NEVER commit to git)
PROCORE_API_KEY=sk_live_***
PROCORE_SECRET=***

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

Step 2: Implement Secret Rotation


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

# 3. Verify new key works
curl -H "Authorization: Bearer ${PROCORE_API_KEY}" \
  https://api.procore.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 ProcoreClient({
    apiKey: process.env.PROCORE_READ_KEY,
  }),
  writer: new ProcoreClient({
    apiKey: process.env.PROCORE_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 Procore analytics
  await procoreClient.track('audit', log);

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

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

Resources

Next Steps

For production deployment, see procore-prod-checklist.

Ready to use procore-pack?