FireEye and SolarWinds Cyber Attack: Information for Exabeam Customers and Partners

By now you’ve heard of the supply chain attack on the SolarWinds Orion Platform, made public by FireEye on December 8, 2020. FireEye, U.S. governmental agencies, and other global entities were all involved in this highly-sophisticated attack. As a cybersecurity vendor, we know how hard it is when a breach happens – especially one perpetrated by a well-funded, state-sponsored actor. Like all cybersecurity vendors, we’re committed to helping our customers secure their organizations and address security incidents. FireEye has quickly addressed this breach and provided much information on steps for detection and remediation.

We just released new detection rules specific to this attack which customers can access through their Community page. As always Exabeam is here to support you. Our OOTB capabilities can be used to help identify similar incidents in your environment.

Information for Exabeam customers and partners

Based on information that FireEye has shared on “Post Compromise Activity and Detection Opportunities,” here is how parts of the attack unfolded.

“The attacker used multiple IP addresses per VPS provider, so once a malicious login from an unusual ASN is identified, looking at all logins from that ASN can help detect additional malicious activity. This can be done alongside baselining and normalization of ASN’s used for legitimate remote access to help identify suspicious activity.”

Exabeam take: The attacker optimized their IP addresses based on the victim’s country. This was done to avoid detection. We recommend finding the first and abnormal activity from the ISP. 

“Once the attacker gained access to the network with compromised credentials, they moved laterally using multiple different credentials. The credentials used for lateral movement were always different from those used for remote access.”

Exabeam take: Lateral movement using different credentials is a technique of the attack. As accounts were switched in this attack, using lateral movement rules will help with tracing the timeline of the attack. 

Here is MITRE’s guidance on lateral movement detection:

Correlate use of login activity related to remote services with unusual behavior or other malicious or suspicious activity. Adversaries will likely need to learn about an environment and the relationships between systems through discovery techniques prior to attempting lateral movement.

“DGA and Blocklists: The backdoor determines its C2 server using a Domain Generation Algorithm (DGA) to construct and resolve a subdomain of avsvmcloud[.]com. The Update method is responsible for initializing cryptographic helpers for the generation of these random C2 subdomains.”

Exabeam take: We have a number of DGA-related rules for customers to use that auto-detect DGAs, e.g. “cnn[.]com” compared to “xhibfwda[.]com“. We group this with other granular, contextual information so you can investigate in a comprehensive manner. DGA is one of Exabeam’s contributions to the ATT&CK framework that has been accepted by MITRE as T1483. This technique was cited in FireEye’s list of observed MITRE ATT&CK techniques.

In HTTP Command and Control (C2) Communication/Data Exfiltration, “The HTTP thread begins by delaying for a configurable amount of time that is controlled by the SetTime command. The HTTP thread will delay for a minimum of 1 minute between callouts. The malware uses HTTP GET or HEAD requests when data is requested and HTTP PUT or HTTP POST requests when C2 output data is being sent to the server. The PUT method is used when the payload is smaller than 10000 bytes; otherwise the POST method is used.”

Exabeam take: The varying delay between calls means you can’t build a correlation rule for this. But data exfiltration could be detected in the abnormal amount of data being sent outbound using the HTTP protocol. Exabeam gives you visibility into abnormal amounts of data uploaded to the web in HTTP GET requests as you conduct your investigation.

Keeping your network safe

If you think you may have been affected in a similar way, here are the known attacker techniques according to FireEye’s reporting. Below you will find the Exabeam detections for these known TTPs.

We’re here for you

Customers can now access new detection rules specific to this attack through their Community page. We have also released a saved searches package for this breach for Data Lake. Exabeam is here to partner with your organization to help you meet your security needs. If you have any cybersecurity-related questions or just want to talk with a security expert about this or any other security concerns, don’t hesitate to reach out.