OWASP SecurityRAT Project

• Main
• Acknowledgements
• Road Map
• Project About

OWASP SecurityRAT Tool mission: Simplify security requirement management during the SSDLC using automation approaches. Description The core functionality of SecurityRAT ("Requirement Automation Tool") can be described in the following steps: You tell SecurityRAT what kind of a software artifact you're going to develop / are running SecurityRAT tells you which requirements you should fulfill. You decide how you want to handle the desired requirements. You persist the the artifact state in an issue tracker and create tickets for the requirements where an explicit action is necessary Throughout the continuous development of the particular artifact, you respect the rules defined in SecurityRAT and document relevant changes in requirement compliance whenever appropriate. 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. Licensing This program is licensed under the Apache 2.0 license.

Project Resources GitHub Repository Docker Image Documentation Project Leaders Daniel Kefer René Reuter Related Projects OWASP Security Knowledge Framework Classifications

Releases Please see our GitHub Releases page for the information about the most current release! SecurityRAT on Tour [22 May 2017] Karlsruher Entwicklertag. [21 Mar 2017] OWASP Stammtisch München. [29 Nov 2016] German OWASP Day 2016. [25 Nov 2016] BeNeLux OWASP Day 2016-2 [22 Sep 2016] Netherlands Chapter Meeting [30 Jun 2016] OWASP AppSec EU [13 Jun 2016] OWASP Stammtisch Karlsruhe

Get Involved

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 the idea, 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 Current version: 1.0.2

Addtional Instructions for making changes:

The About 'tab' on that page is done with a MediaWiki template. If you log into the wiki page for your project and click the "Edit" button/link/tab in the top-right between 'Read' and 'View History', you'll see the edit page for the main body of your project page.

If you scroll down below the form to edit that page (below the "Save page", "Show preview", "Show changes" buttons, you'll see some text with a triangle in front of it reading "Templates used on this page:" A list will expand if you click on the triangle/text to show the templates that make up this page. The one you want is the "Projects/OWASP Example Project About Page" - click the (edit) next to this to edit that template. The direct link is: https://www.owasp.org/index.php?title=Projects/OWASP_Example_Project_About_Page&action=edit

The template takes 'input' that are key/value pairs where you'll need to edit the stuff after the equals (=) like: project_name =Place your project name here.

You'd edit the bold bit.

This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager. Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project

PROJECT INFO What does this OWASP project offer you?	RELEASE(S) INFO What releases are available for this project?
what is this project? Name: N/A Purpose: N/A License: N/A who is working on this project? Project Leader(s): N/A how can you learn more? Project Pamphlet: Not Yet Created Project Presentation: Mailing list: N/A Project Roadmap: Not Yet Created Key Contacts Contact the GPC to contribute to this project Contact the GPC to review or sponsor this project	current release pending last reviewed release pending other releases