WebGoat is a deliberately insecure web application maintained by OWASP designed to teach web application security lessons. You can install and practice with WebGoat. There are other ‘goats’ such as WebGoat for .Net. In each lesson, users must demonstrate their understanding of a security issue by exploiting a real vulnerability in the WebGoat application. For example, in one lesson the user must use SQL injection to steal fake credit card numbers. The application aims to provide users with a realistic learning environment, giving them hints and code that further explains each lesson.
The focus of WebGoat 8.0 is to train developers not only how to exploit, but also how to fix and mitigate, a vulnerability.
This Working Session will explore how WebGoat can be improved.
- Add the ability to fix a vulnerability within a lesson. Instead of just finding an issue, we want to allow users to try and fix the issue. It is technically challenging to implement this without restarting the complete WebGoat application
- We need to ‘automatically’ verify an implemented fix. We need test cases which will try to trigger the issue. It would be nice to develop a shared knowledge base in which anyone can submit their solution and others could try to break proposed solutions
- Develop a shared knowledge base for different Goat implementations. Only the language implementation details are different; the explanation about a specific vulnerability and mitigation can be shared
- Develop more lesson content, for example lessons specifically about crypto
The target audience for this Working Session is:
- Web application developers
- Teachers of web application security
For more details, more ideas etc. contact https://github.com/OWASP/owasp-summit-2017/blob/master/Participants/Nanne-Baars.md
Related Working Session(s)
- Evaluation/Optimization/Creation of Training Slides
- Teaching Attacker perspective to Developers
Back to list of all Working Sessions and Tracks
Edit this page here