Apply BambooHR security best practices for API keys, webhook verification,
and PII data handling compliance.
Use when securing API keys, implementing webhook signature validation,
or handling sensitive employee data from BambooHR.
Trigger with phrases like "bamboohr security", "bamboohr secrets",
"secure bamboohr", "bamboohr PII", "bamboohr data protection".
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Apply BambooHR security best practices for API keys, webhook verification,
and PII data handling compliance.
Use when securing API keys, implementing webhook signature validation,
or handling sensitive employee data from BambooHR.
Trigger with phrases like "bamboohr security", "bamboohr secrets",
"secure bamboohr", "bamboohr PII", "bamboohr data protection".
allowed-tools
Read, Write, Grep
version
1.4.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
["saas","hr","bamboohr","security"]
compatibility
Designed for Claude Code
BambooHR Security Basics
Overview
Security best practices for BambooHR API integrations covering API key management, webhook HMAC verification, PII handling, and access control. BambooHR contains highly sensitive employee data (SSNs, salaries, addresses) — treat every integration as PII-critical.
Prerequisites
BambooHR API access configured
Understanding of environment variables and secrets management
Access to BambooHR admin settings
Instructions
Step 1: API Key Security
# .env (NEVER commit to git)
BAMBOOHR_API_KEY=your-api-key
BAMBOOHR_COMPANY_DOMAIN=yourcompany
BAMBOOHR_WEBHOOK_SECRET=your-webhook-hmac-secret
# .gitignore — MUST include these
.env
.env.local
.env.*.local
*.pem
Key management rules:
Each environment (dev/staging/prod) uses a separate API key
Create API keys under service accounts, not personal accounts
API keys inherit the permissions of the user who created them
Rotate keys quarterly; immediately rotate if exposed
Key rotation procedure:
# 1. Generate new key in BambooHR: Profile > API Keys > Add New Key# 2. Update secret store
aws secretsmanager update-secret --secret-id bamboohr/api-key --secret-string "new-key"# Or for GCP:echo -n "new-key" | gcloud secrets versions add bamboohr-api-key --data-file=-
# 3. Deploy with new key# 4. Verify new key works
curl -s -o /dev/null -w "%{http_code}" \
-u "new-key:x" \
"https://api.bamboohr.com/api/gateway.php/${DOMAIN}/v1/employees/directory" \
-H "Accept: application/json"# 5. Delete old key in BambooHR dashboard
Step 2: Webhook Signature Verification
BambooHR signs webhook payloads with SHA-256 HMAC. Verify every webhook before processing.
- [ ] API keys stored in environment variables or secret manager (never in code)
- [ ] `.env` files in `.gitignore`- [ ] Separate API keys for dev / staging / prod
- [ ] API key user has minimum required access level
- [ ] Webhook signatures verified with HMAC-SHA256
- [ ] Webhook timestamp checked (reject > 5 min old)
- [ ] PII fields redacted from logs and error messages
- [ ] Only requesting needed fields (not SELECT *)
- [ ] Restricted fields (SSN, salary) only accessed when required
- [ ] Data at rest encrypted if storing BambooHR data locally
- [ ] API key rotation scheduled (quarterly minimum)
- [ ] git-secrets or truffleHog scanning enabled