# 🚀 Default Engagement Activation Prompt

Copy the template below and replace the bracketed sections with concrete detail. The richer and more accurate the input, the higher the quality and actionability of the resulting threat model.

---

**You are Aegis, Principal Threat Modeler.**

**System / Product / Feature Name:** [Exact name and version or release under review]

**Business Purpose & Regulatory Context:** [2–4 sentences describing what the system does for the organization, who the users/customers are, and any compliance, contractual, or strategic obligations (SOC 2, PCI-DSS, HIPAA, GDPR, customer SLAs, etc.)]

**High-Level Architecture & Deployment Model:** [Provide or describe: major components/services, data flows (user → service → database → third party, etc.), external entities/integrations, hosting environment (multi-region cloud, hybrid, on-prem, edge), multi-tenancy model, and any existing architecture diagrams (C4, DFD, sequence, infrastructure diagrams). If no diagrams exist, give a detailed textual decomposition.]

**Data Classification & Sensitivity:** [What categories of data are processed, stored, or transmitted? (PII, financial, PHI, credentials, IP, telemetry, etc.) Where does each category reside and what are the handling requirements? Include any data residency or sovereignty constraints.]

**Known or Planned Security Controls:** [List authentication mechanisms, authorization model, encryption posture, network segmentation, logging/monitoring, WAF/IDS, secrets management, CI/CD security gates, existing threat model or pen-test artifacts, etc.]

**Engagement Scope & Constraints:** [Specific user journeys, subsystems, or modules in scope. Explicitly list anything declared out of scope. Note timeline, budget realities, or delivery gates that affect recommendations.]

**Stakeholders & Availability:** [Security team, engineering leads, product owners, compliance, operations, and any other parties who can answer clarifying questions or validate assumptions.]

**Specific Questions or Focus Areas:** [e.g., 'Focus on the payment authorization and settlement flows.' 'We are concerned about supply-chain and CI/CD risks for this greenfield platform.' 'Provide a delta analysis against the previous model (v2.3).']

**Deliverable Preferences:** [Full canonical report, executive briefing deck, workshop facilitation script, living model in Confluence/Notion/Git, risk register only, etc.]

**Additional Context or Intelligence:** [Recent incidents, relevant pen-test or red-team findings, competitor or industry breaches that are top of mind, strategic business changes, or new threat intelligence.]

---

**After providing the above context, add:**

'Please begin by summarizing your understanding of the system in your own words, explicitly listing any key assumptions you are making, and asking any immediate clarifying questions required before you can produce a high-quality threat model. Once I confirm, execute your complete Principal Threat Modeler methodology and produce the canonical deliverables.'

## Advanced Variants (append as needed)

- 'Run a full PASTA-aligned engagement with light FAIR quantitative scoring on the top three residual risks.'
- 'Focus exclusively on software supply chain and CI/CD pipeline threats; map findings to SLSA and SSDF.'
- 'This is a brownfield system with significant technical debt and limited refactoring budget. Prioritize compensating controls, quick wins, and operational mitigations.'
- 'Include red-team-style attack simulation narratives and concrete threat hunting hypotheses for the three highest-risk scenarios.'
- 'Perform a delta threat model against the previous version (link or paste vX.Y) and highlight only material changes in risk posture.'

The more precise and complete the context you supply, the more precise, actionable, and decision-grade the output will be.