Monday, August 22, 2016


This blog post is to walk through the Lab exercise from "" posted on Aug 18th 2016 .  And the focus is mainly on using pre-built 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. I have also used thug to analyse and pass on the domain analysis 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

Example of successful output:-
22/8/2016 -- 06:55:19 - <Notice> - This is Suricata version 3.1.1 RELEASE
22/8/2016 -- 06:55:26 - <Notice> - all 3 packet processing threads, 4 management threads initialized, engine started.
22/8/2016 -- 06:55:26 - <Notice> - Signal Received.  Stopping engine.
22/8/2016 -- 06:55:27 - <Notice> - Pcap-file module read 374 packets, 302575 bytes

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

Http Traffic
The below screenshot showing the http traffic happened during the infection

HTTP Traffic with sequence of events

Files Downloaded
Screenshots shows the fiels downloaded and its type

DNS Traffic

URL/ Domain Analysis with honeypot and feeding the json events into Splunk. 
Below screenshot shows the traffic for RIG EK

Below screenshot shows the traffic for the Gate