What is Multi-Juicer?
Editor to share with you what Multi-Juicer is, I believe that most people do not know much about it, so share this article for your reference, I hope you will learn a lot after reading this article, let's go to understand it!
Multi-Juicer
Multi-Juicer is a multi-user platform toolset that helps users run CTF and security training in conjunction with OWASP Juice Shop. As you security researchers may know, with the help of OWASP Juice Shop, we can easily build a CTF platform or conduct security training. However, the design philosophy of OWASP Juice Shop does not support multiple users using it at the same time. In addition, users may spend a lot of time building OWASP Juice Shop on their own devices. But don't worry, Multi-Juicer can help you solve all kinds of problems.
Multi-Juicer can help us run a separate Juice Shop instance for each OWASP Juice Shop participant in a central Kubernetes cluster, and each user no longer has to run the Juice Shop instance locally.
Function introduction
1. Create a new Juice Shop instance dynamically when the user needs it
2. Runs in a single domain name and uses a load balancer to help participants in the Juice Shop instance send traffic
3. To prevent the Juice Shop container from restarting, the challenge process can be automatically backed up and restored.
4. Automatically clear old and unused Juice Shop instances
Tool installation
Multi-Juicer needs to run on Kubernetes, and we need to use helm during installation]:
Helm repo add multi-juicer https://iteratec.github.io/multi-juicer/# for helm = installation guidelines for 3helm install multi-juicer multi-juicer/multi-juicer cloud service providers
In general, Multi-Juicer can run normally in any Kubernetes cluster, in order to facilitate the installation, configuration and operation of Multi-Juicer in Kubernetes clusters of different cloud service providers
Custom configuration
During the installation of Multi-Juicer, we can configure our own Juice Shop instance through a variety of custom configurations.
Download and save the file, and then have helm use our configuration file to perform the installation and configuration of the tool:
Helm install-f values.yaml multi-juicer. / multi-juicer/helm/multi-juicer/
Tool unloading
Helm delete multi-juicer
Tool dependence
In order to run Multi-Juicer normally on a Kubernetes cluster, the computing resource requirements of the tool for the cluster are as follows:
-1GB memory & 1 CPU
-for a single JuiceShop instance, number of 200MB & 0.2CPU* participants
The above is all the content of this article "what is Multi-Juicer?" thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!
