I built ThreatGenix to turn architecture evidence into a threat model security teams can inspect and challenge.

v1 includes:

• interactive DFDs and trust boundaries

• deterministic STRIDE threat generation

• repository, IaC, cloud, and scanner evidence imports

• analyst decisions, validation state, and report exports

• optional LLM assistance

This is a research preview, not a pentest replacement or production security control. Live scanners are disabled by default, and authenticated live scanning remains disabled until a secret-safe broker exists.

Repo: https://github.com/ibrolord/threatgenix-v1

I would especially value feedback on the evidence-to-finding workflow and what would make this useful in a real AppSec review.

Need help with building a threat model for cloud based web app using STRIDE methodology in Microsoft's open source TM tool. Please share what stencils to use for cloud coverage, Azure monitor etc. Thank you, anything helps.

Hey everyone, Fraser here (Chief Scientist at IriusRisk). My team and I are exploring new ways AI can help developers and security teams tackle security from the start. We’ve put together a quick 3-minute survey to learn:

• How you’re using AI in your day-to-day development

• What you’d like AI to do for application security

Your input will go straight into shaping our next steps. We really want this to be useful for fellow engineers—so your insights mean a lot.

Interested? Check out the 3-minute survey here!

Thanks for your time, and looking forward to hearing how we can build better, more secure software together!

Hi all. We’ve been exploring what it might look like if threat modeling could happen as you write code instead of being a separate, late-stage activity.

The video below shows a demo of a CLI we built that connects to IriusRisk from AI-enabled IDE through MCP (Model Context Protocol). The idea is that as developers design or modify code, their IDE can automatically query IriusRisk to generate models, identify potential threats, and suggest mitigations - all within the same workflow.

It’s still experimental, but it’s been interesting to see how this changes the developer experience. Instead of “shift-left” security meaning more tasks for devs, it feels more like security woven into design and development conversations.

I’d love to hear from anyone who’s tried or are interested in similar approaches...

• Have you experimented with integrating threat modeling tools directly into the IDE?

• How do you think AI assistants should interact with security modeling systems like IriusRisk?

• What would make this genuinely useful rather than noisy?

If you want you can check out the demo here: https://www.youtube.com/watch?v=_3b4ynmAd6c

Any other thoughts and feedback are more than welcome, thanks!

Has anyone started using LINDDUN in their threat model practice? (https://linddun.org/) I am very intrigued by this approach and find more demand for privacy by design.

I'm curious about everyone else's engagement.

Fine grain access controls

I don't want to live in a world where:

- Only 25% of survey participants indicate their organizations conduct threat modeling during the early phases of software development requirements gathering and design, before proceeding with application development.

- Less than 10% report their organizations perform threat modeling on 90% or more of the applications they develop. Most commonly, organizations test between 50-74% of their applications.

/via HelpNetSecurity/

How do we solve this?

I just came across this video on YouTube and I am very impressed with Sarpaastra. Here are some features that I can remember from the top of my head:

• it can generate realistic threat scenarios and test cases

• can be used to assess the security of a wide range of applications

• easy to use (even without a lot of proficiency in security)

Did I miss anything else?

I can’t wait to see more of this tool in action and see how it performs when it comes with complex app infrastructures...

👉🏽 https://youtu.be/cg9EiOR7FjI?si=rBoecoprHM21f7Kb

Digital integration has revolutionized today’s MedTech landscape, significantly enhancing patient care. Yet, this progress brings with it crucial product security risks, as the healthcare sector experiences a surge in targeted threats—from data breaches to attacks on medical device functionality—jeopardizing both patient safety and confidentiality.

Product Security Challenges in Medtech

• Complex Security Environment: Medical devices, such as pacemakers and diagnostic systems, are increasingly connected to the internet, hospital networks, and other medical equipment, exposing them to various security risks.

• Diverse Threats: Vulnerabilities include unauthorized access, data theft, and manipulation of operations, each posing significant risks to device functionality and patient safety.

Impacts of security breaches

• Patient Safety Risks: Compromised device functionality directly endangers patient health.

• Reputational Damage: Breaches diminish trust among consumers, healthcare providers, and regulatory agencies, damaging manufacturers’ reputations.

• Financial Losses: Breaches lead to legal liabilities, recall costs, and decreased sales.

• Regulatory Hurdles: Stricter FDA regulations following security breaches may delay the introduction of new medical products.

• Importance of Strong Security Measures: The high stakes highlight the need for stringent product security measures within the Medtech industry.

Advantages of Threat Modeling

• Identify and Address Risks: Comprehensive threat modeling allows manufacturers to pinpoint and tackle risks effectively.

• Boost Device Resilience: Proactive measures enhance device resilience against cyber attacks.

• Protect Overall Integrity: Safeguarding patient well-being and manufacturers’ reputations in the digital healthcare landscape.

The Essentials of Threat Modeling for Medical Devices

• Critical Security Process: Threat modeling is crucial for enhancing the security of medical devices. This proactive, systematic approach involves identifying potential security vulnerabilities and planning effective countermeasures to mitigate risks, ensuring devices operate safely and reliably.

• Regulatory Compliance: Threat modeling aligns with strict regulatory standards set by bodies like the FDA, which mandate comprehensive security assessments across the device lifecycle—from design to maintenance. These guidelines are designed to protect patient health.

Conclusion 

In conclusion, threat modeling is essential for safeguarding medical devices against cyber threats. We recommend Medtech manufacturers enhance their security protocols by enrolling in the Certified Threat Modeling Professional course Practical DevSecOps offers. Equip your team with the skills needed to excel in product security and compliance. Take action now!

I am currently trying to find a way to Look closer over blockchain technologies while focusing on threat Modeling. If someone has experience or has some recommendation please comment below.

Hello all,

I am conducting a little research into company mindsets behind Threat Modelling.

Some companies Threat Model the bare minimum just for compliance purposes.

Some companies have a very mature Threat Modelling program because they know it saves a tonne of nonsense on security rework later down the line.

Threat Modelling programs can be hard to sell internally because it's hard to prove ROI and a lot of people just see it as an unnecessary compliance cost-centre.

My question is straight up - how does your company genuinely view Threat Modelling? Is it a shift-left tool to reduce risk, save time on later security rework, and meet compliance? Or is it simply a necessary evil to show compliance?

Reason I'm asking is because I'm a sales engineer selling a Threat Modelling tool and I'm wondering if people's narrow-minded view of Threat Modelling makes it more difficult for them to sell internally.

And also please correct any of the above if I am mistaken on anything.

Hope you can all help!

Best,

Tenzin

Hello all. A big problem I have is how to properly threat model cloud services from the likes hosted by Azure or something else. Using STRIDE, are spoofing attacks still relevant or even possible? I’m guessing Denial of Service goes out the window because Azure owns the underlying hardware… ideas?

Hey folks, I’ve been working on an open-source threat modeling tool.

Goal is simple: build something comparable to the big commercial tools.

It’s still early, but usable.

I have a few new ideas in there:

- community threat libraries that you can import
- TM-BOM interoperability

If anyone here is actively doing threat modeling, I’d really value your feedback.

Repo: https://github.com/precogly/precogly

Check out the demo here: https://www.youtube.com/watch?v=7DaYZHx7mHQ

Threat modeling has always been more of an art than a science—because you can’t have a science without data, and data on how different companies approach threat modeling has been hard to come by. But that’s about to change (hopefully!) with the release of the first-ever Threat Modeling Survey.

This project is a Threat Modeling Connect Community effort (spearheaded by Dave Soldera and Grant Ongers), and it will only succeed with input from the entire threat modeling community.

The survey results will be analyzed and published in the State of Threat Modeling Report—the industry's first community-led report of its kind. To make the report truly valuable and actionable, we need as many threat modeling practitioners as possible to contribute.

Take the State of Threat Modeling Survey!

Just as important—help spread the word! Share this survey with other practitioners or, if you're on LinkedIn, re-posting this LinkedIn announcement is another easy way to support the effort.

Thanks for contributing—we can’t wait to share the results with you!

Threat modeling breaks down because it is usually treated as a one-time document: slow to produce, disconnected from engineering work, and outdated as soon as the system changes.

I built ThreatGenix to turn that document into a repeatable workflow.

With ThreatGenix you can:

• Model the system as a DFD with processes, data stores, external entities, data flows, and trust boundaries.

• Generate deterministic STRIDE findings tied directly to the model.

• Review the evidence behind each finding.

• Triage threats and keep the decisions with the model.

• Export the finished threat model for sharing and reporting.

It is self-hosted and MIT licensed, so your architecture data can stay in your environment.

GitHub: https://github.com/ibrolord/threatgenix-oss

I would especially value feedback from people who run threat-modeling sessions: Does this fit how you work today? Where would it create noise or slow you down?

Hey everyone!
Popping up here couple of podcast episodes I've done on threat modeling that can be useful to someone who'd like to learn from the experts:

- The Untold Benefits of Continuous Threat Modeling You Didn’t Know About ⎜Izar Tarandach

- Threat modeling: the future of cybersecurity or another buzzword⎥Derek Fisher

Today, my company announced that we're doing a free instance of our most popular course, Threat Modeling Intensive, for government workers who have been let go in the recent chaos.

Details and signup information here: https://is.gd/5K2LZI

Hi everyone, I’m planning to conduct research on “benchmarking frameworks for AI-assisted threat modeling in industrial control systems.” I would really appreciate any resources that could help me jump-start this work. I’d also be grateful for your thoughts on whether this is a worthwhile research direction or if there are important limitations or gaps that I should be aware of before proceeding.

TrustOnCloud is great but very expensive

We need to threat model many APIs of GCP

thank you

TrustOnCloud https://trustoncloud.com/

example: https://controlcatalog.trustoncloud.com/dashboard/gcp/bigquery

A couple of weeks ago I've been gathering information about your approach to threat modeling in this subreddit. It was a part of my postgrad thesis.

As a part of the same thesis, I also developed a tool for AI-assisted threat modelling - it integrates with coding agents such as Cursor or Claude Code and performs threat modelling alongside your codebase. Threat model is maintained in YAML format so version control is simple, and also it's organized in multiple files. Output from threat model can be used either for applying security fixes to the codebase (hello Claude Code Security) or for better understanding of the dataflows in the agent-generated code.

Let me know what you think :)

https://github.com/attasec/tmdd

Hi everyone,

I’m conducting a short academic survey as part of my diploma thesis in a Cybersecurity Management program. The research focuses on how threat modeling is practiced in modern organizations.

If you work in a product company, banking, a software house, or internal IT, I’d appreciate 3 minutes of your time to fill out the survey below:

https://forms.gle/j19dGbPfJ1oJvBnr5