$npx -y skills add Chipagosfinest/enterprise-team --skill security-catchallRoutes security requests to the correct specialist: secure coding, auditing, compliance, or penetration testing. Covers OWASP, SOC2, GDPR, authentication, encryption, and vulnerability management. Triggers: security audit, vulnerability, penetration test, compliance, gdpr, soc2,
| 1 | # Security Department |
| 2 | |
| 3 | Routes security work to the appropriate specialist role. |
| 4 | |
| 5 | ## Routing Targets |
| 6 | |
| 7 | | Role | Handles | |
| 8 | |---|---| |
| 9 | | security-engineer | Secure coding, auth implementation, encryption, OWASP fixes, secrets management | |
| 10 | | security-auditor | Penetration testing, vulnerability assessments, threat modeling, risk reports | |
| 11 | | compliance-officer | SOC2, GDPR, HIPAA, regulatory audits, compliance programs, policy review | |
| 12 | |
| 13 | ## Examples |
| 14 | |
| 15 | - "Review this auth implementation for vulnerabilities" -> security-engineer |
| 16 | - "Run a security audit on our API endpoints" -> security-auditor |
| 17 | - "Ensure our data handling is GDPR-compliant" -> compliance-officer |
| 18 | - "Fix the XSS vulnerability in the search input" -> security-engineer |
| 19 | - "Create a threat model for our payment system" -> security-auditor |
| 20 | - "Prepare documentation for our SOC2 audit" -> compliance-officer |
| 21 | - "Implement rate limiting and API key rotation" -> security-engineer |
| 22 | |
| 23 | ## Workflow |
| 24 | |
| 25 | 1. Identify whether the request is about implementation, assessment, or compliance. |
| 26 | 2. For broad security reviews, start with security-auditor for assessment, then security-engineer for fixes. |
| 27 | 3. For compliance-related requests, always involve compliance-officer. |
| 28 | 4. For security incidents, route to sre (via infrastructure-orchestrator) for immediate response, then security-auditor for post-mortem. |