Simulation environment for attacks on computer networks
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Thorsten Sick ab6787241c pylinting round2 3 years ago
app pylinting round2 3 years ago
doc Added compiled documentation to shipit 3 years ago
plugins pylinting round2 3 years ago
systems attacker and target 3 working properly in vagrant 4 years ago
tests pylinting round2 3 years ago
tools Added compiled documentation to shipit 3 years ago
.gitignore Initial update 4 years ago
CONTRIBUTING.txt Documentation upgrade improved contributing.txt 4 years ago
CONTRIBUTORS.txt Basic contribution files added 4 years ago
Makefile Added compiled documentation to shipit 3 years ago
README.md Documentation upgrade 4 years ago
caldera_control.py PEP8 fixes 4 years ago
caldera_subset_classic.txt Caldera experiments can be independently controlled by files. Those will overwrite the caldera attacks in the experiment files. Good for batch processing 4 years ago
experiment_control.py TODO cleanup 3 years ago
init.sh Documentation can be built now 4 years ago
machine_control.py pylinting 3 years ago
metasploit_control.py pylinting 3 years ago
plugin_manager.py pylinting 3 years ago
pylint.rc Added pylint rc 4 years ago
requirements.txt pylinting 3 years ago
requirements_dev.txt Documentation can be built now 4 years ago
setup.py Unit tests working now 4 years ago
template.yaml Removed kali config from yaml files. Replaced with a more generic attack_plugin config 3 years ago
tox.ini Automated tests for plugins 3 years ago

README.md

PurpleDome creates simulated systems which hack each other

It creates several virtual machines to simulate a target network. A Kali attacker will be spawned and use configured attacks to blast at the targets. Those attacks can be Kali command line tools, Caldera abilities or Metasploit tools.

The goal is to test sensors and detection logic on the targets and in the network and improve them.

The system is at the same time reproducible and quite flexible (target system wise, vulnerabilities on the targets, attacks).

Installation

Setting up the python environment:

./init.sh

The typical local use case is to create the machines using Vagrant and running them in VirtualBox:

... sudo apt install vagrant virtualbox ...

You will have to switch into the python environment to run it

Before using any PurpleDome commands switch into the python environment:

... source venv/bin/activate ...

(this will contain the libraries in the required versions)

Testing

Basic code and unit tests can be run by

make test

That way you can also see if your env is set up properly

Running the basic commands

All command line tools have a help included. You can access it by the "--help" parameter

... python3 ./experiment_control.py -v run ...

  • -v is verbosity. To spam stdout use -vvv
  • run is the default command
  • --configfile is optional. If not supplied it will take experiment.yaml

Most of the configuration is done in the yaml config file. For more details check out the full documentation

The real documentation

This README is just a short overview. In depth documentation can be found in the doc folder.

Documentation is using sphinx

https://www.sphinx-doc.org/en/master/index.html

Generate it switching to the directory doc and calling

make all