To bootup the range you need to perform the following steps: 1 - clone the project & perform the basic setup guide: 2 - terraform apply 3 - awsnuke to destroy
This started as an unofficial fork of the terraform-with-circleci-example. Then quickly evolved into a cloud-based SecDevOps penTesting lab.
The simple goal is to create an open-source repository of vulernable targets which provide the security researcher with the scalability, performance, and elastic compute of the cloud.
If you don't know how to use terraform, consider: this udemy terraform course content on github to learn the basics
The range is primarily setup for us-east-1. This is a simple reminder that I'm plan to create regional ami manifests for simple copy/pasta simplication of setup.
Create a location for all the terraform state files. These are the files which hold the Let's create a bucket to store our terraform data in & a few folders within.
aws s3 mb s3://secdevops-cuse
aws s3api put-object --bucket secdevops-cuse --key us-east-1
aws s3api put-object --bucket secdevops-cuse --key eu-west-2
aws s3api put-object --bucket secdevops-cuse --key ap-south-1
then let's initialize terraform in the desired aws region
cd ./terraform/environments/<aws-region>; terraform init; terraform plan
- docs
- environments
- keys
- modules
- infrastructure
- cloud-init
- config
- assets
- state
- tutorials
The only assets which obtain public IPs are configured for the kali subnet. That subnet has the very
specific map_public_ip_on_launch = true configuration. Add this configuration to other subnets before
creating the subnet.
IEUser / Passw0rd! - win7 / FlareVM
terraform / terraform - Default Windows
administrator / terraform - CommandoVM
remnux / malware - remnux
webuser / w3b$ecret - T-Pot
nxadmin / nxpassword - r7
password - Kali VNC Server
vagrant / vagrant - a few windows assets
3389 - CommandoVM / Flare VM 8000 - Nessus Network Monitor 443 - Tenable.SC 8834 - Nessus 5901 - Kali VNC 64297 - TPot UI 64295 - TPot SSH 3780 - R7 Insight VM