Co-authored by Timo Pagel
Make sure all participants have their own running Juice Shop instance to work with. While attempting challenges like RCE or XXE students might occasionally take down their server and would severely impact other participants if they shared an instance.
There are multiple Run Options which you can choose from. It is perfectly fine to run multiple docker containers on one host. They do not effect each other.
Especially in awareness trainings for management you might want to create a higher immersion by making the Juice Shop look like an application in the corporate design of the participants' own company. Juice Shop offers various customization options to achieve this.
Several custom configurations already come packaged with the Juice Shop source code, the two most sophisticated ones being 7 Minute Security and Mozilla.
In addition, you might want to disable all challenge notifications during awareness trainings to avoid distraction. The Quiet configuration demonstrates the necessary options to achieve this.
For a really sophisticated and immersive demo consider performing some Additional Browser tweaks. These will let you use OAuth2 login via Google and cast the illusion that coupon codes were actually tweeted by your customer's company.
In a class room setup you have to find a way to distribute the URL of each instance to the participants. For small groups, it is probably fine to just spin up a number of containers and tell all participants which URL they have to use. An example to spin up 10 Docker containers on a UNIX based system is to run
for i in {10..19}; do docker run -d -p 40$i:3000 bkimminich/juice-shop; done
If you want to track progress centrally during the training, you might want to host a central CTF server where participants can post the challenges they already solved. You might consider turning off public visibility of the leader board on the CTF server unless you want to encourage the students to hack very competitively.
One existing training which uses the Juice Shop for example is a Timo Pagel's University Module. The structure mostly is as follows:
- Introduce a topic (e.g. SQL Injection)
- Let the participants try it out in the Juice Shop
- Show mitigation/counter measures
Björn Kimminich's Web Application Security Training slides as well as the web attack chapters of his IT Security Lecture follow a similar pattern of
- Introduction
- Timeboxed exercise
- Demonstration of the hack (for all who did not finish the exercise in time)
- Explaining mitigation and prevention
You can find more links to existing material in the Lectures and Trainings section of the project references on on GitHub.
Well suited for live demonstrations in trainings or talks are the the following challenges:
- XSS Tier 0 ( ⭐ )
- XSS Tier 1 ( ⭐ )
- Admin Section ( ⭐⭐ )
- Confidential Document ( ⭐ )
- Basket Access ( ⭐⭐ )
- Forgotten Sales Backup ( ⭐⭐⭐ )
- Forgotten Developer Backup ( ⭐⭐⭐⭐ )
- CSRF ( ⭐⭐⭐⭐ )
- User Credentials ( ⭐⭐⭐⭐ )
- Forged Coupon ( ⭐⭐⭐⭐⭐⭐ )
A particularly impressive showcase of XSS site-defacement combined with a keylogger is provided explicitly for live demos and awareness trainings.
There is also a video recording available on YouTube: https://www.youtube.com/watch?v=L7ZEMWRm7LA. This is a good fallback in case the Docker-based setup does not work for you.