Monday, August 29, 2016


This blog post is to walk through the Lab exercise from "" posted on Aug 26th 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

HTTP Requests to malicious domains

HTTP Traffic with flow of information

HTTP Traffic in Wireshark

Files Downloaded

Post infection traffic

Malicious Executable analysis

PE info - Sections

Threat Intelligence on the IOC shows various submission and hits on VT and Malshare sites.


Threat Intelligence on the IOC -