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 secureCodeBox"

From OWASP
Jump to: navigation, search
(Updated the project description)
 
(2 intermediate revisions by the same user 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;" |
  
−
<span style="color:#ff0000">
+
==OWASP secureCodeBox Project ==
−
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.
+
[[File:Logo secureCodeBox.png|frameless|right|Logo of the OWASP secureCodeBox Project]]
−
</span>
+
The OWASP secureCodeBox Project is a '''docker based, modularized toolchain''' for ''continuous security scans of your software project''. Its goal is to ''orchestrate'' and easily ''automate'' a bunch of ''security-testing tools'' out of the box.
−
==Project About==
+
With the secureCodeBox we provide a toolchain for continuous scanning of applications to find the low-hanging fruit issues early in the development process and free the resources of the penetration tester to concentrate on the major security issues.
−
<span style="color:#ff0000">
+
 
−
{{Template:Project_About
+
==Description==
−
  | project_name=OWASP secureCodeBox
 
−
  | leader_name1=Robert Seedorff
 
− 
−
}}
 
  
 +
The purpose of secureCodeBox is not to replace the penetration testers or make them obsolete. We strongly recommend to run extensive tests by experienced penetration testers on all your applications.
 +
For more informations about this project please have look at our [https://github.com/secureCodeBox/secureCodeBox GitHub Repo]
  
−
==OWASP Tool Project Template==
+
Our main goal is to implement a major security testing platform and framework which enables developers and teams to integrate a bunch of security testing tools in their CI/CD environment as easy as possible. The flexibility and scalability of the platform architecture leads to features like ''multi tenancy support'', ''large scale (multi-) project testing'', support of distributed and private networks, customisable security test flows,... which enables projects to test complex environments without implementing the complete security testing infrastructure on their own.  
−
<span style="color:#ff0000">
 
−
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>
 
  
−
The OWASP Tool 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.
+
Secondly we try to foster a broad range of security tools to be easily integrated. Also we will try to integrate existing OWASP Projects as building blocks in our platform.  
  
−
==Description==
+
==Roadmap==
−
<span style="color:#ff0000">
+
As of <strong>Mai, 2019, the highest priorities for the next 6 months</strong> are:
−
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. 
+
* Finalize the integration with the OWASP DefectDojo Project, as a building block for security finding analytics
−
</span>
+
* Enhance the multi tenant support
 +
* Migrate the deployment setup to Kubernetes, based on terraform for provisioning
 +
* Implement a UI for the Project based on the existing secureCodeBox API
 +
* Integrate a new REST API security scanner
  
−
The Tool Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Tool 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.
+
'''Future milestones in general are:'''
 +
* Adapt a serverless infrastructure architecture for the security scanner microservices
 +
* Migrate the process engine (Camunda) to a more lightweight technology (Zeebe.io maybe)
  
−
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 Tool Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security.
+
==Getting Involved==
 +
Contributions are welcome and extremely helpful 🙌
  
−
Contextual custom dictionary builder with character substitution and word variations for pen-testers
+
You are welcome, please join us on... 👋
 +
* [https://github.com/secureCodeBox/ GitHub]
 +
* [https://join.slack.com/t/securecodebox/shared_invite/enQtNDU3MTUyOTM0NTMwLTJiNzg3MmU2ZDY2NDFiMGI0Y2FkM2I5Mzc2ZmEzYTcyN2FlN2Y2NDFiZDE5NjAxMjg1M2IxNDViNzE3OTIxMGU Slack]
 +
* [https://twitter.com/secureCodeBox Twitter]
  
 
==Licensing==
 
==Licensing==
−
<span style="color:#ff0000">
+
This Project is free software: you can redistribute it and/or modify it under the terms of the [https://github.com/secureCodeBox/secureCodeBox/blob/master/LICENSE Apache License 2.0].
−
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.
+
OWASP secureCodeBox Project and any contributions are Copyright &copy; by {the Project Leader(s) or OWASP} {Year(s)}.   
−
</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)}. 
+
==Project About==
−
 
 
−
==Roadmap==
 
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
−
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
+
{{Template:Project_About
−
<strong>
+
  | project_name=OWASP secureCodeBox
−
* Complete the first draft of the Tool Project Template
+
  | leader_name1=Robert Seedorff
−
* Get other people to review the Tool Project Template and provide feedback
+
  | leader_email1=robert.seedorff@owasp.org
−
* Incorporate feedback into changes in the Tool Project Template
+
}}
−
* Finalize the Tool Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
 
−
</strong>
 
−
 
 
−
Subsequent Releases will add
 
−
<strong>
 
−
* Internationalization Support
 
−
* Additional Unit Tests
 
−
* Automated Regression tests
 
−
</strong>
 
−
 
 
−
==Getting Involved==
 
−
<span style="color:#ff0000">
 
−
Involvement in the development and promotion of <strong>Tool Project Template</strong> 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:
 
  
 
| 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/SamanthaGroves Installation Package]
+
[https://github.com/secureCodeBox GitHub Project]
  
−
[https://github.com/SamanthaGroves Source Code]
+
[https://securecodebox.github.io/secureCodeBox/ Documentation]
  
−
[https://github.com/SamanthaGroves What's New (Revision History)]
+
[https://github.com/secureCodeBox/secureCodeBox/issues Issue Tracker]
  
−
[https://github.com/SamanthaGroves Documentation]
+
[https://www.secureCodeBox.io Website]
  
−
[https://github.com/SamanthaGroves Wiki Home Page]
+
[https://join.slack.com/t/securecodebox/shared_invite/enQtNDU3MTUyOTM0NTMwLTJiNzg3MmU2ZDY2NDFiMGI0Y2FkM2I5Mzc2ZmEzYTcyN2FlN2Y2NDFiZDE5NjAxMjg1M2IxNDViNzE3OTIxMGU Slack]
  
−
[https://github.com/SamanthaGroves Issue Tracker]
+
[https://twitter.com/secureCodeBox Twitter]
  
−
[https://github.com/SamanthaGroves Slide Presentation]
 
−
 
−
[https://github.com/SamanthaGroves Video]
 
  
 
== Project Leader ==
 
== Project Leader ==
−
<span style="color:#ff0000">
+
Leader:
−
A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.
+
* [[User:Rseedorff|Robert Seedorff]]
−
</span>
+
Maintainer:
 +
* [[User:J12934|Jannik Hollenbach]]
 +
Contributer:
 +
* [[User:Timo Pagel|Timo Pagel]]
 +
* [[User:Benjamin Pfänder|Benjamin Pfänder]]
  
−
Robert Seedorff
+
== Integrated Projects ==
 +
* [[OWASP Juice Shop Project|OWASP JuiceShop Project]]
 +
* [[OWASP Zed Attack Proxy Project]]
 +
* [[OWASP DefectDojo Project]]
  
 
== Related Projects ==
 
== Related Projects ==
−
<span style="color:#ff0000">
+
* [[OWASP DevSlop Project|OWASP DevSlop Project]]
−
This is where you can link to other OWASP Projects that are similar to yours.
+
* [[OWASP Glue Tool Project]]
−
</span>
 
−
* [[OWASP_Code_Project_Template]]
 
−
* [[OWASP_Documentation_Project_Template]]
 
  
 
==Classifications==
 
==Classifications==

Latest revision as of 10:03, 19 May 2019

OWASP Project Header.jpg

OWASP secureCodeBox Project

Logo of the OWASP secureCodeBox Project

The OWASP secureCodeBox Project is a docker based, modularized toolchain for continuous security scans of your software project. Its goal is to orchestrate and easily automate a bunch of security-testing tools out of the box. With the secureCodeBox we provide a toolchain for continuous scanning of applications to find the low-hanging fruit issues early in the development process and free the resources of the penetration tester to concentrate on the major security issues.

Description

The purpose of secureCodeBox is not to replace the penetration testers or make them obsolete. We strongly recommend to run extensive tests by experienced penetration testers on all your applications. For more informations about this project please have look at our GitHub Repo

Our main goal is to implement a major security testing platform and framework which enables developers and teams to integrate a bunch of security testing tools in their CI/CD environment as easy as possible. The flexibility and scalability of the platform architecture leads to features like multi tenancy support, large scale (multi-) project testing, support of distributed and private networks, customisable security test flows,... which enables projects to test complex environments without implementing the complete security testing infrastructure on their own.

Secondly we try to foster a broad range of security tools to be easily integrated. Also we will try to integrate existing OWASP Projects as building blocks in our platform.

Roadmap

As of Mai, 2019, the highest priorities for the next 6 months are:

  • Finalize the integration with the OWASP DefectDojo Project, as a building block for security finding analytics
  • Enhance the multi tenant support
  • Migrate the deployment setup to Kubernetes, based on terraform for provisioning
  • Implement a UI for the Project based on the existing secureCodeBox API
  • Integrate a new REST API security scanner

Future milestones in general are:

  • Adapt a serverless infrastructure architecture for the security scanner microservices
  • Migrate the process engine (Camunda) to a more lightweight technology (Zeebe.io maybe)

Getting Involved

Contributions are welcome and extremely helpful 🙌

You are welcome, please join us on... 👋

Licensing

This Project is free software: you can redistribute it and/or modify it under the terms of the Apache License 2.0. OWASP secureCodeBox Project and any contributions are Copyright © by {the Project Leader(s) or OWASP} {Year(s)}.

Project About

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


other releases

Project Resources

GitHub Project

Documentation

Issue Tracker

Website

Slack

Twitter


Project Leader

Leader:

Maintainer:

Contributer:

Integrated Projects

Related Projects

Classifications

Project Type Files TOOL.jpg
Incubator Project Owasp-builders-small.png
Owasp-breakers-small.png
Apache License 2.0

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_secureCodeBox&oldid=251735"