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 d06bf8a5ff
Merge pull request #15 from avast/first_action
de-activated pylint in Makefile. Tox.ini will be a better place for it
3 years ago
.github/workflows Reducing to python 3.9 3 years ago
app Updated documentation 3 years ago
doc Updated documentation 3 years ago
plugins Made pylint happy 3 years ago
systems Extending vagrant file - machine upgrade 3 years ago
templates Adding line numbers and file names to metasploit attacks 3 years ago
tests fixing path in unit test 3 years ago
tools shipit extended to accept deeper nested files. Especially in plugin resource folders 3 years ago
.gitignore Initial update 4 years ago
CONTRIBUTING.txt Documentation upgrade improved contributing.txt 3 years ago
CONTRIBUTORS.txt Basic contribution files added 4 years ago
Makefile Updating auto python tests 3 years ago
README.md Documentation upgrade 3 years ago
caldera_control.py PEP8 fixes 3 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
doc_generator.py Some PEP8 cleanup 3 years ago
experiment_control.py TODO cleanup 3 years ago
init.sh Init now installs latex dependencies. Auto generation of human readable documentation is now possible 3 years ago
machine_control.py pylinting 3 years ago
metasploit_control.py pylinting round 4 3 years ago
plugin_manager.py Unit tests for pluginmanager 3 years ago
pydantic_test.py Made pylint happy 3 years ago
pylint.rc Made pylint happy 3 years ago
requirements.txt Unit tests work. Still some PEP errors and no integration checks 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 Updated documentation 3 years ago
tox.ini All auto tests work. Integration tests not yet run ! 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