Difference between revisions of "OWASP Security Ninja Project"
(→Green, Brown, Black Belt)
|Line 91:||Line 91:|
= White Belt =
= White Belt =
= Yellow Belt =
= Yellow Belt =
Revision as of 00:35, 7 December 2015
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. 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" begins their journey 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.
OWASP Security Ninja educates, empowers, reaches, and recognizes builders and breakers in web application security.
OWASP Security Ninja is free to use. Its licensing is dependent on several factors:
The OWASP Security Ninja code will be stored on GitHub shortly.
News and Events
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.
Identify Project Vision & Strategy (November 2015 - January 2016)
- Scope and Governance (January 2016)
- Initial project summit (January 2016)
OWASP White Belt (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 (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.
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:
- Security learning module content creator (security subject matter expert)
- Content reviewer
- Web interface / full stack developer
- Database developer
- AWS setup and administration
- Graphic designer
- 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.
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?