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

From OWASP
Jump to: navigation, search
(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=</...")
 
(OWASP Security Ninja)
 
(63 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
=Main=
 
=Main=
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
+
<div style="width:100%;height:90px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
 
 
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
 
{| 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.
+
==OWASP Security Ninja ==
 
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<span style="color:#ff0000">
 
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.
 
</span>
 
 
 
==The OWASP Security Principles==
 
 
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<span style="color:#ff0000">
 
This is where you need to add your more robust project description. A project description should outline the purpose of the project, 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, and project leaders should ensure that the description is meaningful.
 
</span>
 
 
 
Inevitably applications are designed with security principles architects knew about, security folks included. However, as this project demonstrates there are far more than just a 'few' principles, most of which never make it into the design.
 
 
 
For example, security design happens with perhaps a handful of principles:
 
 
 
* Least Privilege
 
* Perimeter Security
 
* Defence in Depth
 
 
 
However, we regularly see designs without '''separation of privilege'''!
 
 
 
Think about that, most web applications today have all their eggs in a single basket. The business logic, the identities, passwords, products, policy enforcement, security rules are all found in the same application database that makes up the typical website! It is little wonder then, that attacks on the database have been so completely devastating, since there is no separation of privilege!
 
 
 
The aim of this project, is to identify and describe a minimum functional set of principles that must be present in a secure design.
 
 
 
==Description==
 
 
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<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.
 
</span>
 
 
 
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]
 
'''
 
 
 
Over the course of my career, I have come across and collected a number of security ''aphorisms.'' These aphorisms constitute the fundamental principles of information security.
 
 
 
None of the ideas or truths are mine, and unfortunately, I did not collect the citations. Initially, I would like to identify the correct citations for each aphorism.
 
 
 
Additionally, many are re-statements of the same idea; thus, the 'collection of ideas' defines a fundamental principle. As such, I would also like to reverse engineer the principles from the aphorisms where appropriate, as well.
 
 
 
==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.-->
 
<span style="color:#ff0000">
 
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.
 
</span>
 
  
'''The OWASP Security Principles are free to use. In fact it is encouraged!!!
+
The world of application security has a gaping hole when it comes to interesting and engaging security learning. Builders, breakers, and defenders lack a solid foundation of application security knowledge and an appreciation for the evolving threat landscape. These same folks also lack experience with secure development practices and tools. Finally, they lack the motivation to volunteer to improve application security.
'' Additionally, I also encourage you to contribute back to the project. I have no monopoly on this knowledge; however, we all have pieces of this knowledge from our experience. Let's begin by putting our individual pieces together to make something great. Great things happen when people work together.
 
  
The OWASP Security Principles are licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
+
Enter the OWASP Security Ninja program, a content and action based application security learning adventure using the latest advancements in the world of gamification to enhance the learner experience and keep them coming back. The project recognizes the learning and activity achievements of OWASP application security practitioners using a system of security belts. The OWASP security belts are white, yellow, green, brown, and black. Similar to belts in the world of martial arts, a student in our "virtual dojo" must train and test to earn a belt.  
 +
* '''White Belt''' -- The journey begins with the student reviewing video learning modules and taking an assessment per module. When the learner achieves passing status on all the white belt modules, they earn the OWASP Security White Belt and are eligible to continue to Yellow Belt.
 +
* '''Yellow Belt''' -- The yellow belt focuses on applying the security knowledge, and splits the content into builder and breaker specific roles, each with a separate set of learning modules to be completed.
 +
* '''Green, Brown, Black Belts''' -- After yellow, the student must put their new found knowledge into action by completing activities that improve some facet of application security. For each activity, the student earns points towards the next belt in the series (green, brown, and black). OWASP Security Black belt is the highest honor, and signifies that the student has become the teacher, and has taken a leadership stake in learning and doing application security.
  
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
+
==Mission==
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
+
OWASP Security Ninja '''educates, empowers, reaches, and recognizes''' builders and breakers in web application security.
  
== What is OWASP Security Principles Project? ==
+
* Educates — providing the content to expand the application security knowledge of both the OWASP faithful and academia / industry
 +
* Empowers — opens doors and minds to new facets of application security
 +
* Reaches — connects with those who have had no historical appreciation or understanding of security
 +
* Recognizes — provides recognition for those that expand their minds and put forth effort to improve application security
  
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
==Delivery==
<span style="color:#ff0000">
 
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>
 
 
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.
 
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 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.
 
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.
+
==Licensing==
 +
OWASP Security Ninja is free to use. Its licensing is dependent on several factors:
 +
* OWASP Security Ninja created documentation is licensed under the [https://creativecommons.org/licenses/by/4.0 Creative Commons Attribution 4.0 license], so you can distribute, remix, tweak, and build upon our work, even commercially, as long as you credit us for the original creation.  
 +
* OWASP Security Ninja created software and tools are licensed under the [http://www.gnu.org/copyleft/gpl.html GPLv3] or later license. You are free to use and modify this software as well as having the right to re-distribute this software as long as any changes you've made are contributed back to the project under the same license.  For questions, see the [http://www.gnu.org/licenses/gpl-faq.html GPL FAQ]
 +
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
  
This document should serve as a guide to technical architects and designers outlining the fundamental principles of security.
+
== Logo ==
 +
[[File:New-ninja-base-stand-black.png|200px]]
  
 
== Presentation ==
 
== Presentation ==
  
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
Coming Soon.
<span style="color:#ff0000">
 
This is where you can link to slide presentations related to your project.
 
</span>
 
 
 
 
 
AppSec USA 2013 [https://github.com/OWASP/Security-Principles/tree/master/Presentations/AppSec%20NYC%202013]
 
  
 
== Project Leader ==
 
== Project Leader ==
  
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* [https://www.owasp.org/index.php/User:edgeroute Chris Romeo]
<span style="color:#ff0000">
 
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.
 
</span>
 
 
 
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
 
 
 
  
 
== Related Projects ==
 
== Related Projects ==
  
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* [[https://owasp.org/index.php/Category:OWASP_Education_Project OWASP Education Project]]
<span style="color:#ff0000">
 
This is where you can link to other OWASP Projects that are similar to yours.
 
</span>
 
 
 
* [[OWASP_CISO_Survey]]
 
 
 
== Openhub ==
 
 
 
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]
 
 
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
| valign="top"  style="padding-left:25px;width:200px;" |
 
 
 
== Quick Download ==
 
 
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<span style="color:#ff0000">
 
This is where you can link to your repository.
 
</span>
 
  
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.
+
== Code Repository ==
  
However, if you like you may also download the master repository from the following links:
+
The OWASP Security Ninja code will be stored on GitHub shortly.
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]
 
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]
 
  
 
== News and Events ==
 
== News and Events ==
 
+
* [2015-12-06] Project site kicked off, and search for volunteers begins.
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<span style="color:#ff0000">
 
This is where you can link to press your project has been a part of. Appropriate press includes: Project Leader interviews, articles written about your project, and videos about your project.
 
</span>
 
 
 
* [20 Nov 2013] News 2
 
* [30 Sep 2013] News 1
 
 
 
== In Print ==
 
 
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<span style="color:#ff0000">
 
This is where you place links to where your project product can be downloaded or purchased, in the case of a book.
 
</span>
 
 
 
This project can be purchased as a print on demand book from Lulu.com
 
  
 
==Classifications==
 
==Classifications==
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<span style="color:#ff0000">
 
Here is where you can let the community know what project stage your project is currently in, whether the project is a builder, breaker, or defender project, and what type of project you are running.
 
</span>
 
  
 
   {| width="200" cellpadding="2"
 
   {| width="200" cellpadding="2"
Line 166: Line 62:
 
   | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]   
 
   | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]   
 
   |-
 
   |-
   | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
+
   | align="center" valign="top" width="50%"| [[File:Owasp-breakers-small.png|link=]]
  |-
 
  | colspan="2" align="center"  | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
 
  |-
 
  | colspan="2" align="center"  | [[File:Project_Type_Files_DOC.jpg|link=]] 
 
 
   |}
 
   |}
  
 
|}
 
|}
  
=FAQs=
+
= Road Map =
 
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<span style="color:#ff0000">
 
Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'
 
</span>
 
  
 +
The OWASP Security Ninja program is a multi-phase, multi-year undertaking. The OWASP White and Yellow Belts require the creation of a series of video based learning modules. The Green, Brown, and Black belts require the creation of an activity submission process, including a tracking and review component.
 +
== Phases ==
 +
=== Identify Project Vision & Strategy (November 2015 - January 2016) ===
 +
In this phase, a core group of volunteers must come together to help in defining the OWASP Security Ninja program. While Chris Romeo as the project leader has many ideas and plans, the idea is for the core group of participants with broad knowledge of OWASP to help scope the content to be developed.
 +
* Scope and Governance (January 2016)
 +
* Initial project summit (January 2016)
  
==How can I participate in your project?==
+
=== OWASP White Belt (January 2016 - September 2016) ===
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.
+
During the creation of the content for white belt, the official content creation process will be finalized.
 +
* Content creation (January - March 2016)
 +
* Content recording (March 2016)
 +
* Infrastructure code and build (January - September 2016)
 +
A user interface and set of web services must be developed to support the delivery of OWASP Security Ninja.
 +
* Alpha (July 2016)
 +
Alpha is opening up the content and systems to a select group of testers.
 +
* Second project summit @ AppSec EU (July 2016)
 +
* Beta (August 2016)
 +
Beta is a wider group of testers pushing the system to it's limits.
 +
* Launch of content at AppSec USA (September 2016)
 +
OWASP Security White Belt available to the world!
  
==If I am not a programmer can I participate in your project?==
+
=== OWASP Yellow Belt (October 2016 - September 2017) ===
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.  
+
* 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)
 +
Additional front end and web services will be developed to track the activity submissions of the participants.
 +
* Finalize governance and oversight (January - March 2018)
 +
The processes and procedures for judging and tracking activities must be finalized.
 +
* Alpha (July 2018)
 +
* Beta (August 2018)
 +
* Launch of concept and completion of initial scope (September 2018)
 +
===Content Refresh===
 +
The challenge with security learning modules is that they become stale after roughly one year of release. The content refresh process ensures that once per year content is reviewed and select pieces of content are updated. At the conclusion of the green, brown, and black belt deployment, the project will begin an aggressive content refresh process.
  
= Acknowledgements =
+
= White Belt =
 +
[[File:White-belt.png|200px]]
 +
==Objective==
 +
Familiarity with basic security fundamentals and basic knowledge of Secure Development Lifecycle
 +
==Keyword==
 +
Learning
 +
==Module List==
 +
In development now.
  
==Contributors==
+
= Yellow Belt =
 +
[[File:Yellow-belt.png|200px]]
 +
==Learning Objective==
 +
Application of knowledge tailored to a specific role (builder and breaker)
 +
==Keyword==
 +
Applying
 +
==Module List==
 +
In development now.
  
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
= Green, Brown, Black Belt =
<span style="color:#ff0000">
+
[[File:Green-belt.png|200px]]
The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project.
+
[[File:Brown-belt.png|200px]]
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project.
+
[[File:Black-belt.png|200px]]
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
+
==Learning Objective==
</span>
+
Putting the learning lessons to work by contributing to the betterment of application security through activities
 +
==Keyword==
 +
Doing, Leading, Leader
 +
==Activty List==
 +
In development now.
  
The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project  [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].
+
=FAQs=
  
The first contributors to the project were:
+
==What is the problem statement that this project is trying to solve?==
 +
Builders, breakers, and defenders lack:
 +
* general application security knowledge
 +
* appreciation for the evolving threat landscape
 +
* experience with secure development practices and tools
 +
* motivation to volunteer to improve security
  
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
+
==What is the mission of this project?==
* [https://github.com/sublimino Andrew Martin]
+
OWASP Security Ninja educates, empowers, reaches, and recognizes builders, breakers, and defenders in web application security.
* [https://github.com/Lambdanaut Josh Thomas]
 
* '''YOUR NAME BELONGS HERE'''
 
  
= Road Map and Getting Involved =
+
==Who is the target consumer for this project?==
 +
The target audience begins with the OWASP faithful, the builders and breakers  that are already part of the OWASP community. Our secondary audiences  are educators / students and industry. We see the real benefit for this program in reaching builders and breakers in industry and the next generation studying now.
  
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
==What is different about the learning created in this project versus regular security learning?==
<span style="color:#ff0000">
+
Face it, regular security learning training is boring. Voice over powerpoint is painful to listen to. Someone reading off a script in front of a camera is as interesting as watching paint dry. We do learning modules differently. We bake in fun to the process of how we record. Think of our modules as more of a late night talk show talking security then boring script readers. We use a laid back conversational style to deal with complex topics, ask lots of questions, and share our personal experiences within the content.
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:
+
==What roles / specializations are needed for this project?==
- outline of topic
+
We need folks who can perform any or many of the following roles:
- review of outline
+
# Security learning module content creator (security subject matter expert)
- draft content
+
# Content reviewer
- technical review
+
# Web interface / full stack developer
- instructional design review
+
# Database developer
- final content
+
# AWS setup and administration
- generate assessment
+
# Graphic designer
 +
# Psychometrician -- fancy name for someone who writes fair test questions
  
Multiple modules can be processed in parallel, presuming that multiple community resources are available to assist with content creation and review.
+
==Is this thing a certification?==
 +
At this stage, the plan is no. A certification program requires a more formal, rigid testing and evaluation process than we plan to build. We will revisit this as the project develops.
  
Major Milestones
+
= Acknowledgements =
  
Identify Project Vision & Strategy (November 2015 - January 2016)
+
==Contributors==
 
 
- 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.
 
</span> 
 
  
<span style="color:#ff0000">
+
The OWASP Security Ninja project is in need of some additional people to list on this site!
Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.
 
</span>
 
  
As of October 2013, the priorities are:
+
The first contributors to the project are:
* Finish the referencing for each principle.
 
* Update the Project Template.
 
* Use the OWASP Press to develop a book.
 
* Finish and publish the book on Lulu.
 
  
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!
+
* [https://www.owasp.org/index.php/User:edgeroute Chris Romeo]
You do not have to be a security expert in order to contribute.
 
Some of the ways you can help:
 
* Helping find references to some of the principles.
 
* Project administration support.  
 
* Wiki editing support.
 
* Writing support for the book.  
 
  
 
=Project About=
 
=Project About=
  
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
{{Template:Project About
<span style="color:#ff0000">
+
| project_name =OWASP Security Ninja
This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager.
+
| project_description = OWASP Security Ninja educates, empowers, reaches, and recognizes builders, breakers, and defenders in web application security using a system of learning modules and practical experience
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
+
| project_license =CC-BY 3.0 for documentation and GPLv3 for code
</span>
+
| leader_name1 =Chris Romeo
 
+
| leader_email1 [email protected].us
{{:Projects/OWASP_Example_Project_About_Page}}  
+
| leader_username1 = edgeroute
 +
}}
  
  
Line 297: Line 193:
 
__NOTOC__ <headertabs />  
 
__NOTOC__ <headertabs />  
  
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]
+
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Breakers]]

Latest revision as of 01:10, 7 December 2015

OWASP Project Header.jpg

OWASP Security Ninja

The world of application security has a gaping hole when it comes to interesting and engaging security learning. Builders, breakers, and defenders lack a solid foundation of application security knowledge and an appreciation for the evolving threat landscape. These same folks also lack experience with secure development practices and tools. Finally, they lack the motivation to volunteer to improve application security.

Enter the OWASP Security Ninja program, a content and action based application security learning adventure using the latest advancements in the world of gamification to enhance the learner experience and keep them coming back. The project recognizes the learning and activity achievements of OWASP application security practitioners using a system of security belts. The OWASP security belts are white, yellow, green, brown, and black. Similar to belts in the world of martial arts, a student in our "virtual dojo" must train and test to earn a belt.

  • White Belt -- The journey begins with the student reviewing video learning modules and taking an assessment per module. When the learner achieves passing status on all the white belt modules, they earn the OWASP Security White Belt and are eligible to continue to Yellow Belt.
  • Yellow Belt -- The yellow belt focuses on applying the security knowledge, and splits the content into builder and breaker specific roles, each with a separate set of learning modules to be completed.
  • Green, Brown, Black Belts -- After yellow, the student must put their new found knowledge into action by completing activities that improve some facet of application security. For each activity, the student earns points towards the next belt in the series (green, brown, and black). OWASP Security Black belt is the highest honor, and signifies that the student has become the teacher, and has taken a leadership stake in learning and doing application security.

Mission

OWASP Security Ninja educates, empowers, reaches, and recognizes builders and breakers in web application security.

  • Educates — providing the content to expand the application security knowledge of both the OWASP faithful and academia / industry
  • Empowers — opens doors and minds to new facets of application security
  • Reaches — connects with those who have had no historical appreciation or understanding of security
  • Recognizes — provides recognition for those that expand their minds and put forth effort to improve application security

Delivery

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.

Licensing

OWASP Security Ninja is free to use. Its licensing is dependent on several factors:

  • OWASP Security Ninja created documentation is licensed under the Creative Commons Attribution 4.0 license, so you can distribute, remix, tweak, and build upon our work, even commercially, as long as you credit us for the original creation.
  • OWASP Security Ninja created software and tools are licensed under the GPLv3 or later license. You are free to use and modify this software as well as having the right to re-distribute this software as long as any changes you've made are contributed back to the project under the same license. For questions, see the GPL FAQ

New-ninja-base-stand-black.png

Presentation

Coming Soon.

Project Leader

Related Projects

Code Repository

The OWASP Security Ninja code will be stored on GitHub shortly.

News and Events

  • [2015-12-06] Project site kicked off, and search for volunteers begins.

Classifications

New projects.png Owasp-builders-small.png
Owasp-breakers-small.png

The OWASP Security Ninja program is a multi-phase, multi-year undertaking. The OWASP White and Yellow Belts require the creation of a series of video based learning modules. The Green, Brown, and Black belts require the creation of an activity submission process, including a tracking and review component.

Phases

Identify Project Vision & Strategy (November 2015 - January 2016)

In this phase, a core group of volunteers must come together to help in defining the OWASP Security Ninja program. While Chris Romeo as the project leader has many ideas and plans, the idea is for the core group of participants with broad knowledge of OWASP to help scope the content to be developed.

  • Scope and Governance (January 2016)
  • Initial project summit (January 2016)

OWASP White Belt (January 2016 - September 2016)

During the creation of the content for white belt, the official content creation process will be finalized.

  • Content creation (January - March 2016)
  • Content recording (March 2016)
  • Infrastructure code and build (January - September 2016)

A user interface and set of web services must be developed to support the delivery of OWASP Security Ninja.

  • Alpha (July 2016)

Alpha is opening up the content and systems to a select group of testers.

  • Second project summit @ AppSec EU (July 2016)
  • Beta (August 2016)

Beta is a wider group of testers pushing the system to it's limits.

  • Launch of content at AppSec USA (September 2016)

OWASP Security White Belt available to the world!

OWASP Yellow Belt (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)

Additional front end and web services will be developed to track the activity submissions of the participants.

  • Finalize governance and oversight (January - March 2018)

The processes and procedures for judging and tracking activities must be finalized.

  • Alpha (July 2018)
  • Beta (August 2018)
  • Launch of concept and completion of initial scope (September 2018)

Content Refresh

The challenge with security learning modules is that they become stale after roughly one year of release. The content refresh process ensures that once per year content is reviewed and select pieces of content are updated. At the conclusion of the green, brown, and black belt deployment, the project will begin an aggressive content refresh process.

White-belt.png

Objective

Familiarity with basic security fundamentals and basic knowledge of Secure Development Lifecycle

Keyword

Learning

Module List

In development now.

Yellow-belt.png

Learning Objective

Application of knowledge tailored to a specific role (builder and breaker)

Keyword

Applying

Module List

In development now.

Green-belt.png Brown-belt.png Black-belt.png

Learning Objective

Putting the learning lessons to work by contributing to the betterment of application security through activities

Keyword

Doing, Leading, Leader

Activty List

In development now.

What is the problem statement that this project is trying to solve?

Builders, breakers, and defenders lack:

  • general application security knowledge
  • appreciation for the evolving threat landscape
  • experience with secure development practices and tools
  • motivation to volunteer to improve security

What is the mission of this project?

OWASP Security Ninja educates, empowers, reaches, and recognizes builders, breakers, and defenders in web application security.

Who is the target consumer for this project?

The target audience begins with the OWASP faithful, the builders and breakers that are already part of the OWASP community. Our secondary audiences are educators / students and industry. We see the real benefit for this program in reaching builders and breakers in industry and the next generation studying now.

What is different about the learning created in this project versus regular security learning?

Face it, regular security learning training is boring. Voice over powerpoint is painful to listen to. Someone reading off a script in front of a camera is as interesting as watching paint dry. We do learning modules differently. We bake in fun to the process of how we record. Think of our modules as more of a late night talk show talking security then boring script readers. We use a laid back conversational style to deal with complex topics, ask lots of questions, and share our personal experiences within the content.

What roles / specializations are needed for this project?

We need folks who can perform any or many of the following roles:

  1. Security learning module content creator (security subject matter expert)
  2. Content reviewer
  3. Web interface / full stack developer
  4. Database developer
  5. AWS setup and administration
  6. Graphic designer
  7. Psychometrician -- fancy name for someone who writes fair test questions

Is this thing a certification?

At this stage, the plan is no. A certification program requires a more formal, rigid testing and evaluation process than we plan to build. We will revisit this as the project develops.

Contributors

The OWASP Security Ninja project is in need of some additional people to list on this site!

The first contributors to the project are:

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 Security Ninja
Purpose: OWASP Security Ninja educates, empowers, reaches, and recognizes builders, breakers, and defenders in web application security using a system of learning modules and practical experience
License: CC-BY 3.0 for documentation and GPLv3 for code
who is working on this project?
Project Leader(s):
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
current release
Not Yet Published
last reviewed release
Not Yet Reviewed


other releases