Automated Red Team Infrastructure deployement using Docker
Early release. Follow me on Twitter to stay updated on Redcloud's development.
Redcloud is a powerful and user-friendly toolbox for deploying a fully featured Red Team Infrastructure using Docker. Harness the cloud's speed for your tools. Deploys in minutes. Use and manage it with its polished web interface.
Ideal for your penetration tests, shooting ranges, red teaming and bug bounties!
Self-host your attack infrastructure painlessly, deploy your very own live, scalable and resilient offensive infrastructure in a matter of minutes.
The following demo showcases deployment of Redcloud through ssh, followed by Metasploit. We then look at Traefik and a live volume attached to Metasploit. Finally, we check that Metasploit's DB is functional with the web terminal, delete the container, and terminate Redcloud.
cat ~/.ssh/idrsa.pub | ssh [email protected] 'cat >> .ssh/authorizedkeys'
eval (docker-machine env default)
Deploy: ```bash > git clone https://github.com/khast3x/redcloud.git > cd redcloud > python redcloud.py
PyYAMLto print the list of available templates. It's installed by default on most systems.
pip install -r requirements.txt ```
Redcloud has 3 different deployment methods: 1. Locally 2. Remotely, using ssh. Requires having your public key in your target's
authorized_keysfile. 3. Remotely, using docker-machine. Run the
eval (docker-machine env deploy_target)line to preload your env with your docker-machine, and run
redcloud.py. Redcloud should automatically detect your docker-machine, and highlight menu items relevant to a docker-machine deployment.
redcloud.pydeploys a Portainer stack, preloaded with many tool templates for your offensive engagements, powered by Docker. Once deployed, control Redcloud with the web interface. Uses Traefik as reverse-proxy. Easy remote deploy to your target server using the system
Use the web UI to monitor, manage, and interact with each container. Use the snappy web terminal just as you would with yours. Create volumes, networks and port forwards using Portainer's simple UI.
Deploy and handle all your favorite tools and technics with the power of data-center-grade internet :rocket:
In the following section, we'll be going more in-depth inside Redcloud's design concepts. You can get started without having to dive inside though.
redcloud.py: Starts/Stops the Web interface and App Templates, using Docker and Portainer.
portainer: Portainer web interface.
traefik: Traefik reverse-proxy container to the web interface, api and files containers. Some templates have pre-configured routes for convenience. See the
http.servercontainer that feeds the App Templates. Lives in an "inside" network.
cert_gen: The omgwtfssl container that generates the SSL certificates using common best practices.
redcloud_filesvolume. You can also access the
redcloud_logcontainer content, protected by the same
.htpasswdas Traefik. Default credentials:
Redcloud deployment workflow is as follows: 1. Clone/Download Redcloud repository. 2. Launch
redcloud.py. 3. Choose deployment candidate from the menu (local, ssh, docker-machine). 4.
redcloud.pyautomatically: * checks for
docker-composeon target machine. * installs
docker-composeif absent. * deploys the web stack on target using
docker-compose. 5. Once deployment is complete,
redcloud.pywill output the URL. Head over to https://your-deploy-machine-ip/portainer. 6. Set username/password from the web interface. 7. Select the endpoint (the only one on the list). 8. Access the templates using the "App Templates" menu item on the left :rocket:
App Template deployment is as follows:
1. Choose template.
2. If you wish to add additional options, select "+ Show advanced options".
3. Add port mapping, networking options, and volume mapping as you see fit.
4. Select "Deploy the container".
5. Portainer will launch the container. It may take a few minutes if it needs to fetch the image. If your server is in a data center, this step will be very fast.
6. Container should be running :rocket:
7. Portainer will redirect you to the "Containers" page. From there, you can:
a. View live container logs.
b. Inspect container details (
sh. Choose accordingly from the drop-down menu.
Redcloud makes it easy to play around with networks and containers.
You can create additional networks with different drivers, and attach your containers as you see fit. Redcloud comes with 2 networks,
You can share data between containers by sharing volumes. Redcloud comes with 3 volumes:
certs: Container with the certificates generated by omgwtfssl.
files: Standard file sharing volume. For now, the files are available when browsing https://your-server-ip/files, and are served by the Traefik reverse-proxy container directly from the
filesvolume. A typical use-case is to attach the volume to a Metasploit container, generate your payload directly into the
filesvolume. You can now serve your fresh payload directly through the Traefik to file server route.
logs: Available for logs, served by the file-server too. Access requires basic auth. Default is
If you wish to stay in your terminal to work with the deployed containers, its very easy using Docker. Keep these things in mind: * Most containers have
bash, but some use
shinstead * All Redcloud App Templates container names start with
red_, such as
red_msf-postgresql* With Docker, you can either use
attachto interact with a container *
execis preferred as it creates a new process *
attachlands you straight on the running process, potentially killing your running container * If running Redcloud: * Locally or using
docker-machine, simply type these in your local shell * Using
ssh, first ssh into your deployment target to run the following commands
To start interacting with the desired deployed container:
docker exec -it red_container-name /bin/bash [email protected]:/# ```
If you see the following message, it means
bashis not installed. In that case simply replace
> docker exec -it red_container-name /bin/bash OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown
> docker exec -it red_container-name /bin/sh #
docker attach, simply run: ```bash
docker attach red_container-name ``If usingattach, the container needs to be started ininteractive mode`, so as to land in a interactive shell.
Point your browser to
filesvolume for more information.
Redcloud generates a new unsigned SSL certificate when deploying.
The certificate is generated by omgwtfssl, implementing most best practices. Once generated:
It will dump the certificates it generated into /certs by default and will also output them to stdout in a standard YAML form, making them easy to consume in Ansible or other tools that use YAML.
Certificates are stored in a shared docker volume called
certs. Your containers can access this volume if you indicate it in "+ Advanced Settings" when deploying it. The Traefik reverse-proxy container fetches the certificates directly from its configuration file. If you wish to replace these certificates with your own, simply replace them on this volume.
It also means you can share the generated certificates into other containers, such Empire or Metasploit for your reverse callbacks, or for a phishing campaign. Most SSL related configurations can be found in
You can stop Redcloud directly from the menu.
Deployed App templates need to be stopped manually before stopping Redcloud. You can stop them using the Portainer web interface, or
docker rm -f container-name.
docker-compose killinside the
redcloud/folder. The local and docker-machine stop option is the same, thus they are combined in the same option.
Redcloud uses Portainer to orchestrate and interface with the Docker engine. Portainer in itself is a fantastic project to manage Docker deployments remotely. Portainer also includes a very convenient template system, which is the major component for our Redcloud deployment.
Templates can be found in
./templates/templates.yml. Portainer fetches the template file from a dedicated container (
Traefik is a wonderful "cloud-native edge router". It has replaced the previous NGINX reverse-proxy setup.
A Traefik image is built during deployment, using the Dockerfile located in
traefik/Dockerfile. It adds a
By default, deployment spawns the following routes:
Authentications are based of the
From the Traefik api web interface, you can view your deployed routes, monitor health, as well as real time metrics. Its very neat.
You can add additional labels that tell Traefik where to route traffic, using either: *
templates.ymlfile * Portainer's web interface
See the official documentation for more information.
Redcloud deploys with a self-signed https certificate, and proxies all interactions with the web console through it.
However, the default network exposes your containers' ports to the outside world.
You can: * Remove exposed ports and access the normal port from a machine inside the docker network * Add custom
labelsto create routes with Traefik. See the
docker-compose.ymlfile for inspiration. * Start an Ubuntu or Kali with noVNC (VNC through http) from templates, add it to both an "inside" and "outside" network, and access exposed interfaces from inside. * Add .htaccess configurations
docker-machineinstallations require root privileges. You can downgrade privilege requirements following the official documentation. * The install script is pulled directly from the official docker repositories. *
redcloud.pyfetches Redcloud's public IP address using icanhazip.com.
| Deploy Target | Status | |:-------------:|:-------------------:| | Ubuntu Bionic | :heavycheckmark: | | Ubuntu Xenial | :heavycheckmark: | | Debian Strech | :heavycheckmark: |
python --version. Redcloud needs python 3+.
pythonif on an older system.
redcloud.pyrequires that deployment candidate have the public key in their
.ssh/authorized_keys, and handles password-less authentication using the user's public key. This is the default configuration for most VPS workflows.
evalcommand as illustrated above.
docker-machineinstallations require root privileges. You can downgrade privilege requirements following the official documentation
rm -rf /opt/portainer/data
apt-get install python3-distutilson debian/ubuntu base.
portainerwill be unable to use its default volume location
/opt/. To solve this, open the
/opt/portainer/data:/datawith a folder with write-access, for example:
/tmp/portainer/:/dataand create the
/tmp/portainerdirectory before running Redcloud.
Deploying a container
msfconsolethrough the web interface
Traefik real-time data on reverse-proxy routes
Deploying using ssh
Any help is appreciated. This is a side project, so it's probably missing a few bolts and screws. Above all: * Reporting or fixing Redcloud bugs & quirks. * Adding templates. Please keep it clean, and from the creator's docker hub repository if possible. * Adding documentation. * Detailing use cases in blog articles. I'll add links to blog posts here, so please be sure to contact me if you make one! :v: * Integrating Traefik with more templates. I'm currently having issues with the spiderfoot and ubuntu novnc for example. * Typos as issues. (no pull requests please)
You can host Redcloud on any Unix server that runs Docker.
Redcloud is intended to be used in a cloud environment, such as a simple VPS with ssh, or even an AWS EC2, GCP, etc...
A large range of cloud providers offer free credits to get familiar with their services. Many lists and tutorials cover getting free hosting credits from major vendors. This list is a good place to start.
Regarding deployment method, I personally prefer working with docker-machine as it becomes ridiculously easy to spawn new machines and manage them once you've got your cloud provider's driver setup. If you prefer using
ssh, be sure to take a look at evilsocket's shellz project to manage your keys and profiles.
hideNsneak - Mike Hodges
Finally, if you wish to see your tool integrated, hit me up on Twitter. This project is maintained on my free time. Keep an eye out in the dev branch for upcoming features.
Redcloud was originally developed to make deploying training environments for infosec students easier.
If you wish to stay updated on this project: