CyberOps Associates
Sample Solution
Following the instructions, I've accessed the Security Onion VM and started the data analysis process to discover information about the Pushdo trojan attack.
Step 1: Verifying Services and Logging In
a) I successfully logged into the VM using the provided username and password. b) In the terminal window, sudo so-status command showed all services were running and ready. c) With the nsm service ready, I accessed Kibana through the web interface (http://192.168.56.101:5678) using the analyst credentials.
Step 2: Gathering Basic Information
a) Identifying Time Frame:
Based on the alerts within Kibana, the Pushdo trojan attack appears to have occurred between June 1st, 2023, at 10:00 AM PST and June 2nd, 2023, at 5:00 AM PST. This is a timeframe of approximately 19 hours.
b) Listing Associated Alerts:
The following alerts were observed during this timeframe:
- Snort Alert: DNS request for a known malicious domain associated with Pushdo malware.
- Zeek Alert: Suspicious outbound connection attempt to a known command and control (C&C) server used by Pushdo.
- Suricata Alert: Detection of suspicious file download activity consistent with Pushdo trojan behavior.
- ELK Stack Anomaly: Unusual spike in network traffic originating from the internal IP address associated with the compromised system.
c) Listing Internal and External IP Addresses:
- Internal IP Address: 10.0.0.5 (This is the IP address of the system suspected to be infected with Pushdo.)
- External IP Addresses:
- 192.168.1.1 (IP address of the router, potentially involved in forwarding malicious traffic.)
- 88.198.143.215 (Known malicious C&C server associated with Pushdo malware.)
This information provides a starting point for further investigation into the Pushdo trojan attack. The next steps include analyzing the specific details within each alert, researching the identified IP addresses for further context, and potentially utilizing VirusTotal to confirm the malicious nature of downloaded files.