Proj 1x: BOSS OF THE SOC: Finding Attack Servers (35 pts)

What You Need for this Project


To practice threat hunting, using the Boss of the SOC (BOTS) Dataset.

This project uses only the stream:http data.

Connecting to My Splunk Server

Go here:

Log in using these credentials, as shown below.

Once you are logged in, at the top left, click "Search & Reporting", as shown below.

The "Search" page opens, as shown below.

Exploring the BOTS Data

Sampling the Data

Do these steps: The search finishes within a few seconds, and finds approximately 9,452 results, as shown below. (The number varies because the sampling is random.)

There are actually 100x as many events, but we are only looking at 1% of them for now.

Viewing Sourcetypes

On the lower left, in the "SELECTED FIELDS" list, click the blue sourcetype link.

A "sourcetype" box pops up, showing the "Top 10 Values" of this field, as shown below.

Notice these items:

XmlWinEventLog:Microsoft-Windows-Sysmon/Operational    "Sysmon", a Windows monitoring tool from Microsoft
stream:smb,stream:ip,stream:tcp,stream:http "Splunk Stream", which monitors live network traffic
suricata The Suricata Intrusion Detection System (IDS)
wineventlog and WinRegistry Windows OS
fgt_traffic and fgt_utm Fortigate firewalls
Note: because the sampling is random, you may see different items near the bottom of this list.

Viewing stream:http Events

In the "sourcetype" box, in the "Top 10 Values" list, near the bottom, if it is visible, click stream:http

Splunk adds

to the search and finds approximately 252 results, as shown below.

If there is no stream:http item in the list, just type it into the query.

Scroll down to examine the most recent event. Splunk has parsed this event into many fields, shown in red, including c_ip, the client IP address, as shown below.

These fields are explained here.

Viewing HTTP Events for

In the Search box, at the right end, add this text:
251 events are found, as shown below. (The sampling is random, so you may not see the exact events shown below.)

Scroll through the first few events found, and note these items, highlighted in the image below.


Find these items. Use the forms below to record your score in Canvas.

If you don't have a Canvas account, see the instructions here.

1x_1: Scanner Name (5 pts)

Find the brand name of the vulnerability scanner, covered by a green box in the image above.

If your name is not found, make account on my Canvas server as explained here.

Name or Email:
Brand name:

1x_2: Attacker IP (5 pts)

Find the attacker's IP address.
Name or Email:
Attacker IP:

1x_3: Web Server IP (5 pts)

Find the IP address of the web server serving "".
Name or Email:
Web Server IP:

1x_4: Defacement Filename (10 pts)

Find the name of the file used to deface the web server serving "".

HINT: It was downloaded by the Web server, so the server's IP is a client address, not a destination address.
Remove the filter to see all 9 such events. Examine the uri values.

Name or Email:
Defacement Filename (like foo.gif):

1x_5: Domain Name (10 pts)

Find the fully qualified domain name (FQDN) used by the staging server hosting the defacement file.

HINT: Examine the 9 events from the previous challenge. Look at the url values.

Name or Email:
FQDN (like

Posted 2-9-19