The files in this repository were used to configure the network depicted below.

/Diagrams/Cloud_Diagram.png

These files have been tested and used to generate a live ELK deployment on Azure. They can be used to either recreate the entire deployment pictured above. Alternatively, select portions of the filebeat-playbook.yml file may be used to install only certain pieces of it, such as Filebeat.

/Ansible/

This document contains the following details:

• Description of the Topologu
• Access Policies
• ELK Configuration
  • Beats in Use
  • Machines Being Monitored
• How to Use the Ansible Build

The main purpose of this network is to expose a load-balanced and monitored instance of DVWA, the D*mn Vulnerable Web Application.

Load balancing ensures that the application will be highly accesibele, in addition to restricting traffic to the network.

• Loadbalancers offer security and protection to the web servers. Preventing attacks such Denial of Service Attacks and/or a high flux in traffic to the web servers.

Integrating an ELK server allows users to easily monitor the vulnerable VMs for changes to the network and system checks.

• Filebeat helps you keep the simple things simple by offering a lightweight way to forward and centralize logs and file
• Metricbeat is a lightweight shipper that you can install on your servers to periodically collect metrics from the operating system and from services running on the server. Metricbeat takes the metrics and statistics that it collects and ships them to the output that you specify, such as Elasticsearch or Logstash.

The configuration details of each machine may be found below. Note: Use the Markdown Table Generator to add/remove values from the table.

The machines on the internal network are not exposed to the public Internet.

Only the Elk machine can accept connections from the Internet. Access to this machine is only allowed from the following IP addresses:

• 184..60.

Machines within the network can only be accessed by Jumpbox.

• Ansible containter. Public IP 104.210.54.105

A summary of the access policies in place can be found in the table below.

Ansible was used to automate configuration of the ELK machine. No configuration was performed manually, which is advantageous because...

• Perfom commands, updates, changes through the ansible container accross all the servers from one location.

The playbook implements the following tasks:

• Install Docker
• Install pip3
• Install Docker python module

The following screenshot displays the result of running docker ps after successfully configuring the ELK instance.

This ELK server is configured to monitor the following machines:

• TODO: List the IP addresses of the machines you are monitoring

We have installed the following Beats on these machines:

• TODO: Specify which Beats you successfully installed

These Beats allow us to collect the following information from each machine:

• TODO: In 1-2 sentences, explain what kind of data each beat collects, and provide 1 example of what you expect to see. E.g., Winlogbeat collects Windows logs, which we use to track user logon events, etc.

In order to use the playbook, you will need to have an Ansible control node already configured. Assuming you have such a control node provisioned:

SSH into the control node and follow the steps below:

• Copy the _____ file to _____.
• Update the _____ file to include...
• Run the playbook, and navigate to ____ to check that the installation worked as expected.

TODO: Answer the following questions to fill in the blanks:

• Which file is the playbook? Where do you copy it?
• Which file do you update to make Ansible run the playbook on a specific machine? How do I specify which machine to install the ELK server on versus which to install Filebeat on?
• _Which URL do you navigate to in order to check that the ELK server is running?

As a Bonus, provide the specific commands the user will need to run to download the playbook, update the files, etc.