Difference between revisions of "OWASP Security Ninja Project"
|Line 140:||Line 140:|
* [https://www.owasp.org/index.php/User:edgeroute Chris Romeo]
* [https://www.owasp.org/index.php/User:edgeroute Chris Romeo]
= Road Map =
= Road Map =
Revision as of 23:19, 6 December 2015
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.
The OWASP Security Principles
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.
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:
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.
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.
Although this is a sample template, the project is real! 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.
OWASP Security Ninja is free to use. Its licensing is dependent on several factors:
What is OWASP Security Principles Project?
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? 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 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.
This document should serve as a guide to technical architects and designers outlining the fundamental principles of security.
The OWASP Security Ninja code will be stored on GitHub shortly.
News and Events
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 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
The OWASP Security Ninja project is in need of some additional people to list on this site!
The first contributors to the project are:
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.
| PROJECT INFO
What does this OWASP project offer you?
| RELEASE(S) INFO|
What releases are available for this project?