Build the Baseline Environment (Eagle Net)

Dante Rocca; Kyle Wheaton

45 Build the Baseline Environment (Eagle Net)

Dante Rocca and Kyle Wheaton

This section is for building a baseline environment. e.g., Your target. We’ll call it Eagle Network, The Eagle, or just Eagle for reference. It will contain many of the devices of a real network, but it will be abbreviated to save on host machine resources. You will need to create this enterprise network first before starting any of the attack labs.

Learning Objectives

Create a network to serve as a target for offensive cyber operations

Prerequisites

Deliverables

Four (4) Screenshots are required:
- GNS3 lab environment
- Kali box receiving an IP address
- Metasploitable3-Win box receiving an IP address
- Metasploitable3-Linux box receiving an IP address

Resources

N/A

Contributors and Testers

Mathew J. Heath Van Horn, PhD
Jacob M. Christensen, Cybersecurity Student, ERAU-Prescott

Phase I – Setting up the network

This lab provides students with a guide to creating a network containing vulnerabilities that can be exploited during a cyber attack. Much of this lab is directly from the DHCP Relay chapter. We highly recommend that once the GNS3 environment is complete, you save a master copy for reuse in future activities.

The goal is to create a network like this:

Figure 1 – Expected final result
Create the following virtual machines and add them to the GNS3 environment:

NOTE: Not every virtual machine (VM) is used in every lab. To conserve resources, consider replacing any unused machine with a Tiny Core Linux box. This device swap will still display live targets on scans, but it utilizes only 50 MB of memory instead of 2 GB.
1. TinyCore Linux in Chapter 5 – Installing Tiny Core Linux
2. Ubuntu Server VM with all add-ons in Chapter 7 – Create a Linux Server
3. Ubuntu Desktop in Chapter 11 – Create a Ubuntu Desktop
4. Kali VM in Chapter 12 – Create a Kali Linux VM
5. Both Metasploitable 3 (Windows and Linux) VMs in Chapter 13 – Create a Vulnerable Desktop VM
Configure the Ubuntu Server to handle DHCP requests
1. Modify the /etc/netplan/*.yaml on the DHCP server
  
  Figure 2 – Ubuntu Server netplan configuration
2. Modify the /etc/kea/kea-dhcp4.conf file on the DHCP machine
  
  ” Figure 3 – Ubuntu Server DHCP configuration
3. Ensure the daemon is active and running
  
  NOTE: As a reminder to:
  
  1. Start the service:
  
  > sudo systemctl start kea-dhcp4-server.service
  
  2. Restart the service:
  
  > sudo systemctl restart kea-dhcp4-server.service
  
  3. Start the service on system boot:
  
  > sudo systemctl enable kea-dhcp4-server.service
  
  4. Check service status:
  
  > systemctl status key-dhcp4-server.service
  
  5. Check the configuration for errors
  
  > kea-dhcp4 -t /etc/kea/kea-dhcp4.conf
  
  6. Check the system log for additional error messages
  
  > journalctl -xeu kea-dhcp4-server.service
Configure the router
1. Assign each interface on the router an IP address according to the following
  1. ether 1 – 150.150.150.1/24
  2. ether 2 – 100.100.100.1/24
  3. ether3 – 200.200.200.1/24
2. Disable the ether1 DHCP service
3. Configure the router as a DHCP relay for the Red and Blue networks
Check to make sure that everything is working properly
1. The attacker’s machine should receive an address from the 100.100.100.0/24 pool
2. The blue machines should receive addresses from the 200.200.200.0/24 pool