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"
m (Modifed docker image link) (Tag: Visual edit) |
m (modified docker link) (Tag: Visual edit) |
||
Line 91: | Line 91: | ||
==Test SecurityRAT and open issues== | ==Test SecurityRAT and open issues== | ||
− | You don't have to be a developer in order to help! Simply e.g. download our [https:// | + | You don't have to be a developer in order to help! Simply e.g. download our [https://github.com/SecurityRAT/SecurityRAT-dockercompose docker image] play around and open a [https://github.com/SecurityRAT/SecurityRAT/issues GitHub issue] for anything what doesn't work according to your expectations! |
==Create alternative requirement sets== | ==Create alternative requirement sets== |
Revision as of 11:18, 13 May 2019
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. Current versionCurrent version is 1.7.7 released in April 2018: https://github.com/SecurityRAT/SecurityRAT/releases/latest Changelog: - Bug fixes - Fixed issue where FrontEndUniversalResource returns 404 if id > 127 - Changes - More configurable constants have been added to increase flexibility - 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 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:
- 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