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 SecurityRAT Project"
| Line 34: | Line 34: | ||
== Project Leaders == | == Project Leaders == | ||
* [https://www.owasp.org/index.php/User:Dkefer Daniel Kefer] | * [https://www.owasp.org/index.php/User:Dkefer Daniel Kefer] | ||
| − | * René Reuter | + | * [https://www.owasp.org/index.php/User:Ares René Reuter] |
== Related Projects == | == Related Projects == | ||
| Line 89: | Line 89: | ||
* [https://www.owasp.org/index.php/User:Dkefer Daniel Kefer] | * [https://www.owasp.org/index.php/User:Dkefer Daniel Kefer] | ||
| − | * René Reuter | + | * [https://www.owasp.org/index.php/User:Ares René Reuter] |
* Jay Mbolda Yamdjeu | * Jay Mbolda Yamdjeu | ||
Revision as of 14:42, 27 June 2017
OWASP SecurityRATTool mission: Simplify security requirement management during the SSDLC using automation approaches. DescriptionThe core functionality of SecurityRAT ("Requirement Automation Tool") can be described in the following steps:
Focus of SecurityRAT is currently put on automation of procedures rather then quality of requirements. There is a set of requirements provided which you can start with, nevertheless it is recommended to create your own set of requirements which fits your company risk profile. LicensingThis program is licensed under the Apache 2.0 license. |
Project ResourcesProject LeadersRelated ProjectsClassifications
|
ReleasesPlease see our GitHub Releases page for the information about the most current release! SecurityRAT on Tour
| |||||||
We're looking for volunteers helping us with the project. These are the possibilities to get involved:
Test SecurityRAT and open issues
You don't have to be a developer in order to help! Simply e.g. download our docker image play around and open a GitHub issue for anything what doesn't work according to your expectations!
Create alternative requirement sets
Current default requirement set is very basic and targeted on web development only.
If you want to improve that, you can create your own security requirement set in your own instance of SecurityRAT and provide it in a form of an SQL dump accordingly to the default one.
Join the development team
If you like our idea and want to make it better, know some coding (JavaScript/Angular & JAVA/Spring Boot) and have some spare time, we will be happy to receive you in the team and provide any starting support necessary!
Contributors
The following volunteers take care of pushing development of SecurityRAT forwards:
- Daniel Kefer
- René Reuter
- Jay Mbolda Yamdjeu
Current version
Current version is 1.6 (new feature being support of manual (de-)linking of existing tickets for particular requirements.
Version in preparation
We're currently working on 1.7.0, target date being September 2017.
New feature will be management of HTML5 slides serving for giving trainings relevant to the requirements
Version in planning
We've started collecting ideas for v2.0.
Please see the current list of ideas for version 2.0 and contribute your ideas on this GitHub Wiki Page
