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 DevSlop Project"
Tanyajanca (talk | contribs) |
Tanyajanca (talk | contribs) (First draft COMPLETE!) (Tag: Visual edit) |
||
| Line 158: | Line 158: | ||
=Project About= | =Project About= | ||
| − | + | The OWASP DevSlop project is intended as place for people to learn about new, modern and different web related application security issues. It is a vulnerable series of systems, open to the public to download and play with. The first instalment is called Pixi and is available now. More pieces will be released as they are available, as well as training and other learning aids. | |
| − | |||
| − | The | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
__NOTOC__ <headertabs></headertabs> | __NOTOC__ <headertabs></headertabs> | ||
Revision as of 20:49, 9 September 2017
OWASP DevSlop Tool ProjectThe hacker jungle gym built on DevOps disasters.Modern applications often use APIs and other micro services to deliver faster and better products and services. However, there are currently few training grounds for security testing in such areas. In comes DevSlop, OWASP's newest project, a collection of DevOps security catastrophes made as a vulnerable testing and proving ground for developers and security testers alike.DescriptionDevSlop's Pixi, the first of many entries to come for this OWASP project, is currently publicly available for your hacking and learning pleasure. Pixi is available in a docker container and consists of vulnerable web services, which will hopefully teach users how to test APIs for security and how to write better APIs in the future. It is intentionally vulnerable, with the hopes that users can learn to test on it and also learn how to create better APIs in the future.As more pieces of DevSlop are released they will be introduced here. LicensingThis program is free software: you can redistribute it and/or modify it under the terms of the link GNU Affero General Public License 3.0 as published by the Free Software Foundation. OWASP DevSlop and any contributions are Copyright © by Nicole Becher & Tanya Janca 2017. |
Project ResourcesDocumentation Wiki Home Page Issue Tracker Project LeaderRelated ProjectsClassifications
|
News and Events
| |||||||
To get Pixi is simple!
Download Pixi here: https://github.com/thedeadrobots/pixi
Install Docker and start it.
Type the following at your command prompt:
> git clone https://github.com/thedeadrobots/pixi.git <enter>
> docker-compose up <enter>
You're all set!
I have a great idea for new DevSlop additions, how do I tell you(s)?
Email us! [email protected] (Nicole Becher and Tanya Janca). You can do the math. :)
How can I follow updates on the project?
How can I participate in your project?
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.
If I am not a programmer can I participate in your project?
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 people to give us ideas for new components and problems to add, as well as people to help code them. See the Road Map and Getting Involved tab for more details.
Contributors
The OWASP DevSlop Project was created by the project leaders, Nicole and Tanya. Contributors include: Mordecai Kraushar.
The first contributors to the project were:
- Nicole Becher
- Tanya Janca
Roadmap
As of September 2017, the highest priorities for the next 12 months are:
Each DevSlop component will have it's own roadmap.
DevSlop Project Roadmap:
- Finish completing this Wiki page and get it reviewed/approved
- Move all Pixi code into OWASP GitHub
- Promote Project (interviews, speaking engagements, articles, etc)
- Document Project
- Create Issue Tracker
- Follow Pixi Roadmap
- Accept ideas for future components
- Create HTTP 2.0 app as Component #2
- Create more DevOps apps
Pixi Roadmap (First DevSlop Component):
- Document all the vulnerabilities
- Multi language support
- Finish CTF mode
Getting Involved
Involvement in the development and promotion of DevSlop is actively encouraged! You do not have to be a security expert or a programmer to contribute. Some of the ways you can help are as follows:
Ideas
We need to know where to go next with this project. Have you seen an IT tragedy recently? Tell us about it! The more modern and 'different' the better!
Coding
We could implement some of the later items on the roadmap sooner if someone wanted to help out with coding it. Someone like you.
Localization
Are you fluent in another language? Can you help translate the text strings in the DevSlop Project into that language? Pretty please?
Feedback
Please email us to give us feedback: [email protected] (Nicole Becher and Tanya Janca)
- What do like?
- What don't you like?
- What features would you like to see prioritized on the roadmap?
The DevSlop Project must provide documentation (in form of videos, blog posts, interviews, within the app, or anything else) to teach users how to use it. Without any information it's hard to know if the users are learning all of the lessons that they need to. It would also be ideal if Pixi and other future components were translated into different languages.
The OWASP DevSlop project is intended as place for people to learn about new, modern and different web related application security issues. It is a vulnerable series of systems, open to the public to download and play with. The first instalment is called Pixi and is available now. More pieces will be released as they are available, as well as training and other learning aids.
