keepcalculator

06 Numbers and Powers

Ransomware Threat Model: Step-by-Step Guide

Card No. 06·82255 · Updated · Standard formula, shown below

This guide walks you through building a practical ransomware threat model for your business. You’ll map out your critical assets, identify how ransomware could enter, and define concrete controls to prevent, detect, and respond. By the end, you’ll have a living document that prioritizes your defenses based on real risk, not guesswork.

What You’ll Need

  • A current inventory of your IT systems (servers, endpoints, cloud services, OT/IoT devices)
  • List of critical business functions and their dependencies (e.g., email, file storage, ERP)
  • Network diagram or at least a list of network segments and internet-facing entry points
  • Access to your backup strategy details (what’s backed up, where, how often)
  • Input from IT staff, security lead (if any), and key business unit managers
  • A spreadsheet or document tool (e.g., Excel, Google Sheets, or a wiki page)
  • 2–3 hours for the initial workshop, plus recurring review time

Step-by-Step

  1. Define your assets and their value. List all systems that hold data or support operations. For each, note the data type (customer PII, financial records, intellectual property, employee data) and the impact if that data were encrypted or exfiltrated. Use a simple scale: low (minor inconvenience), medium (significant disruption), high (business-threatening).
  2. Map the attack surface. Identify every way ransomware could enter: email (phishing attachments/links), remote desktop protocol (RDP) exposed to the internet, unpatched software, malicious ads, USB drives, third-party vendors with access, and cloud misconfigurations. Write these as entry points on your diagram.
  3. Identify likely attack paths. For each entry point, trace how an attacker would move: initial access → privilege escalation → lateral movement → reaching high-value assets or backups. Use known ransomware tactics (e.g., credential theft, exploiting SMB vulnerabilities, abusing PowerShell). Mark which paths are most feasible given your current controls.
  4. Assess existing controls. For each attack path, list what you already have: antivirus/EDR, email filtering, MFA, network segmentation, least-privilege access, backup immutability, and user training. Rate each as strong, moderate, weak, or missing.
  5. Determine likelihood and impact. For each attack path, assign a likelihood (rare, possible, likely) based on your industry and current threat landscape. Combine with the asset impact from step 1 to create a risk matrix (e.g., high impact + likely = critical).
  6. Prioritize gaps and define mitigations. Focus on the highest-risk paths first. For each gap, specify a concrete control: enable MFA on all remote access, implement backup immutability (e.g., object lock or air-gapped copies), patch critical vulnerabilities weekly, restrict RDP to VPN only, deploy EDR with rollback capabilities. Assign an owner and a due date.
  7. Plan detection and response. Define what triggers an alert (e.g., mass file renames, unusual admin logins, backup failures). Create a response playbook: isolate affected systems, preserve evidence, activate incident response, notify stakeholders, and restore from clean backups. Test the playbook with a tabletop exercise.
  8. Document and review regularly. Write the model in a shared document with a clear version history. Review it quarterly or after any major change (new system, merger, cloud migration). Update likelihoods as the threat landscape shifts.

Common Mistakes

  • Focusing only on prevention. Ransomware will eventually get in; if you have no detection/response plan, you’ll lose more time and money.
  • Ignoring backups in the model. If backups are on the same network or lack versioning, they can be encrypted too. Always include backup security as a key control.
  • Treating all assets equally. A small internal wiki is not as critical as your customer database. Prioritize based on impact.
  • Overlooking third-party access. Vendors with VPN or remote support can be a backdoor. Include them in your attack surface.
  • Making the model a one-time project. Ransomware tactics evolve; a static model becomes obsolete quickly.
  • Not involving business stakeholders. IT cannot guess which systems are truly critical. Ask department heads.

Tips

  • Use a visual whiteboard for the first session—it helps everyone see the attack paths clearly.
  • Start small: even a 5-row table with assets, entry points, and controls is better than nothing.
  • Align your controls with a recognized framework like NIST CSF or CIS Controls to avoid gaps.
  • Test your assumptions: run a phishing simulation to see how many users click, or review firewall logs for exposed RDP.
  • Include “what if” scenarios: what if the attacker deletes backups? What if they’re inside for 30 days before encrypting?
  • Keep the document concise—executives should be able to read it in 15 minutes.

Troubleshooting

  • You don’t have a complete asset inventory. Start with the systems you know are critical (email, file server, financial software) and expand later. Use network scanning tools to discover unknown devices.
  • Stakeholders disagree on impact ratings. Facilitate a discussion using concrete scenarios: “If this system is down for a week, what happens to revenue?” Let them decide.
  • The model feels too large. Break it into smaller phases: first map only internet-facing systems, then move to internal. Or focus on one business unit at a time.
  • You identify too many gaps to fix. Prioritize by risk score (likelihood × impact). Fix the top 3–5 first. Document the rest as accepted risks with a review date.
  • You’re not sure how to test backups. Perform a restore test of a critical server to a test environment. If it fails, fix the backup process immediately.

Frequently Asked Questions

Do we need a threat model if we already have antivirus and backups?

Yes. Antivirus and backups are important but don’t cover all paths. A threat model helps you see where those controls might fail and what else is needed, like MFA or network segmentation.

How often should we update the threat model?

At least quarterly, or after any significant change (new cloud service, merger, remote work expansion). Also review after a major ransomware news event to see if your assumptions changed.

What’s the difference between a threat model and a risk assessment?

A threat model focuses on specific attack paths and controls; a risk assessment is broader, covering all types of risk (financial, operational, compliance). A threat model is a key input to a risk assessment.

We’re a small business with no IT staff. Can we still do this?

Yes, but adapt it: use a simple spreadsheet, focus on your top 5 critical systems, and consider hiring a managed security service provider (MSSP) to help implement controls. Even a basic model is better than none.

Should we include insider threats in the model?

Yes, but ransomware is usually external. Still, an insider could accidentally click a malicious link or intentionally leak credentials. Include user behavior as an entry point.

What if we find a critical gap we can’t fix immediately?

Document it as an accepted risk with a mitigation plan and a deadline. For example, if you can’t implement MFA on legacy systems, restrict access to those systems and monitor them closely.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →