This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP PyTM"
Hblankenship (talk | contribs) (Created page with "<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</div> {| style="padding: 0;margin:0;margin-top:10px;text-alig...") |
|||
| Line 4: | Line 4: | ||
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | ||
| − | |||
| − | |||
| − | |||
==Project About== | ==Project About== | ||
| − | |||
{{Template:Project_About | {{Template:Project_About | ||
| project_name=PyTM | | project_name=PyTM | ||
| + | | project_description=A Pythonic framework for threat-modeling-from-code | ||
| + | | project_license=MIT License | ||
| leader_name1=Izar Tarandach | | leader_name1=Izar Tarandach | ||
| − | | | + | | leader_name2= Matthew J. Coles |
| + | | contributor_name1=Rohit Shambhuni | ||
| + | | contributor_name2=Nick Ozmore | ||
| + | | contributor_name3=Pooja Ahvad | ||
| + | | presentation_link=https://www.youtube.com/watch?v=VbW-X0j35gw AppSecCali 2019 - Threat Model Every Story: Practical Continuous Threat Modeling Work for Your Team - | ||
}} | }} | ||
| − | ==OWASP | + | ==OWASP PyTM== |
| − | + | PyTM is an effort to enable developers to create and maintain threat models in a way that is natural for them, using a familiar OO syntax (Python, but should be generic enough to enable any developer with minimal OO experience to use it) to describe a system in terms of its elements and their attributes, in a way that can be easily shared, version-controlled and collaborated on. | |
| − | |||
| − | |||
| − | + | That description is a self-enclosed Python script that when run generates diagrams (DFDs and sequence), threats (based on a library of rules) and reports (joining diagrams and threats). | |
==Description== | ==Description== | ||
| Line 28: | Line 28: | ||
</span> | </span> | ||
| − | |||
| − | |||
| − | |||
| − | |||
==Licensing== | ==Licensing== | ||
| Line 39: | Line 35: | ||
</span> | </span> | ||
| − | This program is free software: you can redistribute it and/or modify it under the terms of the [ | + | This program is free software: you can redistribute it and/or modify it under the terms of the [https://opensource.org/licenses/MIT MIT License] as published by the Massachusetts Institute of Technology. OWASP PyTM and any contributions are Copyright © by the Project Leader(s). |
==Roadmap== | ==Roadmap== | ||
| Line 88: | Line 84: | ||
== Project Leader == | == Project Leader == | ||
| − | + | Izar Tarandach | |
| − | |||
| − | |||
| − | + | Matthew J. Coles | |
== Related Projects == | == Related Projects == | ||
| − | + | * [[OWASP_Threat_Dragon]] | |
| − | + | * [[OWASP_Automated_Threats_to_Web_Applications]] | |
| − | |||
| − | * [[ | ||
| − | * [[ | ||
==Classifications== | ==Classifications== | ||
Revision as of 19:14, 28 August 2019
Project About
OWASP PyTMPyTM is an effort to enable developers to create and maintain threat models in a way that is natural for them, using a familiar OO syntax (Python, but should be generic enough to enable any developer with minimal OO experience to use it) to describe a system in terms of its elements and their attributes, in a way that can be easily shared, version-controlled and collaborated on. That description is a self-enclosed Python script that when run generates diagrams (DFDs and sequence), threats (based on a library of rules) and reports (joining diagrams and threats). DescriptionThis is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful.
LicensingA project must be licensed under a community friendly or open source license. For more information on OWASP recommended licenses, please see OWASP Licenses. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects. This example assumes that you want to use the AGPL 3.0 license. This program is free software: you can redistribute it and/or modify it under the terms of the MIT License as published by the Massachusetts Institute of Technology. OWASP PyTM and any contributions are Copyright © by the Project Leader(s). RoadmapAs of November, 2013, the highest priorities for the next 6 months are:
Subsequent Releases will add
Getting InvolvedInvolvement in the development and promotion of Tool Project Template is actively encouraged! You do not have to be a security expert or a programmer to contribute. Some of the ways you can help are as follows: |
Project ResourcesThis is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc. Project LeaderIzar Tarandach Matthew J. Coles Related ProjectsClassifications
| |||||||||||||||||||||||||||||||||||||||||||||||
