In Part 3
of the Active Directory Project, we’ll install and configure Sysmon and Splunk Universal Forwarder to collect and forward telemetry data from our Windows target machine and server to the Splunk server. By the end, both machines will be sending security, system, and application logs to Splunk, preparing our environment for active monitoring and analysis.
-
Splunk Account
Ensure you have a Splunk account and have downloaded the Splunk Enterprise DEB package and Splunk Universal Forwarder. -
Network Configuration
Verify your virtual machines are set to the same NAT Network and have static IPs assigned as per your network diagram.
- Open VirtualBox, go to File > Host Network Manager.
- Select NAT Network and configure the IP range, using the same prefix as your lab diagram.
- Apply the network to each VM (Splunk server, target machine, etc.) under Settings > Network.
- On the Splunk VM, set a static IP using:
sudo nano /etc/netplan/00-installer-config.yaml
- Specify IP settings matching your diagram, and apply changes with:
sudo netplan apply
- Transfer the DEB package to the Splunk VM and install:
sudo dpkg -i splunk-package.deb
- Set up admin credentials and configure Splunk to auto-start.
- Download Sysmon and Sysmon configuration file (e.g., from Olaf Hartong’s GitHub).
- Open PowerShell with admin privileges, navigate to the Sysmon executable location, and run:
.\sysmon.exe -accepteula -i sysmonconfig.xml
-
Install Splunk Universal Forwarder on the Windows target machine.
-
Configure the
inputs.conf
file under:C:\Program Files\SplunkUniversalForwarder\etc\system\local\inputs.conf
-
Specify the IP and port of the Splunk server (e.g.,
9997
for forwarding logs) and save. -
Restart the Splunk Forwarder service.
By completing Part 3, you now have:
- Sysmon and Splunk Forwarder installed on your Windows machines
- Telemetry Collection configured to gather logs for security, system, and application events
- Splunk Server receiving and indexing logs from each configured machine
In Part 4, we’ll dive into installing and configuring Active Directory to establish our domain environment.