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 "Risk Assessment Framework"

From OWASP
Jump to: navigation, search
 
(26 intermediate revisions by 2 users not shown)
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;" |
  
<s7pan style="color:#ff0000">
+
=Home=
Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.
+
The OWASP Risk Asessement Framework is SAS(Source Code Analysis) and Risk Assesment tool.
</span>
+
 
 
==Project About==
 
==Project About==
 +
https://github.com/OWASP/RiskAssessmentFramework
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
{{:Projects/OWASP_Example_Project_About_Page}}
 
  
  
==OWASP Documentation Project Template==
+
 
<span style="color:#ff0000">
+
==OWASP Risk Assessment Framework Project / RAF ==
This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.
+
<span style="color:>
 +
The OWASP Risk Asessement Framework is SAS(Source Code Analysis) and Risk Assesment tool.
 +
features<br>
 +
Web Deface Detection<br>
 +
Scanning Tools based on OWASP Top 10<br>
 +
Risk Assesment Tools<br>
 +
Static Application security Testing<br>
 
</span>
 
</span>
 
The OWASP Documentation Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.
 
  
 
==Description==
 
==Description==
<span style="color:#ff0000">
+
<span style="color:">
This 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. 
+
Introduction to Problem: <br>
</span>
+
There are hundreds of SAST tools available for a penetration tester to use from and there
 
+
are frameworks to assess the risk of a security flaw. But in the OWASP Risk Assessment to testers
The Documentation Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Documentation project.  After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red.  Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category. The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort.
+
have to manually input the the test results from each and every tool to get a relative
 
+
approximation. This makes the assessment part as a separate component from all other tools.
Creating a new set of project pages from scratch can be a challenging task. By providing a sample layout, with instructional text and examples, the OWASP Documentation Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security.
 
 
 
Contextual custom dictionary builder with character substitution and word variations for pen-testers
 
  
 
==Licensing==
 
==Licensing==
<span style="color:#ff0000">
+
<span style="color:">
 
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses 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.
 
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses 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.
 
</span>
 
</span>
  
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.  OWASP XXX and any contributions are Copyright &copy; by {the Project Leader(s) or OWASP} {Year(s)}.
+
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.  OWASP XXX and any contributions are Copyright &copy; by {the Project Leader(s) or OWASP} {Year(s)}.
  
==Roadmap==
+
=Roadmap=
<span style="color:#ff0000">
+
<span style="color:">
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
+
https://github.com/OWASP/RiskAssessmentFramework/blob/master/readme.md
<strong>
 
* Complete the first draft of the Documentation Project Template
 
* Get other people to review the Documentation Project Template and provide feedback
 
* Incorporate feedback into changes in the Documentation Project Template
 
* Finalize the Documentation Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
 
 
</strong>
 
</strong>
  
Subsequent Releases will add
+
 
<strong>
 
* Internationalization Support
 
* Additional Unit Tests
 
* Automated Regression tests
 
 
</strong>
 
</strong>
  
 
==Getting Involved==
 
==Getting Involved==
<span style="color:#ff0000">
+
<br>
Involvement in the development and promotion of <strong>Documentation Project Template</strong> is actively encouraged!
+
Involvement in the development and promotion of his project is actively encouraged!
 
You do not have to be a security expert or a programmer to contribute.
 
You do not have to be a security expert or a programmer to contribute.
 
Some of the ways you can help are as follows:
 
Some of the ways you can help are as follows:
 
+
Contact me at [email protected]
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
  
 
== Project Resources ==
 
== Project Resources ==
<span style="color:#ff0000">
 
This 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.
 
</span>
 
  
[ https://github.com/OWASP/RiskAssessmentFramework
+
[https://github.com/OWASP/RiskAssessmentFramework
Installation Package]
+
Installation Package] <br>
[https://github.com/OWASP/RiskAssessmentFramework]
+
[https://github.com/OWASP/RiskAssessmentFramework Source Code]
  
 
== Project Leader ==
 
== Project Leader ==
 
Ade Yoseman Putra
 
Ade Yoseman Putra
  
 +
Rejah Rehim
 +
==News==
 +
* [23 May 2019] Published in ToolsWatch.org, [https://www.toolswatch.org/2019/05/amazing-black-hat-arsenal-usa-2019-lineup-announced/ Amazing Black Hat Arsenal USA 2019 Lineup Announced]
 
== Related Projects ==
 
== Related Projects ==
<span style="color:#ff0000">
+
 
This is where you can link to other OWASP Projects that are similar to yours.
+
* [[OWASP Testing Guide v4 Table of Contents]]
</span>
+
* [[OWASP SonarQube Project]]
* [[OWASP_Code_Project_Template]]
 
* [[OWASP_Tool_Project_Template]]
 
  
 
==Classifications==
 
==Classifications==

Latest revision as of 03:49, 24 May 2019

OWASP Project Header.jpg

The OWASP Risk Asessement Framework is SAS(Source Code Analysis) and Risk Assesment tool.

Project About

https://github.com/OWASP/RiskAssessmentFramework


OWASP Risk Assessment Framework Project / RAF

The OWASP Risk Asessement Framework is SAS(Source Code Analysis) and Risk Assesment tool. features
Web Deface Detection
Scanning Tools based on OWASP Top 10
Risk Assesment Tools
Static Application security Testing

Description

Introduction to Problem:
There are hundreds of SAST tools available for a penetration tester to use from and there are frameworks to assess the risk of a security flaw. But in the OWASP Risk Assessment to testers have to manually input the the test results from each and every tool to get a relative approximation. This makes the assessment part as a separate component from all other tools.

Licensing

A 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 link GNU Affero General Public License 3.0 as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP XXX and any contributions are Copyright © by {the Project Leader(s) or OWASP} {Year(s)}.

https://github.com/OWASP/RiskAssessmentFramework/blob/master/readme.md </strong>


</strong>

Getting Involved


Involvement in the development and promotion of his project 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: Contact me at [email protected]

Project Resources

[https://github.com/OWASP/RiskAssessmentFramework Installation Package]
Source Code

Project Leader

Ade Yoseman Putra

Rejah Rehim

News

Related Projects

Classifications

Project Type Files DOC.jpg
Incubator Project Owasp-builders-small.png
Owasp-defenders-small.png
Creative Commons Attribution ShareAlike 3.0 License