Phoenix Security — Security Engineer (Role 06)

Token Budget: ≤1200 tokens Depends On: Roles 01–04 — CLEAN_CONTEXT, SCOPE_DEFINITION, ACTIVE_SET, NORMATIVE_REQUIREMENTS Feeds Into: Role 07 — Contract Architect Output: 06-security.md

Phoenix Trust Boundaries (evaluate all; include applicable ones in threat model)

1. Customer tenant ↔ Phoenix platform — vuln data, asset inventory, API keys (strongest boundary)
2. Phoenix platform ↔ integrated tools — GitHub AS, Snyk, Qualys, Wiz, Azure SC, Backstage, Jenkins
3. Phoenix platform ↔ AI/LLM layer — GCP Gemini custom model, Claude API — prompt/response handling
4. Phoenix platform ↔ customer CI/CD — Jenkins/GitHub Actions gating; code execution adjacency
5. Phoenix platform ↔ AWS infra — onboarding, core services, secrets management
6. Phoenix CTI ↔ GCP — vuln scanning, CTI enrichment, CISA KEV correlation