mirror of
https://github.com/telekom-security/tpotce.git
synced 2025-04-29 03:38:51 +00:00
247 lines
10 KiB
Markdown
247 lines
10 KiB
Markdown
# T-Pot Ansible
|
||
|
||
Here you can find a ready-to-use solution for your automated T-Pot deployment using [Ansible](https://www.ansible.com/).
|
||
It consists of an Ansible Playbook with multiple roles, which is reusable for all [OpenStack](https://www.openstack.org/) based clouds (e.g. Open Telekom Cloud, Orange Cloud, Telefonica Open Cloud, OVH) out of the box.
|
||
Apart from that you can easily adapt the deploy role to use other [cloud providers](https://docs.ansible.com/ansible/latest/modules/list_of_cloud_modules.html) (e.g. AWS, Azure, Digital Ocean, Google).
|
||
|
||
The Playbook first creates a new server and then installs and configures T-Pot.
|
||
|
||
This example showcases the deployment on our own OpenStack based Public Cloud Offering [Open Telekom Cloud](https://open-telekom-cloud.com/en).
|
||
|
||
# Table of contents
|
||
- [Preparation of Ansible Master](#ansible-master)
|
||
- [Ansible Installation](#ansible)
|
||
- [Agent Forwarding](#agent-forwarding)
|
||
- [Preparations in Open Telekom Cloud Console](#preparation)
|
||
- [Create new project](#project)
|
||
- [Create API user](#api-user)
|
||
- [Import Key Pair](#key-pair)
|
||
- [Create VPC, Subnet and Security Group](#vpc-subnet-securitygroup)
|
||
- [Clone Git Repository](#clone-git)
|
||
- [Settings and recommended values](#settings)
|
||
- [OpenStack authentication variables](#os-auth)
|
||
- [Ansible remote user](#remote-user)
|
||
- [Instance settings](#instance-settings)
|
||
- [User password](#user-password)
|
||
- [Configure `tpot.conf.dist`](#tpot-conf)
|
||
- [Optional: Custom `ews.cfg`](#ews-cfg)
|
||
- [Optional: Custom HPFEEDS](#hpfeeds)
|
||
- [Deploying a T-Pot](#deploy)
|
||
- [Further documentation](#documentation)
|
||
|
||
<a name="ansible-master"></a>
|
||
# Preparation of Ansible Master
|
||
You can either run the deploy script locally on your Linux or MacOS machine or you can use an ECS (Elastic Cloud Server) on Open Telekom Cloud, which I did.
|
||
I used Ubuntu 18.04 for my Ansible Master Server, but other OSes are fine too.
|
||
Ansible works over the SSH Port, so you don't have to add any special rules to your Security Group.
|
||
|
||
<a name="ansible"></a>
|
||
## Ansible Installation
|
||
At first we need to add the repository and install Ansible:
|
||
`sudo apt-add-repository --yes --update ppa:ansible/ansible`
|
||
`sudo apt install ansible`
|
||
|
||
<a name="agent-forwarding"></a>
|
||
## Agent Forwarding
|
||
Agent forwarding must be enabled in order to let Ansible do its work.
|
||
- On Linux or MacOS:
|
||
- Create or edit `~/.ssh/config`
|
||
- If you execute the script remotely on your Ansible Master Server:
|
||
```
|
||
Host ANSIBLE_MASTER_IP
|
||
ForwardAgent yes
|
||
```
|
||
- If you execute the script locally, enable it for all hosts, as this includes newly generated T-Pots:
|
||
```
|
||
Host *
|
||
ForwardAgent yes
|
||
```
|
||
- On Windows using Putty:
|
||
|
||
|
||
<a name="preparation"></a>
|
||
# Preparations in Open Telekom Cloud Console
|
||
(You can skip this if you have already set up an API account, VPC, Subnet and Security Group)
|
||
(Just make sure you know the naming for everything, as you will need it to configure the Ansible variables.)
|
||
|
||
Before we can start deploying, we have to prepare the Open Telekom Cloud tenant.
|
||
For that, go to the [Web Console](https://auth.otc.t-systems.com/authui/login) and log in with an admin user.
|
||
|
||
<a name="project"></a>
|
||
## Create new project
|
||
I strongly advise you to create a separate project for the T-Pots in your tenant.
|
||
In my case I named it `tpot`.
|
||
|
||
|
||
|
||
<a name="api-user"></a>
|
||
## Create API user
|
||
The next step is to create a new user account, which is restricted to the project.
|
||
This ensures that the API access is limited to that project.
|
||
|
||
|
||
|
||
<a name="key-pair"></a>
|
||
## Import Key Pair
|
||
:warning: Now log in with the newly created API user account and select your project.
|
||
|
||
|
||
|
||
|
||
Import your SSH public key.
|
||
|
||
|
||
|
||
<a name="vpc-subnet-securitygroup"></a>
|
||
## Create VPC, Subnet and Security Group
|
||
- VPC (Virtual Private Cloud) and Subnet:
|
||
|
||
|
||
|
||
- Security Group:
|
||
The configured Security Group should allow all incoming TCP / UDP traffic.
|
||
If you want to secure the management interfaces, you can limit the incoming "allow all" traffic to the port range of 1-64000 and allow access to ports > 64000 only from your trusted IPs.
|
||
|
||
|
||
|
||
<a name="clone-git"></a>
|
||
# Clone Git Repository
|
||
Clone the `tpotce` repository to your Ansible Master:
|
||
`git clone https://github.com/dtag-dev-sec/tpotce.git`
|
||
All Ansible related files are located in the [`cloud/ansible/openstack`](../../cloud/ansible/openstack) folder.
|
||
|
||
<a name="settings"></a>
|
||
# Settings and recommended values
|
||
You can configure all aspects of your Elastic Cloud Server and T-Pot before using the Playbook.
|
||
The settings are located in the following Ansible vars files:
|
||
|
||
<a name="os-auth"></a>
|
||
## OpenStack authentication variables
|
||
Located at [`openstack/roles/deploy/vars/os_auth.yaml`](openstack/roles/deploy/vars/os_auth.yaml).
|
||
Enter your Open Telekom Cloud API user credentials here (username, password, project name, user domain name):
|
||
```
|
||
auth_url: https://iam.eu-de.otc.t-systems.com/v3
|
||
username: your_api_user
|
||
password: your_password
|
||
project_name: eu-de_your_project
|
||
os_user_domain_name: OTC-EU-DE-000000000010000XXXXX
|
||
```
|
||
You can also perform different authentication methods like sourcing your `.ostackrc` file or using the OpenStack `clouds.yaml` file.
|
||
For more information have a look in the [os_server](https://docs.ansible.com/ansible/latest/modules/os_server_module.html) Ansible module documentation.
|
||
|
||
<a name="remote-user"></a>
|
||
## Ansible remote user
|
||
You may have to adjust the `remote_user` in the Ansible Playbook under [`openstack/deploy_tpot.yaml`](openstack/deploy_tpot.yaml) depending on your Debian base image (e.g. on Open Telekom Cloud the default Debian user is `linux`).
|
||
|
||
<a name="instance-settings"></a>
|
||
## Instance settings
|
||
Located at [`openstack/roles/deploy/vars/main.yaml`](openstack/roles/deploy/vars/main.yaml).
|
||
Here you can customize your virtual machine specifications:
|
||
- Specify the region name
|
||
- Choose an availibility zone. For Open Telekom Cloud reference see [here](https://docs.otc.t-systems.com/en-us/endpoint/index.html).
|
||
- Change the OS image (For T-Pot we need Debian 9)
|
||
- (Optional) Change the volume size
|
||
- Specify your key pair
|
||
- (Optional) Change the instance type (flavor)
|
||
`s2.medium.8` corresponds to 1 vCPU and 8GB of RAM and is the minimum required flavor.
|
||
A full list of Open telekom Cloud flavors can be found [here](https://docs.otc.t-systems.com/en-us/usermanual/ecs/en-us_topic_0035470096.html).
|
||
- Specify the security group
|
||
- Specify the network ID (For Open Telekom Cloud you can find the ID in the Web Console under `Virtual Private Cloud --> your-vpc --> your-subnet --> Network ID`; In general for OpenStack clouds you can use the `python-openstackclient` to retrieve information about your resources)
|
||
|
||
```
|
||
region_name: eu-de
|
||
availability_zone: eu-de-03
|
||
image: Standard_Debian_9_latest
|
||
volume_size: 128
|
||
key_name: your-KeyPair
|
||
flavor: s2.medium.8
|
||
security_groups: your-sg
|
||
network: your-network-id
|
||
```
|
||
|
||
<a name="user-password"></a>
|
||
## User password
|
||
Located at [`openstack/roles/install/vars/main.yaml`](openstack/roles/install/vars/main.yaml).
|
||
Here you can set the password for your Debian user (**you should definitely change that**).
|
||
```
|
||
user_password: LiNuXuSeRPaSs#
|
||
```
|
||
|
||
<a name="tpot-conf"></a>
|
||
## Configure `tpot.conf.dist`
|
||
The file is located in [`iso/installer/tpot.conf.dist`](../../iso/installer/tpot.conf.dist).
|
||
Here you can choose:
|
||
- between the various T-Pot editions
|
||
- a username for the web interface
|
||
- a password for the web interface (**you should definitely change that**)
|
||
|
||
```
|
||
# tpot configuration file
|
||
# myCONF_TPOT_FLAVOR=[STANDARD, SENSOR, INDUSTRIAL, COLLECTOR, NEXTGEN]
|
||
myCONF_TPOT_FLAVOR='STANDARD'
|
||
myCONF_WEB_USER='webuser'
|
||
myCONF_WEB_PW='w3b$ecret'
|
||
```
|
||
|
||
<a name="ews-cfg"></a>
|
||
## Optional: Custom `ews.cfg`
|
||
Enable this by uncommenting the role in the [deploy_tpot.yaml](openstack/deploy_tpot.yaml) playbook.
|
||
```
|
||
# - custom_ews
|
||
```
|
||
|
||
You can use a custom config file for `ewsposter`.
|
||
e.g. when you have your own credentials for delivering data to our [Sicherheitstacho](https://sicherheitstacho.eu/start/main).
|
||
You can find the `ews.cfg` template file here: [`openstack/roles/custom_ews/templates/ews.cfg`](openstack/roles/custom_ews/templates/ews.cfg) and adapt it for your needs.
|
||
|
||
For setting custom credentials, these settings would be relevant for you (the rest of the file can stay as is):
|
||
```
|
||
[MAIN]
|
||
...
|
||
contact = your_email_address
|
||
...
|
||
|
||
[EWS]
|
||
...
|
||
username = your_username
|
||
token = your_token
|
||
...
|
||
```
|
||
|
||
<a name="hpfeeds"></a>
|
||
## Optional: Custom HPFEEDS
|
||
Enable this by uncommenting the role in the [deploy_tpot.yaml](openstack/deploy_tpot.yaml) playbook.
|
||
```
|
||
# - custom_hpfeeds
|
||
```
|
||
|
||
You can also specify custom HPFEEDS in [`openstack/roles/custom_hpfeeds/templates/hpfeeds.cfg`](openstack/roles/custom_hpfeeds/templates/hpfeeds.cfg).
|
||
That file constains the defaults (turned off) and you can adapt it for your needs, e.g. for SISSDEN:
|
||
```
|
||
myENABLE=true
|
||
myHOST=hpfeeds.sissden.eu
|
||
myPORT=10000
|
||
myCHANNEL=t-pot.events
|
||
myCERT=/opt/ewsposter/sissden.pem
|
||
myIDENT=your_user
|
||
mySECRET=your_secret
|
||
myFORMAT=json
|
||
```
|
||
|
||
<a name="deploy"></a>
|
||
# Deploying a T-Pot :honey_pot::honeybee:
|
||
Now, after configuring everything, we can finally start deploying T-Pots!
|
||
Go to the [`openstack`](openstack) folder and run the Anible Playbook with:
|
||
`ansible-playbook deploy_tpot.yaml`
|
||
(Yes, it is as easy as that :smile:)
|
||
|
||
The Playbook will first install required packages on the Anible Master and then deploy a new server instance.
|
||
After that, T-Pot gets installed and configured on the newly created host, optionally custom configs are applied and finally it reboots.
|
||
|
||
<a name="documentation"></a>
|
||
# Further documentation
|
||
- [Ansible Documentation](https://docs.ansible.com/ansible/latest/)
|
||
- [Cloud modules — Ansible Documentation](https://docs.ansible.com/ansible/latest/modules/list_of_cloud_modules.html)
|
||
- [os_server – Create/Delete Compute Instances from OpenStack — Ansible Documentation](https://docs.ansible.com/ansible/latest/modules/os_server_module.html)
|
||
- [Open Telekom Cloud Help Center](https://docs.otc.t-systems.com/)
|
||
- [Open Telekom Cloud API Overview](https://docs.otc.t-systems.com/en-us/api/wp/en-us_topic_0052070394.html)
|