HIPAA Security RuleSecurity Risk AnalysisePHI

Threat modeling for healthcare

The HIPAA Security Rule requires a Security Risk Analysis of every system that touches electronic protected health information -- threat identification, vulnerability identification, and risk determination. ThreatTree gives your team a structured place to build that analysis and keep it current as systems change.

  • Free forever plan
  • Scope threat models to ePHI systems
  • Export anytime, no lock-in
ThreatTree data flow diagram of a patient portal with the Healthcare module on: inside a covered entity network boundary, a patient portal and clinical API read from a records database and write to an access audit log, with a lab partner sending HL7 results. The records database is selected and classified as ePHI.
Real screenHealthcare module: the records database classified as ePHI. Industry Modules are included on Pro and Enterprise.

What is healthcare threat modeling?

Healthcare threat modeling is threat modeling of systems that create, store or move electronic protected health information, such as EHRs, patient portals and integrations. Under the HIPAA Security Rule it provides the threat identification, vulnerability analysis and risk determination a security risk analysis needs.

HIPAA Security Rule

Security Risk Analysis, mapped to ThreatTree

OCR guidance points to NIST SP 800-30 for how a Security Risk Analysis should be structured. Here's where each step fits in a ThreatTree forest.

NIST 800-30 step In ThreatTree
1 System & asset characterization
Where ePHI is created, received, maintained, or transmitted
DFD processes and data stores tagged for ePHI, with trust boundaries around each system boundary
2 Threat identification
Sources and events that could compromise ePHI confidentiality, integrity, or availability
Walking every DFD element through STRIDE, with each threat tagged on an attack tree node, surfaces spoofing, tampering, and disclosure threats systematically
3 Vulnerability identification
Weaknesses a threat could exploit
Attack Trees decompose each threat scenario into AND/OR attack steps down to the exploitable weakness, tagged with CAPEC and MITRE ATT&CK
4 Likelihood & impact determination
Probability of occurrence and severity of harm to ePHI
Likelihood x Impact scoring per attack tree node, weighted toward confidentiality and availability of ePHI
5 Risk determination & documentation
Combine likelihood and impact, document for OCR review
A ranked risk register generated automatically across the forest, exportable as a PDF for your risk analysis file

What this is, and isn't: ThreatTree addresses the technical system-level threat and risk analysis a HIPAA Security Risk Analysis requires. It does not cover administrative or physical safeguards, workforce training, or Business Associate Agreement management -- and it isn't a substitute for your compliance and legal teams' judgment on whether your overall risk analysis satisfies the Security Rule.

Why teams use ThreatTree

A risk analysis you can keep current

Every threat traces back to an ePHI system, and every risk decision traces back to a rated attack path.

01

Architecture-Anchored ePHI Flows

Model EHR systems, medical devices, and third-party integrations as DFD elements, with trust boundaries around each. Every threat traces back to a real system, not a floating assumption.

02

Attack Path Decomposition

Break each threat into an Attack Tree with AND/OR logic, from attacker goal to atomic step, so vulnerabilities are documented, not just implied.

03

Prioritized Risk Register

Likelihood x Impact scoring generates a ranked risk register automatically across every tree in a forest -- the risk determination step, backed by traceable evidence.

04

Team Collaboration & RBAC

Invite IT, security, and compliance leads with owner, editor, or viewer roles, so the risk analysis stays a living document instead of an annual one-off exercise.

05

Healthcare Systems in the Palette

With the Healthcare module on, the DFD palette adds a Healthcare group: EHR, FHIR API server, HL7 interface engine, PACS / DICOM imaging, patient portal, health information exchange, clinical device gateway and e-prescribing service.

06

Threats Mapped to the HIPAA Security Rule

Each element has its own suggested threats, at least five each, from FHIR APIs returning the wrong patient to unauthenticated DICOM, mapped to the Security Rule's safeguards (164.308 and 164.312) for your team to review.

FAQ

Healthcare threat modeling, answered

What covered entities and business associates ask before adopting ThreatTree.

Still have questions?

We usually reply within a day.

Get in touch
Is ThreatTree a full HIPAA Security Risk Assessment tool?

No. ThreatTree addresses the technical system-level threat and risk analysis a HIPAA Security Risk Analysis requires -- it does not cover administrative or physical safeguard questionnaires, workforce training tracking, or Business Associate Agreement management.

Does using ThreatTree satisfy 45 CFR 164.308(a)(1)(ii)(A)?

ThreatTree helps you build and document the threat identification, vulnerability identification, and risk determination steps that provision describes, following the structure OCR guidance points to in NIST SP 800-30. Whether your overall risk analysis satisfies the Security Rule is a determination your compliance and legal teams make, not something this page or product can guarantee.

Can I scope a threat model to just our ePHI systems?

Yes. Tag the data stores, processes, and interfaces that touch electronic protected health information and draw a trust boundary around them, so the threat model stays focused on where PHI actually flows.

How often should we update the risk analysis?

OCR guidance treats risk analysis as ongoing, not a once-a-year checkbox. Because a ThreatTree forest is a living model, you can update it whenever a system changes rather than re-doing the whole analysis from scratch annually.

Working through a Security Risk Analysis? Get new threat-modeling guides by email — no more than one a week.

Start your Security Risk Analysis in ThreatTree

Free plan available -- no credit card required. Be up and running in minutes.