Software Engineering, Project Management, and Effectiveness
Here's my trying to explain threat modeling (actually core modeling) to a customer …
My core theme of the modeling is this:
This is the approach I use whether it's security or performance or any other quality attribute. In the case of threat modeling, vulnerabilities are the key. These go in your bug database and help scope test.
I'm not a security expert, but I'm far from clueless and this seems like a solid and useful approach.
It reminds me, however, of my favorite all-time quote about models...
"All models are wrong. Some models are useful." -- George Box, Industrial Statistician.
The point being that models are, by design, simplifications of reality to aid in understanding and communication. If they weren't simplifications, they wouldn't be models -- they would be replications!
So my note to all your readers is this... Use models, they are powerful! Don't over-use models, they can steer you away from major issues that will bite you when you least expect it!
President & Chief Technologist, PerfTestPlus, Inc.
Executive Director, Association for Software Testing
"If you can see it in your mind...
you will find it in your life."
I always suggest conducting Threat Modeling even in advanced dev cycle stages, although it might seem
Threat Modeling is a way to identify potential security issues to help you shape your application's security
Threat Modeling is a way to identify potential security issues to help you shape your application's
When people ask me my take on model-driven approaches, I think of two ends of the spectrum -- human and