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
(→White Belt) |
(→OWASP Security Ninja) |
||
| (11 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
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. | 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 | + | 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== | ==Mission== | ||
| Line 17: | Line 20: | ||
* Reaches — connects with those who have had no historical appreciation or understanding of 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 | * 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== | ==Licensing== | ||
| Line 63: | Line 72: | ||
== Phases == | == Phases == | ||
=== Identify Project Vision & Strategy (November 2015 - January 2016) === | === 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) | * Scope and Governance (January 2016) | ||
* Initial project summit (January 2016) | * Initial project summit (January 2016) | ||
| + | |||
=== OWASP White Belt (January 2016 - September 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 creation (January - March 2016) | ||
* Content recording (March 2016) | * Content recording (March 2016) | ||
* Infrastructure code and build (January - September 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 (July 2016) | ||
| + | Alpha is opening up the content and systems to a select group of testers. | ||
* Second project summit @ AppSec EU (July 2016) | * Second project summit @ AppSec EU (July 2016) | ||
* Beta (August 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) | * Launch of content at AppSec USA (September 2016) | ||
| + | OWASP Security White Belt available to the world! | ||
| + | |||
=== OWASP Yellow Belt (October 2016 - September 2017) === | === OWASP Yellow Belt (October 2016 - September 2017) === | ||
* Content creation (October 2016 - March 2017) | * Content creation (October 2016 - March 2017) | ||
| Line 82: | Line 99: | ||
=== OWASP Green Belt, OWASP Brown Belt, OWASP Black Belt (October 2017 - September 2018) === | === OWASP Green Belt, OWASP Brown Belt, OWASP Black Belt (October 2017 - September 2018) === | ||
* Infrastructure update (January - July 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) | * Finalize governance and oversight (January - March 2018) | ||
| + | The processes and procedures for judging and tracking activities must be finalized. | ||
* Alpha (July 2018) | * Alpha (July 2018) | ||
* Beta (August 2018) | * Beta (August 2018) | ||
* Launch of concept and completion of initial scope (September 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 = | = White Belt = | ||
| Line 102: | Line 121: | ||
==Learning Objective== | ==Learning Objective== | ||
Application of knowledge tailored to a specific role (builder and breaker) | Application of knowledge tailored to a specific role (builder and breaker) | ||
| + | ==Keyword== | ||
| + | Applying | ||
==Module List== | ==Module List== | ||
In development now. | In development now. | ||
| Line 109: | Line 130: | ||
[[File:Brown-belt.png|200px]] | [[File:Brown-belt.png|200px]] | ||
[[File:Black-belt.png|200px]] | [[File:Black-belt.png|200px]] | ||
| + | ==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. | ||
=FAQs= | =FAQs= | ||
Latest revision as of 01:10, 7 December 2015
OWASP Security NinjaThe 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.
MissionOWASP Security Ninja educates, empowers, reaches, and recognizes builders and breakers in web application security.
DeliveryThe 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. LicensingOWASP Security Ninja is free to use. Its licensing is dependent on several factors:
|
Logo
PresentationComing Soon. Project LeaderRelated ProjectsCode RepositoryThe OWASP Security Ninja code will be stored on GitHub shortly. News and Events
Classifications
|
