https://github.com/stevecoward/ansible-pentest-deploy

Using Ansible as an orchestrator, this project is another solution for testers looking to configure and deploy a new VM or VPS box with the tools that they need for penetration testing.
https://github.com/stevecoward/ansible-pentest-deploy

ansible ansible-playbook pentest python2

Last synced: 21 days ago
JSON representation

Using Ansible as an orchestrator, this project is another solution for testers looking to configure and deploy a new VM or VPS box with the tools that they need for penetration testing.

• Host: GitHub
• URL: https://github.com/stevecoward/ansible-pentest-deploy
• Owner: stevecoward
• License: mit
• Created: 2017-08-28T20:24:21.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2017-12-03T17:02:11.000Z (about 7 years ago)
• Last Synced: 2024-08-05T17:40:46.122Z (4 months ago)
• Topics: ansible, ansible-playbook, pentest, python2
• Language: Python
• Size: 22.5 KB
• Stars: 20
• Watchers: 2
• Forks: 10
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-hacking-lists - stevecoward/ansible-pentest-deploy - Using Ansible as an orchestrator, this project is another solution for testers looking to configure and deploy a new VM or VPS box with the tools that they need for penetration testing. (Python)

README

        
## Pentest Tools Deployer with Ansible

Using Ansible as an orchestrator, this project is another solution for testers looking to configure and deploy a new VM or VPS box with the tools that they need for penetration testing. 

Current solutions I've seen involve either a crazy amount of custom Bash/Shell scripting that is buggy or reliance on a home-grown deployment framework which is also buggy and not often updated. Ansible is an extremely flexible orchestration framework used for all kinds of devops projects. It's also an actively maintained project, which is critical when relying on it to deploy servers in many different environments.

### Assumptions

A few assumptions are made with this particular iteration of the Ansible playbook:

* The target systems are Debian 7.x or greater (support for multiple OSes to follow later)

* Ansible is installed on the host deploying the Ansible playbook (see below for installation steps)

* This assumes root + public key authentication access to the target host(s) is feasible

* Python 2.x is installed on the target host(s)

* `group_vars/all` is filled in with a username and linux password hash for the password value

 

### Installation and Usage

On the deployment host, Ansible needs to be installed and two Ansible roles must be installed via `ansible-galaxy`:

```

> pip install ansible

> ansible-galaxy install rvm_io.ruby naftulikay.go-dev

```

Designate a file to house one or many target host IP addresses, formatted like so:

```

[c2]

10.0.0.15

10.0.0.20

```

Run the Ansible playbook:

```

> ansible-playbook -i hosts site.yml

```

### Releases

[v1.0](https://github.com/stevecoward/ansible-pentest-deploy/releases/tag/v1.0 "Ansible Pentest Playbook")

### TODO

There are quite a few things that can be done with the project at this initial stage. The main ideas I have are:

* Support more tools

* ~~Symlink installed tools to `/usr/bin` or `/usr/local/bin` so they can be called anywhere~~

* ~~Group tools into their own sub-roles within the current Ansible playbook structure~~

 * A lot more