Checking threat modeling data flow diagrams for implementation conformance and security
Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering
Impact of inheritance on vulnerability propagation at design phase
ACM SIGSOFT Software Engineering Notes
Analyzing security architectures
Proceedings of the IEEE/ACM international conference on Automated software engineering
Modeling security attacks with statecharts
Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
The security cost of cheap user interaction
Proceedings of the 2011 workshop on New security paradigms workshop
Idea: reusability of threat models – two approaches with an experimental evaluation
ESSoS'10 Proceedings of the Second international conference on Engineering Secure Software and Systems
TAM2: automated threat analysis
Proceedings of the 27th Annual ACM Symposium on Applied Computing
Survey and analysis on Security Requirements Engineering
Computers and Electrical Engineering
| Hi-index | 0.00 |
If done early in the development life cycle, threat modeling can revealarchitecturalweaknesses that could require significant changes to your product. Making design changes early in the product life cycle is much cheaper than trying to make them at the end.