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 Juice Shop Project"
(→Project Resources) |
(→Project Resources) |
||
| Line 37: | Line 37: | ||
== Project Resources == | == Project Resources == | ||
| − | [https://github.com/bkimminich/juice-shop/releases/latest | + | === Installation === |
| + | |||
| + | [https://github.com/bkimminich/juice-shop/releases/latest Packaged Distributions] | ||
| + | |||
| + | [https://registry.hub.docker.com/u/bkimminich/juice-shop/ Docker Image] | ||
| + | |||
| + | [https://juice-shop.herokuapp.com/ Online Preview] | ||
| + | |||
| + | === Sources === | ||
[https://github.com/bkimminich/juice-shop Source Code] | [https://github.com/bkimminich/juice-shop Source Code] | ||
| − | [https://github.com/bkimminich/juice-shop/commits/master | + | [https://github.com/bkimminich/juice-shop/commits/master Revision History] |
| + | |||
| + | === Support === | ||
[https://github.com/bkimminich/juice-shop/blob/master/README.md Documentation] | [https://github.com/bkimminich/juice-shop/blob/master/README.md Documentation] | ||
| Line 49: | Line 59: | ||
[https://github.com/bkimminich/juice-shop/issues Issue Tracker] | [https://github.com/bkimminich/juice-shop/issues Issue Tracker] | ||
| − | [http://bkimminich.github.io/juice-shop | + | === Media === |
| + | |||
| + | [http://bkimminich.github.io/juice-shop Introduction Presentation] | ||
| − | [https://www.youtube.com/watch?v=vdnmR9RVspg | + | [https://www.youtube.com/watch?v=vdnmR9RVspg Auto-Hacking Video] |
== Project Leader == | == Project Leader == | ||
Revision as of 06:59, 26 July 2016
|
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. OWASP Juice Shop Tool ProjectThis section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for. The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects. By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for. And it's easy to get started by simply creating a new project from the appropriate project template. Juice Shop is an intentionally insecure webapp for pentesting & security awareness trainings written entirely in Javascript. Its vulnerabilities encompass the entire OWASP Top 10 as well as business logic bugs and other severe programming mistakes. DescriptionThis is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, 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, so project leaders should ensure that the description is meaningful. The Tool Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Tool project. After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red. Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category. The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort. Creating a new set of project pages from scratch can be a challenging task. By providing a sample layout, with instructional text and examples, the OWASP Tool Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security. Contextual custom dictionary builder with character substitution and word variations for pen-testers LicensingThis program is free software: you can redistribute it and/or modify it under the terms of the MIT License. OWASP Juice Shop and any contributions are Copyright © by Bjoern Kimminich 2014-2016. |
Project ResourcesInstallationSourcesSupportMediaProject LeaderRelated ProjectsThis is where you can link to other OWASP Projects that are similar to yours. Classifications
|
News and EventsThis is where you can provide project updates, links to any events like conference presentations, Project Leader interviews, case studies on successful project implementations, and articles written about your project.
| |||||||
