Questions
Answer these questions to discover which threat modeling approach best suits your needs.
Find the right threat modeling methodology for your needs and access RACI charts
Answer these questions to discover which threat modeling approach best suits your needs.
This comprehensive guide provides detailed RACI (Responsible, Accountable, Consulted, Informed) matrices for seven major threat modeling methodologies. Each methodology has unique strengths and is suited for different organizational contexts, security requirements, and project phases.
Developed by Microsoft in the late 1990s by Praerit Garg and Loren Kohnfelder. Microsoft Security Development Lifecycle (SDL).
Role/Group | Responsible | Accountable | Consulted | Informed |
---|---|---|---|---|
Project Manager | X | |||
Security Officer | X | X | ||
System Architect | X | |||
Development Team Lead | X | |||
Network Administrator | X | |||
Cloud/DevOps Team | X | |||
Software Developers | X | |||
Governance Board | X | |||
Business Stakeholders | X | |||
Suppliers/Vendors | X | |||
Legal/Compliance Team | X |
Developed by KU Leuven researchers Kim Wuyts, Riccardo Scandariato, Wouter Joosen (2015). "LINDDUN Privacy Threat Trees: A Systematic Methodology for Privacy Risk Management."
Role/Group | Responsible | Accountable | Consulted | Informed |
---|---|---|---|---|
Privacy Officer | X | X | ||
Data Protection Officer | X | X | ||
Security Analyst | X | |||
Legal Counsel | X | |||
Business Process Owner | X | |||
Data Engineering Team | X | |||
UX/Product Team | X | |||
Compliance Team | X | |||
Management Board | X | |||
Data Subjects Representatives | X | |||
Third-party Processors | X |
Developed by Carnegie Mellon University's Software Engineering Institute (SEI) and CERT Coordination Center. First introduced in 1999 by Christopher Alberts and Audrey Dorofee.
Role/Group | Responsible | Accountable | Consulted | Informed |
---|---|---|---|---|
OCTAVE Team Lead | X | X | ||
Business Unit Managers | X | |||
IT Operations Manager | X | |||
Risk Management Team | X | |||
Asset Owners | X | |||
Information Security Team | X | |||
External Consultants | X | |||
Executive Sponsor | X | |||
Legal/Audit Team | X | |||
Business Stakeholders | X | |||
Board of Directors | X |
Developed by Tony UcedaVelez and Marco M. Morana. Published in "Risk Centric Threat Modeling: Process for Attack Simulation and Threat Analysis" (2015).
Role/Group | Responsible | Accountable | Consulted | Informed |
---|---|---|---|---|
Threat Analyst | X | X | ||
Attack Simulation Team | X | |||
Risk Assessment Team | X | |||
Security Architect | X | |||
Red Team/Penetration Testers | X | |||
Quantitative Risk Analysts | X | |||
Business Impact Analysts | X | |||
Management Team | X | |||
Development Team | X | |||
Incident Response Team | X | |||
Stakeholders | X |
Fundamental information security model attributed to multiple sources, formally described by Jerome Saltzer and Michael Schroeder in "The Protection of Information in Computer Systems" (1975). Widely adopted across information security frameworks.
Role/Group | Responsible | Accountable | Consulted | Informed |
---|---|---|---|---|
Information Security Manager | X | X | ||
System Administrators | X | |||
Database Administrators | X | |||
Network Security Team | X | |||
Data Classification Officer | X | |||
Access Control Team | X | |||
Business Unit Heads | X | |||
Compliance Officer | X | |||
Executive Leadership | X | |||
All Staff | X | |||
External Auditors | X |
Open source threat modeling methodology developed by Brenda Larcom and Eleanor Saitta. First presented at the Security and Privacy Summit in 2006.
Role/Group | Responsible | Accountable | Consulted | Informed |
---|---|---|---|---|
Risk Management Lead | X | X | ||
Security Analysts | X | |||
Business Analysts | X | |||
Asset Managers | X | |||
Threat Modelers | X | |||
System Architects | X | |||
Security Requirements Team | X | |||
Executive Sponsor | X | |||
Audit Team | X | |||
Project Management Office | X | |||
Development Teams | X |
Developed as a specialized framework for Data Risk Evaluation, Detection, and Defense (DREDD). Originated from research on data-centric security models at the intersection of privacy engineering and threat modeling.
Role/Group | Responsible | Accountable | Consulted | Informed |
---|---|---|---|---|
Data Protection Officer | X | X | ||
Data Architects | X | |||
Data Engineers | X | |||
Data Scientists | X | |||
Security Analysts | X | |||
Cloud Security Specialists | X | |||
Compliance Team | X | |||
Privacy Team | X | |||
Executive Data Sponsor | X | |||
Data Governance Board | X | |||
Business Stakeholders | X |
Criteria | STRIDE | LINDDUN | OCTAVE | PASTA | CIA | TRIKE | DREDD |
---|---|---|---|---|---|---|---|
Complexity | Medium | Medium | High | High | Low | Medium | Medium-High |
Required Expertise | Technical | Privacy | Business | Security | General | Risk | Data |
Time Investment | Medium | Medium | High | High | Low | Medium | Medium-High |
Focus Area | Security | Privacy | Operations | Attack Simulation | Fundamentals | Risk Management | Data Protection |
Best Phase | Design | Design | Planning | Testing | All | Requirements | Architecture |
Scale | Component-System | System | Organization | System | All | Enterprise | Data Systems |
Remember: These models can be combined based on organizational needs. Many teams use a hybrid approach, starting with CIA/STRIDE and adding privacy-focused LINDDUN, data-centric DREDD, or risk-focused OCTAVE/TRIKE as needed.