Using Enterprise Security to find Malware

Enterprise Security provides statistics and interesting events on security domain specific dashboards. Using the dashboards together, you can build a workflow for investigating threats by reviewing the results, isolating the events that require attention, and using the contextual information provided to drill down into the issue.

Prerequisites

• Verify that a Splunk platform instance with Splunk Enterprise Security is installed and configured.
• Verify that logs from an IDS/IPS tool, web proxy software or hardware, and/or an endpoint security product are indexed on a Splunk platform instance.

The Security Posture dashboard

Begin by reviewing the Security Posture dashboard. The dashboard represents a summary of all notable event activity over the last 24 hours. A notable event is the result of a security-oriented correlation search that scans the indexed logs until a match is found. When a notable event is created, it represents a potential issue or threat requiring a review and, depending upon the outcome of the review, an investigation.

On any given day, there might be 10's or 100's of notable events represented on the Security Posture dashboard. Use the urgency field to determine which issue needs your immediate attention.

In the Notable Events Over Time panel, you see a spike in activity labeled "endpoint." The endpoint domain represents host based security, so you know there was a large spike in suspicious activity on the network hosts. In the Top Notable Events panel, you see the count of notable events sorted by the correlation search name.

The panel shows that the number of Host With A Recurring Malware Infection notable events had a sudden spike. To drill down into those numbers, select the peak count on the sparkline to open another browser window and drilldown to the Incident Review dashboard.

Working in Incident Review

Use the Incident Review dashboard to find, assign, analyze, and update notable events. Because the link to Incident Review was initiated from another dashboard panel, the Incident Review dashboard opens with a search for Host With A Recurring Malware Infection notable events and scoped to a narrow timeframe.

Prioritize the task

The search for Host With A Recurring Malware Infection ranges over several Urgency levels. The event urgency is calculated based on the priority assigned to a host or asset and the severity assigned to the correlation search.

1. Start the investigation by looking at the notable events labeled Critical.

2. Remove other notable events from the view by deselecting all other Urgency levels until only Critical remains.

3. Click Submit.

The Incident Review dashboard displays only the two Critical notable events that were created for a Host With A Recurring Malware Infection.

Task assignment

Assigning notable events begins a record of activity that you can use for notes and time tracking, and lets other analysts know that an issue is being investigated.

1. Assign the notable event to your user account.

2. Use the check box to select the first notable event.

3. Click the Edit all matching events link on the top left of the table view.

4. Change the Status field to In Progress, and assign your user as the Owner.

5. Update the Comment field as required by your company security policy.

6. Click Save changes to return to the Incident Review dashboard.

Notable event review

The Description field is a summary of the conditions a correlation search must find for you to create a notable event.

1. Click the arrow next to a notable event to expand the view and display the details of the notable event.

2. Review the information provided with the notable event.

Each notable event has a selection of fields that provide contextual information about the issue. The fields are populated with data correlated from the logs of one or more data sources and asset and identities collections.

3. Review several fields for history about the host or hints of activity. The Urgency assigned to this notable event was partially calculated from the priority assigned to the host.

4. Begin the investigation into the unknown malware by investigating the Destination IP address. Click the arrow next to the Destination field to initiate a field action. A field action initiates a new search on another dashboard in Enterprise Security, using the selected field as a filter. This technique helps you to maintain context while opening multiple dashboards or using views during an investigation.

5. In the field action menu, select Asset Investigator.

A new browser window opens to the Asset Investigator dashboard and begins a search on the selected Destination IP address.

Working in Asset Investigator

The Asset Investigator dashboard displays data about one asset or host collected and grouped by a common threat category. Each category is represented as a named row of data called a swim lane.

Each swim lane has a collection of data points called candlesticks. The event count within a candlestick is represented through a heat map. The brighter the color, the higher the event count.

You can see there is a large number of malware related events attributed to this host. If you see too many events in one category, use the time sliders to focus the view down to the time frame where the notable event was triggered.

At this point, you can follow any number of malware events related to this host. The investigation began with reporting an unknown malware attack. Use the Malware Attacks swim lane to select a candle stick and review the common fields using the Event Panel.

Find the event

1. In the Malware Attacks swim lane, select a candle stick.

2. In the Event Panel find an event marked with a signature of unknown.

3. Click the Go to Search icon to open another browser window to drilldown and search on the selected Destination IP address.

Drilldown to log events

Review the New Search dashboard. The search dashboard is still in Enterprise Security context, as marked by App: Enterprise Security in the top left corner. This mode ensures that the field values, aliases, and other field categories supplied with ES will apply when raw log events are searched from this dashboard.

Examine the drilldown search in the search bar. The process begins by identifying the datamodel | `datamodel ("Malware","Malware_Attacks")` before calling the normalized host value for the Malware data model | search ("Malware_Attacks.dest="x.x.x.x"). A datamodel search command searches the indexed data over the time frame, filters the results through the malware data model constraints, and returns any matches.

Enterprise Security does not use accelerated data models for drilldown searches, so it is important to set a time range for faster results. The Malware_Attacks.dest represents the dest_ip field reference in the malware data model.

Identify relevant fields

You can see that the raw event has a lot of information to process. Let's begin by looking at common fields, such as dest_ip, source, and sourcetype. Reviewing these fields, you see that the dest_ip references an internal IP address range. Searching your network device inventory system might tell you what that host or dest_ip represents.

The source and sourcetype identify the events as sourcefire data. After confirming the dest_ip represents a proxy server device, you know that the src_ip field represents other hosts on the internal network accessing data through the proxy.

This event also contains web_app and uri fields. These fields represent traffic from a web browser to a site requesting a download. Let's review which fields in the source logs are relevant, and why.

Field	Description
src_ip	Represents internal network hosts.
dest_ip	Another internal host that was discovered to be a proxy.
uri	A record of what is being requested by the hosts.
web_app	The browser used.

You know that the Critical notable event represents an unknown malware signature being passed through the proxy server into your network. As you progress through the investigation and followed data flows and requests, you created a list of the key fields relevant to the threat. Because a number of malware downloads are reported by the proxy, expand the search to find the internal hosts that are responsible.

Review a broader timespan of events

Broaden the search by widening the time range and search again.

1. Select the Date time range button.

2. Lower the Earliest time field to the top of the hour.

3. Raise the Latest field to the next hour.

4. Click Apply to keep the changes.

5. Click Search.

The search page now shows many similar events that passed through the proxy.

The search view displays many more events, but is impractical for summarizing the data by important fields. Changing the search to a table view lets you retain the important fields and reduce the visual clutter. A table can also provide a reference because the results can be exported for reporting.

To view a table of the events sorted by the two most relevant fields, use the search bar to add | table src_ip uri to the end of the existing search string and click search again.

On the first page of results, you see a number of common download requests. The .swfl files represent shockwave flash content. Because shockwave is a commonly exploited framework used to run malicious code or exploits, review the uri fields that describe a shockwave download.

There are a number of ways to further search and sort the uri fields based upon a file extensions or a string match. There is a suspicious looking domain that is providing a shockwave file on the first page. Let's determine whether the host receiving this file was reporting issues or downloading other suspicious content.

Find an exploited host

On the table of results, select a src_ip field in an event referencing a downloaded shockwave file.

1. Click the src_ip field.

2. Select New search.

A new browser window opens to a search dashboard and begins to search on the selected src_ip field over the time range.

From the results, you can see additional alerts about this host from other log sources, implying that the specific src_ip is being targeted with multiple forms of attacks. There is a chance that this host has downloaded an exploit from an Internet domain.

3. Examine the uri and file_name fields for the host.

a. Review the data in a table format to give you a view of the important events.

b. Use the search bar to add | table uri file_name to the end of the existing search string and select search.

c. Sort the table by selecting the uri field.

As you review the results, you can see that a number of executable files were downloaded from the same domains.

At this point, quarantine the infected host based upon the data collected. More information is contained in the proxy logs, such as the domain being used to download the suspicious files. Digging deeper into those logs can provide information to use in active remediation.

Pivot on the host to find files or domains

On the table of results, select a uri field in an event that references a suspicious domain.

1. Click the uri field.

2. Select New search.

A new browser window opens to a search dashboard and begins searching on the selected uri field over the time range.

By modifying the search, you can show the count of events and hosts communicating with the domain.

1. On the search bar, update the search string and add a wildcard to return all matches on the domain name, for example, uri=*makerealashnow.com*.

Widen the time range to broaden the search

1. Click Date time range.

2. Select the Last 24 hours option and click Search.

You can see that the total count of events reaching out to this domain over the last 24 hours is high. A review of the src_ip field on the field picker displays a count of the unique hosts attempting a connection to this domain. A number of hosts will require active scanning for malware. A report of all hosts receiving downloads from this domain is a useful resource.

Create reports of the results

Let's review the data in a table format.

1. Use the search bar to add | table src_ip uri file_name to the end of the existing search string.

2. Select Search.

The results are a list of potentially infected hosts including suspicious file names that can be delivered to the endpoint administrator for immediate action.

You can export the results to place into a report or an email attachment.

3. Click the Export button.

4. Update the File Name field and save the results in a .csv format.

5. Click Export to download the results.

6. (Optional): To save a report, click Save As and choose Report.

7. Fill in the required fields, and write a summary of the report for the Description field.

8. Click Save to write the report to the search head. The report is private, and available only to the creator by default.

Update the notable event

Before you perform any additional analysis, update the notable event on the Incident Review dashboard. Record any objects or reports that are created, and other actions required to process and close the notable event.

Use the report results for reference and investigation. You can deliver the .csv of hosts and file names to the team monitoring the endpoints.

Malware discovery summary

Using the data provided by the proxy server, Splunk Enterprise Security created notable events when hosts requested downloads from a suspicious domain. The notable events provided a starting point for investigation and included the most relevant fields to examine. By sorting the data and pivoting on those fields, a collection of reports is generated that exposed the internal hosts involved, domains that might be blacklisted, and common file names that the malware runs as. As the remediation begins, the investigator has all of the critical information to act on the threat.