Wednesday, August 24, 2016


This blog post is to walk through the Lab exercise from "" posted on Aug 23th 2016 .  And the focus is mainly on using Splunk tool to detect  and observe the behavior. Suricata is used as the NIDS engine with ET signatures.  Wireshark is used to further observer the payload. And honey client THUG to analyse and pass on the output to Splunk.



The set-up is to run the like Suricata (IDS), Wireshark and honeypot inside the separate instance for analysis and used a Splunk universal forwarder to transport the logs to Splunk Core instance. Follow the below post for Suricata install and configure to transport the logs-to splunk

Suricata -c suricata.yaml - r input_pcap_file_location -l output_location_to_store_the_logs

Suricata's output eve.json file contains various event_types, segregating the activities to alert, dns, fileinfo, flow, http, stats, tls. This is very useful in identifying the malicious events. Once the traffic is loaded into Splunk and viewed inside  the suricata dashbaord, i can straightawaypot some domains and files downloaded that looks out-of-normal.

Alerts raised by the NIDS

High level Traffic information with types of files

The below screenshot showing the http traffic happened during the infection

HTTP Traffic with sequence of events

Files Downloaded
Screenshots shows the files downloaded and its type

Iframe injection

Threat Intelligence for the indicator shows the following hits