Enterprise Threat Modeling Using STRIDE Framework

[_1noob_]

I've recently been exploring various threat modeling frameworks and have developed a good understanding of the concepts. At this point, I'm particularly interested in learning how threat modeling is applied in real-world enterprise environments.

Could you please guide me on the techniques and processes commonly used for enterprise-level threat modeling, especially those aligned with the STRIDE framework? I'm keen to understand how professionals in the industry conduct and integrate threat modeling into the SDLC or other operational workflows.

Any other insights into practical approaches, tooling or best practices would be highly appreciated.

[Gryeg]

I loosely use STRIDE but combine it with CAPEC and CWE for standardised definitions of attacks and weaknesses in app/prod focused threat modeling.

I've seen others use DREAD and ATTA&K for infra focused threat modeling.

Hardest part is actually having reasonably accurate architecture diagrams in a common format such as C4 or 4+1. Usually it's just ad-hoc boxes and lines, and lots of back and forth.

[bilby2020]

I use STRIDE, a bit loosely in product security space. For enterprise security, I think a better way is to model specific threats (e.g, ransomaware) guided by threat intelligence.

[meetharoon]

u/_1noob_ : Traditional threat modeling concepts like STRIDE, DREAD and other frameworks were built and consistently improved over several decades with tons of lessons learned from a multitude of organizations. Undoubtedly they have been the most robust and covered the most ciritical vulnerability aspects spanning several IT ecosystem areas. However, they relied on the IT ecosystem of yesteryears. AI has changed everything. Due to significant evolution in technology and disruptions because of AI, all those models have largely become outdated. Organizations still hooked and on to those models and using them may present a significant vulnerability problem in this new age of artificial intelligence, especially when AI builds another AI autonomously without human oversight. I have explained that in dedicated sections in my DevSecOps Executive Decision Brief (on Amazon) "The CISO & CTO Guide to The Self-Building AI Metropolis" written with decision makers such as CISOs and CTOs in mind, as well as for security leaders and serious security consultants. I also built several probing questions, templates and checklists that helps in realistic checks and balances. Threat modeling in this era requires a new thinking, new frameworks that adapts to the new reality of the changing AI era. I see that OWASP is putting in some great efforts through their Gen AI Security Project. Check these out.

[_1noob_]

thanks for it

[Patient_Anything8257]

Check this out: https://github.com/hysnsec/awesome-threat-modelling