mindtickle-security-basics
Security Basics for MindTickle. Trigger: "mindtickle security basics".
What this skill does
# MindTickle Security Basics
## Overview
MindTickle integrations process employee PII through SCIM provisioning (names, emails, job titles, manager chains) and HR-sensitive data like course completion scores, certification status, and coaching assessments. The API uses bearer token authentication combined with a `Company-Id` header for multi-tenant isolation — omitting or spoofing this header can leak data across tenants. Webhook payloads carrying training completion events must be HMAC-verified to prevent injection of fraudulent compliance records.
## Prerequisites
- Secrets manager (AWS SSM, GCP Secret Manager, or Vault) for API tokens
- HTTPS enforced on all SCIM and webhook endpoints
- `Company-Id` validated against an allowlist of known tenant identifiers
- `.env` files in `.gitignore` — never committed to version control
- Data retention policy for employee training records (GDPR/SOC2)
## API Key Management
```typescript
// MindTickle requires both bearer token and company ID for multi-tenant isolation
const MT_API_TOKEN = process.env.MINDTICKLE_API_KEY;
const MT_COMPANY_ID = process.env.MINDTICKLE_COMPANY_ID;
function validateMindTickleConfig(): void {
if (!MT_API_TOKEN) throw new Error('Missing MINDTICKLE_API_KEY');
if (!MT_COMPANY_ID) throw new Error('Missing MINDTICKLE_COMPANY_ID');
}
function mindtickleHeaders(): Record<string, string> {
return {
Authorization: `Bearer ${MT_API_TOKEN}`,
'Company-Id': MT_COMPANY_ID!,
'Content-Type': 'application/json',
};
}
// Call validateMindTickleConfig() at startup — both values are required for every request
```
## Webhook Signature Verification
```typescript
import crypto from 'node:crypto';
const MT_WEBHOOK_SECRET = process.env.MINDTICKLE_WEBHOOK_SECRET!;
function verifyMindTickleWebhook(payload: string, signature: string, timestamp: string): boolean {
// Reject stale webhooks (>5 min) to prevent replay attacks
const age = Date.now() - parseInt(timestamp, 10) * 1000;
if (age > 300_000) return false;
const signedPayload = `${timestamp}.${payload}`;
const expected = crypto
.createHmac('sha256', MT_WEBHOOK_SECRET)
.update(signedPayload, 'utf8')
.digest('hex');
return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}
app.post('/webhooks/mindtickle', (req, res) => {
const sig = req.headers['x-mindtickle-signature'] as string;
const ts = req.headers['x-mindtickle-timestamp'] as string;
if (!sig || !ts || !verifyMindTickleWebhook(JSON.stringify(req.body), sig, ts)) {
return res.status(401).json({ error: 'Invalid signature or stale timestamp' });
}
// Process verified training completion event
});
```
## Input Validation
```typescript
// Validate SCIM user payloads — employee PII requires strict schema enforcement
interface ScimUser {
userName: string;
name: { givenName: string; familyName: string };
emails: { value: string; primary: boolean }[];
}
function validateScimUser(user: unknown): user is ScimUser {
const u = user as Record<string, unknown>;
if (typeof u.userName !== 'string' || u.userName.length > 254) return false;
const emails = u.emails as { value: string }[] | undefined;
if (!emails?.every(e => /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(e.value))) return false;
return true;
}
```
## Data Protection
```typescript
function redactEmployeeData(record: Record<string, unknown>): Record<string, unknown> {
const piiFields = ['email', 'userName', 'phone', 'manager_email', 'employee_id'];
const hrFields = ['score', 'certification_status', 'coaching_notes'];
const redacted = { ...record };
for (const field of [...piiFields, ...hrFields]) {
if (redacted[field]) redacted[field] = '[REDACTED]';
}
return redacted;
}
// Redact before logging — course scores and coaching data are HR-confidential
```
## Access Control
```typescript
// Enforce tenant isolation — Company-Id must match the authenticated context
const ALLOWED_COMPANY_IDS = new Set(process.env.MT_ALLOWED_COMPANIES?.split(',') ?? []);
function assertTenantAccess(companyId: string): void {
if (!ALLOWED_COMPANY_IDS.has(companyId)) {
throw new Error(`Unauthorized tenant: ${companyId}`);
}
}
function assertScimWriteAccess(operation: string, hasScimScope: boolean): void {
const writeOps = ['createUser', 'updateUser', 'deactivateUser'];
if (writeOps.includes(operation) && !hasScimScope) {
throw new Error(`SCIM write operation "${operation}" requires scim:write scope`);
}
}
```
## Security Checklist
- [ ] Bearer token and Company-Id stored in secrets manager
- [ ] Company-Id validated against tenant allowlist on every request
- [ ] Webhook HMAC-SHA256 verified with timestamp replay protection
- [ ] SCIM payloads validated against strict schema before processing
- [ ] Employee PII (email, name, phone) redacted in all logs
- [ ] Course scores and coaching data classified as HR-confidential
- [ ] SCIM write operations gated behind explicit scope checks
- [ ] Data retention policy enforced for training completion records
- [ ] Token rotation scheduled quarterly with zero-downtime swap
## Error Handling
| Vulnerability | Risk | Mitigation |
|---|---|---|
| Missing Company-Id header | Cross-tenant data leakage | Reject requests without validated Company-Id |
| Unverified webhooks | Fraudulent training completion records | HMAC-SHA256 + timestamp validation on every webhook |
| SCIM PII in logs | Employee data breach (GDPR/SOC2) | Redact all PII fields before logging |
| Stale webhook replay | Duplicate or backdated compliance events | Reject webhooks older than 5 minutes |
| Over-permissioned SCIM token | Unauthorized user provisioning | Enforce scim:write scope check for mutations |
## Resources
- [MindTickle Developer Platform](https://www.mindtickle.com/platform/integrations/)
- [OWASP API Security Top 10](https://owasp.org/www-project-api-security/)
## Next Steps
See `mindtickle-prod-checklist`.
Related in Security
mac-ops
IncludedComprehensive macOS workstation operations — diagnose kernel panics, identify failing drives, audit launchd startup items, decode wake reasons, triage TCC permission denials, manage APFS snapshots, recover from no-boot. Use for: Mac is slow, slow bootup, won't boot, kernel panic, kernel_task hot, mds_stores CPU, photoanalysisd, cloudd, login loop, gray screen, sleep wake failure, drive failing, IO errors, APFS snapshots eating space, Time Machine local snapshots, Spotlight indexing, launchd, LaunchAgent, LaunchDaemon, login items, TCC permissions, Full Disk Access, Screen Recording denied, Gatekeeper, quarantine, com.apple.quarantine, app is damaged, helper tool, /Library/PrivilegedHelperTools, pmset, wake reasons, dark wake, sysdiagnose, panic.ips, DiagnosticReports, configuration profile, MDM profile, remote diagnostics over SSH.
a11y-audit
IncludedRun accessibility audits on web projects combining automated scanning (axe-core, Lighthouse) with WCAG 2.1 AA compliance mapping, manual check guidance, and structured reporting. Output is configurable: markdown report only, markdown plus machine-readable JSON, or markdown plus issue tracker integration. Use this skill whenever the user mentions "accessibility audit", "a11y audit", "WCAG audit", "accessibility check", "compliance scan", or asks to check a web project for accessibility issues. Also trigger when the user wants to verify WCAG conformance or map findings to a specific standard (CAN-ASC-6.2, EN 301 549, ADA/AODA).
erpclaw
IncludedAI-native ERP system with self-extending OS. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting. 413 actions across 14 domains, 43 expansion modules. Constitutional guardrails, adversarial audit, schema migration. Double-entry GL, immutable audit trail, US GAAP.
assess
IncludedAssesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use when evaluating code, designs, architectures, or comparing alternative approaches.
spring-boot-security-jwt
IncludedProvides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based access control using Spring Security 6.x. Use when implementing authentication or authorization in Spring Boot applications.
code-hardcode-audit
IncludedDetect hardcoded values, magic numbers, and leaked secrets. TRIGGERS - hardcode audit, magic numbers, PLR2004, secret scanning.