Quantitative Risk Estimation With FAIR
Applies the FAIR model to estimate annualized loss exposure for a risk scenario with ranges and assumptions.
Prompt
ROLE: You are a quantitative cyber risk analyst applying the FAIR (Factor Analysis of Information Risk) model to express a risk in financial terms.
CONTEXT:
- Risk scenario to quantify: [THREAT_ACTOR_+_ASSET_+_LOSS_EVENT]
- Available data points: [INCIDENT_HISTORY_INDUSTRY_BENCHMARKS_CONTROL_STRENGTH]
- Asset value & cost factors: [RECORD_COUNTS_RESPONSE_COSTS_FINES_DOWNTIME]
- Existing controls: [WHAT_REDUCES_FREQUENCY_OR_MAGNITUDE]
TASK — reason step by step through the FAIR decomposition:
1. Define the loss event scenario precisely (asset, threat, effect).
2. Estimate Loss Event Frequency: Threat Event Frequency x Vulnerability (or Contact x Probability of Action x control strength), as a range (min/most-likely/max).
3. Estimate Loss Magnitude: primary losses (response, replacement, productivity) and secondary losses (fines, legal, reputation), as ranges.
4. Combine into Annualized Loss Exposure (range), and state the distribution intuition (avoid false precision).
5. Show how a candidate control would shift frequency or magnitude, and the implied risk reduction.
OUTPUT FORMAT:
- Scenario statement
- Frequency estimate (min/likely/max + reasoning)
- Magnitude estimate (primary + secondary, with ranges)
- Annualized Loss Exposure range
- Control sensitivity ('if we do X, ALE moves from A to B')
- Key assumptions & data-quality caveats
CONSTRAINTS: Use ranges and explicit assumptions, never single-point fake precision. Label every estimate's confidence and source. Keep primary and secondary losses separate. If data is thin, say so and provide a defensible estimate with stated uncertainty rather than refusing.How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueAsks the model to reason step by step before answering — ideal for multi-step, logical, or analytical tasks.
Learn this techniquePins the response to a defined structure so it drops straight into your workflow.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Cybersecurity & Risk
STRIDE Threat Model For A New Service
Builds a structured STRIDE threat model for a system with trust boundaries, ranked threats, and concrete mitigations.
Security Incident Postmortem Author
Drafts a blameless post-incident review with timeline, root cause, and corrective actions ready for leadership.
CVE Triage And Prioritization Analyst
Triages a list of CVEs by exploitability and business context to produce an actionable patch priority queue.
Phishing Email Forensic Examiner
Analyzes a suspicious email's headers, URLs, and payload to classify intent and recommend SOC response.