OWASP Threat Modelling Project

From OWASP
Revision as of 11:48, 4 April 2011 by Anurag Agarwal (Talk | contribs)

Jump to: navigation, search

Main

Project About

PROJECT INFO
What does this OWASP project offer you?
RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP Threat Modelling Project (home page)
Purpose: N/A
License: N/A
who is working on this project?
Project Leader(s):
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: Mailing List Archives
Project Roadmap: View
Key Contacts
  • Contact the GPC to report a problem or concern about this project or to update information.
current release
Not Yet Published
last reviewed release
Not Yet Reviewed


other releases


Threat Modeling Working Session Summary from OWASP Portugal Summit

Discussion Points:


1. Threat Modeling – Existing Challenges

2. Taxonomy

3. Threat Modeling Approaches (Asset Centric, System Centric, Attacker centric)

4. Methodology

       a. Existing Methodologies
       i.	Microsoft
       ii.	Trike 
       iii.	PASTA
       b. Classifying threats into Risk
       c. Technical Impact vs Business Impact

5. Input to Threat Modeling

6. Components of a Threat Model (Asset, Threat Agent, Actors, Threats, etc)

7. Output of Threat Modeling

8. Consumers of Threat Model

9. Attack Trees – Advantages and Disadvantages

10. Application Decomposition and DFDs

11. Threat Modeling Tools (TAM, PTA, ThreatModeler)

12. Threat Modeling and Abuse Case Modeling

13. Threat Library (more focused threats as opposed to Top 10, WASC TC)

14. Do we need an OWASP Threat Modeling project?



Accomplishments:

1. An insight into how people have been doing threat modeling individually. There is no set standard used by people but everyone has their own.

2. Discussion on having an OWASP threat modeling project and let OWASP drive build and drive a standard which can be adopted by the industry.

3. Discussion on various components of threat modeling and how they fit into the process.


Output:

1. A unanimous vote to having an OWASP threat modeling project.

2. Promotion of such a project to not only security consultants but also having contributors from an end user organization to provide their feedback on challenges and such.

3. OWASP to promote the methodology to establish it as a standard in the industry.


Next Steps:

1. High level project roadmap with milestones.

2. Call for participants

3. Review existing resources within OWASP to align with threat modeling project.

4. Come up with a threat modeling methodology

5. Publish the first draft