Difference between revisions of "OWASP SecurityRAT Project"

Jump to: navigation, search
m (modified docker link)
m (Updated new SecRAT version)
Line 20: Line 20:
==Current version==  
==Current version==  
Current version is 1.7.7 released in April 2018: https://github.com/SecurityRAT/SecurityRAT/releases/latest
Current version is 1.7.8 released in May 2018: https://github.com/SecurityRAT/SecurityRAT/releases/latest  
- Bug fixes
  - Fixed issue where FrontEndUniversalResource returns 404 if id > 127
- Changes
- Changes
   - More configurable constants have been added to increase flexibility
   - Front-end dependencies have been updated accordingly to newer versions
  - defaultJIRAQueueForYAML Defines the default JIRA queue used to save your requirements.
  - defaultJIRAHost: Default JIRA host used in multiple Interfaces such as create JIRA tickets or import. When defined, the user could only provide a JIRA project name or ticket key instead of the whole URL.
  - Other minor tweaks to improve the usability

Revision as of 06:55, 7 June 2019

OWASP Project Header.jpg


Tool mission: Simplify security requirement management during the SSDLC using automation approaches.


The core functionality of SecurityRAT ("Requirement Automation Tool") can be described in the following steps:

  1. You tell SecurityRAT what kind of a software artifact you're going to develop / are running
  2. SecurityRAT tells you which requirements you should fulfill.
  3. You decide how you want to handle the desired requirements.
  4. You persist the the artifact state in an issue tracker and create tickets for the requirements where an explicit action is necessary
  5. 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.

Current version

Current version is 1.7.8 released in May 2018: https://github.com/SecurityRAT/SecurityRAT/releases/latest


- Changes

 - Front-end dependencies have been updated accordingly to newer versions


This program is licensed under the Apache 2.0 license.

Project Resources

GitHub Repository

Docker Image


Slack Channel

Project Leaders

Related Projects


Project Type Files TOOL.jpg
Incubator Project Owasp-builders-small.png
Affero General Public License 3.0


Please 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!


The following volunteers take care of pushing development of SecurityRAT forwards:

  • Jay Mbolda Yamdjeu
  • Philipp Zschumme

Version in planning

For the moment, we don't anticipate development of further big features in version 1, we're putting it into maintenance mode and have 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