210:
220:(DFD). DFDs were developed in the 1970s as tool for system engineers to communicate, on a high level, how an application caused data to flow, be stored, and manipulated by the infrastructure upon which the application runs. Traditionally, DFDs utilize only four unique symbols: data flows, data stores, processes, and interactors. In the early 2000s, an additional symbol, trust boundaries, were added to improve the usefulness of DFDs for threat modeling.
165:
dynamic threat identification, enumeration, and scoring process. Once the threat model is completed, security subject matter experts develop a detailed analysis of the identified threats. Finally, appropriate security controls can be enumerated. This methodology is intended to provide an attacker-centric view of the application and infrastructure from which defenders can develop an asset-centric mitigation strategy.
118:
highest semantic levels of the DML model. This is followed by the TTP (Tactics, Techniques and
Procedures) which represent intermediate semantic levels. The lowest semantic levels of the DML model are the tools used by the attacker, host and observed network artifacts such as packets and payloads, and finally atomic indicators such as IP addresses at the lowest semantic level. Current
296:. In this context, threats to security and privacy like information about the inhabitant's movement profiles, working times, and health situations are modeled as well as physical or network-based attacks. The latter could make use of more and more available smart building features, i.e., sensors (e.g., to spy on the inhabitant) and actuators (e.g., to unlock doors).
201:
and enumerate potential threats. Further analysis of the model regarding risks associated with identified threats, prioritization of threats, and enumeration of the appropriate mitigating controls depends on the methodological basis for the threat model process being utilized. Threat modeling approaches can focus on the system in use, attackers, or assets.
278:
is a
Pythonic framework for threat modeling and the first Threat-Model-as-Code tool: The system is first defined in Python using the elements and properties described in the pytm framework. Based on this definition, pytm can generate a Data Flow Diagram (DFD), a Sequence Diagram and most important of
173:
The focus of the Trike methodology is using threat models as a risk-management tool. Within this framework, threat models are used to satisfy the security auditing process. Threat models are based on a "requirements model." The requirements model establishes the stakeholder-defined "acceptable" level
271:
is a modeling tool used to create threat model diagrams as part of a secure development lifecycle. Threat Dragon follows the values and principles of the threat modeling manifesto. It can be used to record possible threats and decide on their mitigations, as well as giving a visual indication of the
264:
is a software security requirements management platform that includes automated threat modeling capabilities. A set of threats is generated by filling out a short questionnaire on the application's technical details and compliance factors. Countermeasures are included in the form of actionable tasks
257:
to security engineer, including technician. securiCAD performs automated attack simulations on current and future IT architectures, identifies and quantifies risks globally, including structural vulnerabilities, and provides decision support based on results. securiCAD is available in commercial and
164:
The
Process for Attack Simulation and Threat Analysis (PASTA) is a seven-step, risk-centric methodology. It provides a seven-step process for aligning business objectives and technical requirements, taking into account compliance issues and business analysis. The intent of the method is to provide a
117:
should be expressed with different semantic levels, and proposed the DML (Detection
Maturity Level) model. An attack is an instantiation of a threat scenario which is caused by a specific attacker with a specific goal in mind and a strategy for reaching that goal. The goal and strategy represent the
82:
published his analysis of cyber risks utilizing attack trees in his paper entitled "Toward a Secure System
Engineering Methodology". The paper proved to be a seminal contribution in the evolution of threat modeling for IT-systems. In Schneier's analysis, the attacker's goal is represented as a "root
200:
All IT-related threat modeling processes start with creating a visual representation of the application, infrastructure or both being analyzed. The application or infrastructure is decomposed into various elements to aid in the analysis. Once completed, the visual representation is used to identify
223:
Once the application-infrastructure system is decomposed into its five elements, security experts consider each identified threat entry point against all known threat categories. Once the potential threats are identified, mitigating security controls can be enumerated or additional analysis can be
182:
The Visual, Agile and Simple Threat (VAST) methodology, is based on ThreatModeler, a commercial automated threat-modeling platform. VAST requires creating two types of models: application threat models and operational threat models. Application threat models use process-flow diagrams, representing
155:
was created in 1999 at
Microsoft as a mnemonic for developers to find 'threats to our products'. STRIDE can be used as a simple prompt or checklist, or in more structured approaches such as STRIDE per element. STRIDE, Patterns and Practices, and Asset/entry point were amongst the threat modeling
26:
or the absence of appropriate safeguards, can be identified and enumerated, and countermeasures prioritized. The purpose of threat modeling is to provide defenders with a systematic analysis of what controls or defenses need to be included, given the nature of the system, the probable attacker's
42:
Conceptually, most people incorporate some form of threat modeling in their daily life and don't even realize it. Commuters use threat modeling to consider what might go wrong during the morning journey to work and to take preemptive action to avoid possible accidents. Children engage in threat
142:
Conceptually, a threat modeling practice flows from a methodology. Numerous threat modeling methodologies are available for implementation. Typically, threat modeling has been implemented using one of five approaches independently: asset-centric, attacker-centric, software-centric, value and
272:
threat model components and threat surfaces. Threat Dragon runs either as a web application or as a desktop application. Threat Dragon supports STRIDE / LINDDUN / CIA / DIE / PLOT4ai, provides modeling diagrams and implements a rule engine to auto-generate threats and their mitigations.
62:
In 1994, Edward
Amoroso put forth the concept of a "threat tree" in his book, "Fundamentals of Computer Security Technology." The concept of a threat tree was based on decision tree diagrams. Threat trees graphically represent how a potential threat to an IT system can be exploited.
51:
Shortly after shared computing made its debut in the early 1960s, individuals began seeking ways to exploit security vulnerabilities for personal gain. As a result, engineers and computer scientists soon began developing threat modeling concepts for information technology systems.
174:
of risk assigned to each asset class. Analysis of the requirements model yields a threat model from which threats are enumerated and assigned risk values. The completed threat model is used to construct a risk model based on asset, roles, actions, and calculated risk exposure.
98:
for: Spoofing identity, Tampering with data, Repudiation, Information disclosure, Denial of service, Elevation of privilege) The resultant mnemonic helps security professionals systematically determine how a potential attacker could utilize any threat included in STRIDE.
83:
node," with the potential means of reaching the goal represented as "leaf nodes." Utilizing the attack tree in this way allowed cybersecurity professionals to systematically consider multiple attack vectors against any defined target.
183:
the architectural point of view. Operational threat models are created from an attacker point of view based on DFDs. This approach allows for the integration of VAST into the organization's development and DevOps lifecycles.
122:(Security Information and Event Management) tools typically only provide indicators at the lowest semantic levels. There is therefore a need to develop SIEM tools that can provide threat indicators at higher semantic levels.
43:
modeling when determining the best path toward an intended goal while avoiding the playground bully. In a more formal sense, threat modeling has been used to prioritize military defensive preparations since antiquity.
237:(formerly SDL Threat Modeling Tool), also uses the Microsoft threat modeling methodology, is based on DFD and identifies threats based on the STRIDE threat classification system. It is mainly intended for general use.
133:
In 2024 the same group of authors followed up the
Manifesto with a Threat Modeling Capabilities document, which "...provides a catalog of capabilities to help you cultivate value from your Threat Modeling practice".
191:
Researchers created this method to combine the positive elements of different methodologies. This methodology combines different methodologies, including SQUARE and the
Security Cards and Personae Non Gratae.
102:
In 2003, OCTAVE (Operationally
Critical Threat, Asset, and Vulnerability Evaluation) method, an operations-centric threat modeling methodology, was introduced with a focus on organizational risk management.
130:
The threat modeling manifesto is a document published in 2020 by threat modeling authorities in order to clearly state the core values and principles that every threat modeler should know and follow.
247:. It drives the process using fully customizable questionnaires and risk model libraries, and connects to several other different tools (OWASP ZAP, BDD-Security, Threadfix) to enable automation.
821:
563:
253:
is a threat modeling and risk management tool from the Scandinavian company foreseeti. It is intended for enterprise cybersecurity management, from
548:
243:
provides both a community and a commercial version of the tool. This tool focuses on creating and maintaining a living threat model throughout the
703:
345:
74:
on a structured graphical representation of how specific attacks against IT-systems could be executed. The resulting representation was called "
110:
wrote "Threat Modeling," published by Microsoft press. In it they developed the concept of using threat models to create secure applications.
143:
stakeholder-centric, and hybrid. Based on the volume of published online content, the methodologies discussed below are the most well known.
156:
approaches developed and published by Microsoft. References to "the" Microsoft methodology commonly mean STRIDE and Data Flow Diagrams.
119:
55:
Early technology-centered threat modeling methodologies were based on the concept of architectural patterns first presented by
877:
27:
profile, the most likely attack vectors, and the assets most desired by an attacker. Threat modeling answers questions like
23:
907:
90:
and Praerit Garg developed a model for considering attacks relevant to the Microsoft Windows development environment. (
649:
374:
59:
in 1977. In 1988 Robert Barnard developed and successfully applied the first profile for an IT-system attacker.
808:
244:
860:
Meyer, D.; Haase, J.; Eckert, M.; Klauer, B. (2016-07-01). "A threat-model for building and home automation".
690:
391:
587:
492:
612:
626:
515:
665:
67:
316:
427:
209:
56:
114:
8:
289:
288:
Threat modeling is being applied not only to IT but also to other areas such as vehicle,
477:
883:
873:
836:
645:
542:
446:
370:
217:
152:
91:
887:
865:
832:
331:
87:
732:
409:
516:"Risk Centric Threat Modeling: Process for Attack Simulation and Threat Analysis"
293:
869:
784:
79:
768:
901:
107:
809:
http://publications.lib.chalmers.se/records/fulltext/252083/local_252083.pdf
463:
678:
364:
452:. Semantic Technology for Intelligence, Defence and Security (STIDS 2016).
195:
862:
2016 IEEE 14th International Conference on Industrial Informatics (INDIN)
75:
820:
Hamad, Mohammad; Prevelakis, Vassilis; Nolte, Marcus (November 2016).
796:
757:"Cyber Threat Modelling and Risk Management - securiCAD by foreseeti"
564:"Threat modeling explained: A process for anticipating cyber attacks"
204:
95:
46:
719:
349:
265:
for developers that can be tracked and managed across the SDLC.
831:. Publications Institute of Computer and Network Engineering.
530:
529:
Eddington, Michael, Brenda Larcom, and Eleanor Saitta (2005).
415:. Software Engineering Institute, Carnegie Mellon: Pittsburgh.
756:
71:
666:"Security Quality Requirements Engineering Technical Report"
254:
37:"What do I need to do to safeguard against these threats?"
369:. AT&T Bell Labs. Prentice-Hall: Upper Saddle River.
332:"The World's First Computer Password? It Was Useless Too"
642:
Threat Modeling: A Practical Guide for Development Teams
640:
Tarandach, Izar; Coles, Matthew J. (24 November 2020).
196:
Generally accepted technology threat modeling processes
859:
186:
704:"What's New with Microsoft Threat Modeling Tool 2016"
822:"Towards Comprehensive Threat Modeling for Vehicles"
819:
205:Visual representations based on data flow diagrams
66:Independently, similar work was conducted by the
22:is a process by which potential threats, such as
16:Process of identifying structural vulnerabilities
899:
392:"Toward A Secure System Engineering Methodology"
283:
113:In 2014, Ryan Stillions expressed the idea that
86:In 1999, Microsoft cybersecurity professionals
47:Evolution of technology-centric threat modeling
639:
514:Ucedavélez, Tony and Marco M. Morana (2015).
137:
547:: CS1 maint: multiple names: authors list (
366:Fundamentals of Computer Security Technology
125:
561:
513:
352:. John Wiley & Sons Inc: Indianapolis.
528:
444:
425:
350:"Threat Modeling: Designing for Security"
679:https://securitycards.cs.washington.edu/
389:
344:
329:
227:
208:
588:"Threat Modeling: 12 Available Methods"
407:
397:. National Security Agency: Washington.
362:
29:"Where am I most vulnerable to attack?"
900:
410:"Introduction to the OCTAVE® Approach"
855:
853:
390:Schneier, Bruce; et al. (1998).
33:"What are the most relevant threats?"
311:
309:
216:Most threat modeling approaches use
691:"CSDL | IEEE Computer Society"
613:"The Hybrid Threat Modeling Method"
187:'The Hybrid' Threat Modeling Method
13:
850:
491:Kohnfelder, Loren; Garg, Praerit.
14:
919:
769:"SD Elements by Security Compass"
720:"Irius Risk Risk Management Tool"
627:"A Hybrid Threat Modeling Method"
518:. John Wiley & Sons: Hobekin.
306:
837:10.24355/dbbs.084-201806251532-0
829:Institute of Control Engineering
644:. O'Reilly Media, Incorporated.
447:"Semantic Cyberthreat Modelling"
813:
802:
790:
778:
762:
750:
725:
713:
697:
683:
672:
658:
633:
619:
605:
580:
562:Fruhlinger, Josh (2020-04-15).
555:
531:"Trike v1 Methodology Document"
522:
507:
484:
470:
262:SD Elements by Security Compass
478:"Threat Modeling Capabilities"
456:
438:
419:
401:
383:
356:
338:
323:
1:
408:Alberts, Christopher (2003).
299:
284:Further fields of application
106:In 2004, Frank Swiderski and
432:Ryan Stillions security blog
7:
722:. Continuum Security. 2016.
490:
464:"Threat Modeling Manifesto"
279:all, threats to the system.
10:
926:
908:Computer security exploits
870:10.1109/INDIN.2016.7819280
363:Amoroso, Edward G (1994).
138:Threat modeling frameworks
24:structural vulnerabilities
493:"Threats to Our Products"
330:McMillan, Robert (2012).
317:"The STRIDE Threat Model"
146:
126:Threat Modeling Manifesto
445:Bromander, Siri (2016).
426:Stillions, Ryan (2014).
168:
159:
775:. Retrieved 2017-03-24.
773:www.securitycompass.com
733:"foreseeti - securiCAD"
177:
213:
785:"OWASP Threat Dragon"
708:Microsoft Secure Blog
228:Threat modeling tools
212:
57:Christopher Alexander
864:. pp. 860–866.
235:Threat Modeling Tool
269:OWASP Threat Dragon
258:community editions.
710:. Microsoft. 2015.
668:. 31 October 2005.
319:. Microsoft. 2016.
218:data flow diagrams
214:
879:978-1-5090-2870-2
594:. 2 December 2018
434:. Ryan Stillions.
334:. Wired Business.
233:Microsoft's free
915:
892:
891:
857:
848:
847:
845:
843:
826:
817:
811:
806:
800:
794:
788:
782:
776:
766:
760:
754:
748:
747:
745:
743:
729:
723:
717:
711:
701:
695:
694:
687:
681:
676:
670:
669:
662:
656:
655:
637:
631:
630:
629:. 27 March 2018.
623:
617:
616:
615:. 22 April 2018.
609:
603:
602:
600:
599:
584:
578:
577:
575:
574:
559:
553:
552:
546:
538:
526:
520:
519:
511:
505:
504:
502:
500:
488:
482:
481:
474:
468:
467:
460:
454:
453:
451:
442:
436:
435:
423:
417:
416:
414:
405:
399:
398:
396:
387:
381:
380:
360:
354:
353:
342:
336:
335:
327:
321:
320:
313:
88:Loren Kohnfelder
925:
924:
918:
917:
916:
914:
913:
912:
898:
897:
896:
895:
880:
858:
851:
841:
839:
824:
818:
814:
807:
803:
795:
791:
783:
779:
767:
763:
755:
751:
741:
739:
731:
730:
726:
718:
714:
702:
698:
689:
688:
684:
677:
673:
664:
663:
659:
652:
638:
634:
625:
624:
620:
611:
610:
606:
597:
595:
586:
585:
581:
572:
570:
560:
556:
540:
539:
527:
523:
512:
508:
498:
496:
489:
485:
476:
475:
471:
462:
461:
457:
449:
443:
439:
428:"The DML Model"
424:
420:
412:
406:
402:
394:
388:
384:
377:
361:
357:
343:
339:
328:
324:
315:
314:
307:
302:
294:home automation
286:
230:
207:
198:
189:
180:
171:
162:
149:
140:
128:
49:
20:Threat modeling
17:
12:
11:
5:
923:
922:
911:
910:
894:
893:
878:
849:
812:
801:
789:
777:
761:
749:
724:
712:
696:
682:
671:
657:
651:978-1492056553
650:
632:
618:
604:
579:
554:
521:
506:
483:
469:
455:
437:
418:
400:
382:
375:
355:
346:Shostack, Adam
337:
322:
304:
303:
301:
298:
285:
282:
281:
280:
273:
266:
259:
248:
238:
229:
226:
206:
203:
197:
194:
188:
185:
179:
176:
170:
167:
161:
158:
148:
145:
139:
136:
127:
124:
80:Bruce Schneier
48:
45:
15:
9:
6:
4:
3:
2:
921:
920:
909:
906:
905:
903:
889:
885:
881:
875:
871:
867:
863:
856:
854:
838:
834:
830:
823:
816:
810:
805:
798:
793:
786:
781:
774:
770:
765:
758:
753:
738:
737:foreseeti.com
734:
728:
721:
716:
709:
705:
700:
692:
686:
680:
675:
667:
661:
653:
647:
643:
636:
628:
622:
614:
608:
593:
589:
583:
569:
565:
558:
550:
544:
536:
535:Octotrike.org
532:
525:
517:
510:
494:
487:
479:
473:
465:
459:
448:
441:
433:
429:
422:
411:
404:
393:
386:
378:
376:9780131089297
372:
368:
367:
359:
351:
347:
341:
333:
326:
318:
312:
310:
305:
297:
295:
291:
277:
274:
270:
267:
263:
260:
256:
252:
249:
246:
242:
239:
236:
232:
231:
225:
221:
219:
211:
202:
193:
184:
175:
166:
157:
154:
144:
135:
131:
123:
121:
116:
115:cyber threats
111:
109:
108:Window Snyder
104:
100:
97:
93:
89:
84:
81:
77:
73:
69:
64:
60:
58:
53:
44:
40:
38:
34:
30:
25:
21:
861:
840:. Retrieved
828:
815:
804:
797:"OWASP pytm"
792:
780:
772:
764:
759:. foreseeti.
752:
742:November 27,
740:. Retrieved
736:
727:
715:
707:
699:
685:
674:
660:
641:
635:
621:
607:
596:. Retrieved
591:
582:
571:. Retrieved
567:
557:
534:
524:
509:
497:. Retrieved
486:
472:
458:
440:
431:
421:
403:
385:
365:
358:
340:
325:
287:
275:
268:
261:
250:
240:
234:
222:
215:
199:
190:
181:
172:
163:
150:
141:
132:
129:
112:
105:
101:
85:
76:attack trees
65:
61:
54:
50:
41:
36:
32:
28:
19:
18:
495:. Microsoft
224:performed.
78:." In 1998
598:2022-02-03
573:2022-02-03
568:CSO Online
300:References
276:OWASP pytm
251:securiCAD
241:IriusRisk
902:Category
888:12725362
842:11 March
592:SEI Blog
543:cite web
348:(2014).
290:building
96:acrostic
886:
876:
648:
373:
153:STRIDE
147:STRIDE
94:is an
92:STRIDE
35:, and
884:S2CID
825:(PDF)
499:4 Feb
450:(PDF)
413:(PDF)
395:(PDF)
169:Trike
160:PASTA
72:DARPA
874:ISBN
844:2019
744:2018
646:ISBN
549:link
501:2024
371:ISBN
292:and
255:CISO
245:SDLC
178:VAST
151:The
120:SIEM
70:and
866:doi
833:doi
68:NSA
904::
882:.
872:.
852:^
827:.
771:.
735:.
706:.
590:.
566:.
545:}}
541:{{
533:.
430:.
308:^
39:.
31:,
890:.
868::
846:.
835::
799:.
787:.
746:.
693:.
654:.
601:.
576:.
551:)
537:.
503:.
480:.
466:.
379:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
