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 Security Ninja Program Project"
From OWASP
(Created page with "=Main= <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</...") |
|||
(5 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | Please see new project name corrected on https://www.owasp.org/index.php/OWASP_Security_Ninja_Project | ||
+ | |||
+ | |||
+ | |||
+ | |||
=Main= | =Main= | ||
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | ||
Line 6: | Line 11: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | ||
+ | |||
+ | TEMPORARY NOTE: There is an existing project called the OWASP Security Ninjas Training Program, sponsored by OpenDNS. The project is a single module with labs training class. They used the Ninja metaphor, but not as the backdrop and marketing focus we would do with this new project. I am requesting that the existing Security Ninjas Training modify or relinquish their name. | ||
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | ||
Line 37: | Line 44: | ||
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | ||
<span style="color:#ff0000"> | <span style="color:#ff0000"> | ||
+ | |||
+ | The OWASP Security Ninja Program exists to educate, empower, and recognize developers and testers in the field of web application security. Security belts measure domain specific knowledge and application, ranging from white to black belt. | ||
+ | |||
This section must include a shorter description of what the project is, why the project was started, and what security issue is being helped by the project deliverable. This description will be used to promote the project so make sure the description represents your project in the best way possible. | This section must include a shorter description of what the project is, why the project was started, and what security issue is being helped by the project deliverable. This description will be used to promote the project so make sure the description represents your project in the best way possible. | ||
</span> | </span> | ||
Line 50: | Line 60: | ||
==Licensing== | ==Licensing== | ||
+ | Creative Commons Attribution ShareAlike 3.0 License | ||
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | ||
Line 70: | Line 81: | ||
Here you should add a short description of what your project actually does. What is the primary goal of your project, and why is it important? | Here you should add a short description of what your project actually does. What is the primary goal of your project, and why is it important? | ||
</span> | </span> | ||
+ | The tangible deliverables are broken down into two categories: content and infrastructure. Content refers to any artifacts that contain specific learning. Infrastructure is any of the systems required to deliver the training to the learner. | ||
+ | |||
+ | On the content side, the deliverables are individual training module videos, assessments, and any associated slides or documentation that assist the learner in understanding the topic (and are used in the training video). Other deliverables may include virtual machines or lab based exercises available for download. | ||
+ | |||
+ | On the infrastructure side, front end interfaces, web servers, databases, storage, and a learning management system are required to deliver the training content to the Internet community. A front end interface and a custom piece of middleware are the main code based deliverables. A discussion will take place with the core team in the future to determine if any of the infrastructure is required, or if the content itself will be released. | ||
The end goal is to identify, cite, and document the fundamental principles of information security. Once this is well organised, I think it would be great to publish this through the [http://scriptogr.am/dennis-groves/post/owasp-press OWASP Press]. Of course, it will always remain freely available, and any money collected will go directly into the project to absorb costs with any remaining funds going to the OWASP Foundation. | The end goal is to identify, cite, and document the fundamental principles of information security. Once this is well organised, I think it would be great to publish this through the [http://scriptogr.am/dennis-groves/post/owasp-press OWASP Press]. Of course, it will always remain freely available, and any money collected will go directly into the project to absorb costs with any remaining funds going to the OWASP Foundation. | ||
Line 202: | Line 218: | ||
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | ||
<span style="color:#ff0000"> | <span style="color:#ff0000"> | ||
+ | The OWASP Security Ninja program is a multi-phase undertaking. The OWASP White and Yellow Belts require the creation of a series of video based training modules. The Green, Brown, and Black belts require the creation of an activity submission process, including a tracking and review component. | ||
+ | |||
+ | The high level content creation process per module consists of: | ||
+ | - outline of topic | ||
+ | - review of outline | ||
+ | - draft content | ||
+ | - technical review | ||
+ | - instructional design review | ||
+ | - final content | ||
+ | - generate assessment | ||
+ | |||
+ | Multiple modules can be processed in parallel, presuming that multiple community resources are available to assist with content creation and review. | ||
+ | |||
+ | Major Milestones | ||
+ | |||
+ | Identify Project Vision & Strategy (November 2015 - January 2016) | ||
+ | |||
+ | - Scope and Governance (January 2016) | ||
+ | - Initial project summit (January 2016) | ||
+ | |||
+ | OWASP White Belt (maximum of 8 modules) (January 2016 - September 2016) | ||
+ | |||
+ | - Content creation (January - March 2016) | ||
+ | - Content recording (March 2016) | ||
+ | - Infrastructure code and build (January - September 2016) | ||
+ | - Alpha (July 2016) | ||
+ | - Second project summit @ AppSec EU (July 2016) | ||
+ | - Beta (August 2016) | ||
+ | - Launch of content at AppSec USA (September 2016) | ||
+ | |||
+ | OWASP Yellow Belt (maximum of 32 modules: 16 core, 8 dev, 8 test) (October 2016 - September 2017) | ||
+ | |||
+ | - Content creation (October 2016 - March 2017) | ||
+ | - Content recording (April 2017) | ||
+ | - Infrastructure update (January - September 2017) | ||
+ | - Alpha (July 2017) | ||
+ | - Beta (August 2017) | ||
+ | - Launch of content at AppSec USA (September 2017) | ||
+ | |||
+ | OWASP Green Belt, OWASP Brown Belt, OWASP Black Belt (October 2017 - September 2018) | ||
+ | |||
+ | - Infrastructure update (January - July 2018) | ||
+ | - Finalize governance and oversight (January - March 2018) | ||
+ | - Alpha (July 2018) | ||
+ | - Beta (August 2018) | ||
+ | - Launch of concept and completion of initial scope (September 2018) | ||
+ | |||
+ | Then the cycle begins again, with a refresh of OWASP White Belt. | ||
+ | |||
A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership. | A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership. | ||
</span> | </span> |
Latest revision as of 22:34, 4 November 2015
Please see new project name corrected on https://www.owasp.org/index.php/OWASP_Security_Ninja_Project