# Threat + Mitigation properties
**URL:** https://threatmodelingconnect.discourse.group/t/threat-mitigation-properties/1173
**Category:** Techniques & Tooling
**Created:** [September 16, 2025, 12:22pm UTC](https://threatmodelingconnect.discourse.group/t/threat-mitigation-properties/1173 "2025-09-16T12:22:18Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@hewerlin](https://threatmodelingconnect.discourse.group/u/hewerlin)
#### Post date: [September 16, 2025, 12:22pm UTC](https://threatmodelingconnect.discourse.group/t/threat-mitigation-properties/1173/1 "2025-09-16T12:22:18Z")
Let’s say I design a TM tool and it has threats and mitigations.
When you click on them, you get a key/value editor.
1. What are the properties you would like to see in a threat editor?
2. What are the properties you would like to see in a mitigation editor?
3. If those are enum types, what enum values would you propose?
I’m looking for maximal ideas + a minimal loveable set of properties.
---
### Author:  [@donavancheah](https://threatmodelingconnect.discourse.group/u/donavancheah)
#### Post date: [September 23, 2025, 5:49am UTC](https://threatmodelingconnect.discourse.group/t/threat-mitigation-properties/1173/2 "2025-09-23T05:49:53Z")
At a minimum:
- I want to be able to support multiple threat modeling frameworks. The frameworks themselves may have degrees of overlap, or operate in a chain (e.g. STRIDE-LM tells me the loss of a cybersecurity property, LINDDUN tells me the loss of a privacy property, but MITRE CAPEC/ATT&CK tell me how these attacks result in the loss of associated security properties)
- For a mitigation editor, I need to be able to keep a repository of said mitigations, how they may lower risk likelihood, where they are applied, whether or not they adequately address risk.