The FSL Test bench provides a save environment for security auditing and testing and can be used for teaching security testing methodologies. At the moment the focus lies on web applications. All application are running on top of a current Fedora installation with a Lighttpd web server and a MySQL server.
The FSL Test bench includes:
- Vulnerable web applications (DVWA, bWAPP, SQLI Labs, MIRC and more)
- PHP shells (PHP Shell, b374k and DNA Shell)
- Low-interaction honeypots
- Helper tools (Log viewer, CGIs, linfo and phpmyadmin)
All applications are directly accessible from a bootstrap-based website.
The FSL Test bench repository contains a subset of playbooks from the fedora-ansible git repository maintained by Fabian Affolter.
If you have just found Ansible or the Fedora Security Lab, you should start here:
The setup of Ansible is explained on the Ansible Getting Started page. Here is only the setup of the managed nodes and special details for the management system covered. For every system you want to manage, you need to have the client's SSH key in the authorized_keys file of the managed system and Python.
Make sure that Python is installed. If not, install the Python package on the managed node(s). If you have performed a minimal Fedora installation Python is available.
$ sudo dnf -y install pythonThe playbooks will use DNF as package management software instead of yum as
soon as DNF is the default Package management tool in Fedora. But for now,
everything is done with yum.
Add the SSH key to the authorized_keys file. Assuming you are logged-in with SSH on your management system.
sudo ssh-copy-id -i /root/.ssh/id_rsa.pub root@[IP address of your managed note]The file /etc/ansible/hosts shall contain all hosts to be setup up.
- fsl-tb: Default group name for machine which uses the all-in-one playbook
- fsl-tb-vpn: Default group name for machine which acts as VPN servers
- fsl-tb-master: Hosts for FSL Test bench guests when using visualization
- fsl_hosts: Hosts to install the Fedora Security Lab package set
After cloning this git repository, edit the variables/sensitive.yml file if you don't want to use password as default password.
The documentation is available at Read the Docs.
At the moment the structure of the repository looks like this:
.
├── all-in-one.yml -------- FSL Test bench on a single machine
├── docs ------------------ Documentation
├── files ----------------- Template files
│ ├── cgi --------------- Source files for CGI
│ ├── kickstart --------- Kickstart files
│ └── web-interface ----- All files for the web interface
├── fsl-packages-sync.py -- Python script to sync with FSL package list
├── fsl-tb-detect.nse ----- nmap script for the Test bench detection
├── fsl.yml ---------------
├── handlers -------------- Handlers for services
├── INSTALL.md ------------ Installation guide
├── local-setup.yml -------
├── openvpn-server.yml ----
├── README.md ------------- This files
├── tasks ----------------- A collection of tasks (all playbooks)
│ ├── apps -------------- Vulnerable web applications
│ ├── cgi --------------- CGI
│ ├── db-servers -------- Database servers
│ ├── directory-servers - Directory Servers
│ ├── file-servers ------ File servers
│ ├── ftp-servers ------- FTP servers
│ ├── helpers ----------- Helper tools
│ ├── honeypots --------- Low-interaction honeypots
│ ├── mail-servers ------ Mail server
│ ├── misc-servers ------ Various servers
│ └── shells ------------ PHP shells
│ └── web-servers ------- Web servers
└── variables ------------- Storage files for variablesThe file variables/sensitive.yml contains most application passwords. If you don't want to run with default password, edit this file according your needs and keep it save outside the repository.
All playbook content is assumed to be Creative Commons 3.0 Attribution licensed. Non-commercial or No-derivatives CC extensions are not acceptable, to encourage easy use by all users, regardless of purpose.