This morning, there was yet another case of phishing that was reported by the New York Times. This phishing incident, Larger Prey Are Targets of Phishing, is interesting because of the victim demographics: executives of large companies. As I just learned, this is also referred to as whaling. We have all seen phishing emails that tried to lure us into logging into our PayPal account. But an email from the United States District Court in San Diego that has a very authentic look is a different story. Would you fall for it?
The best way to address phishing is to educate users to make sure they don’t give out personal information. Have a look at the AntiPhishing Working Group‘s phishing checklist that contains a lot of specific tips to prevent successful phishing attacks.
Splunk can addresses a couple of use-cases surrounding phishing attacks:
- Detecting, after the fact, whether someone in your company fell victim to the scam (phishing).
- Protecting your company from being phished. (In today’s story, the United States District Court in San Diego)
Detecting Phishing Victims
Once you know about a phishing attack, you can use Splunk to figure out whether anyone in your company has fallen victim. There are a few ways to do so, depending on the attack vector:
- The phish infects the victim and installs a trojan that starts leaking information.
- The phish uses a Web site to collect victims’ personal information (such as credit cards)
Both of these infections will start communicating with the outside. In the case of the phish reported today, the computers started communicating with machines in Singapore. By analyzing the traffic patterns and figuring out where in the world connections are being made to, this infection can be detected very easily. The Splunk reporting is a great way to quickly generate traffic reports and isolate traffic patterns based on geographic locations of the communicating machines. If , for example, your normal access pattern looks like the first graph and then after some time, you get the result of the second picture, where China suddenly shows up at second position, there might be something wrong.
Normal traffic patterns hitting Web site:
Suspicious traffic pattern hitting Web site. Note China on second position:
Protecting Your Company From Being Phished
If you are operating a Web site, you should try to make sure that there is nobody trying to phish it. There are a couple of ways that IT Search can help you with this:
- Monitor your Web server logs for non-complete session requests. A lot of phishers request images from your site, but not the original site itself (the HTML page).
- Monitor Web server logs for sessions that directly send a login, without ever requesting the login page itself. This happens when the victim logged into the phishing site and the credentials are passed to the real site, making everything look normal for the victim.
- Check DNS lookups and see whether you get a lot of lookups from one single machine. This is tricky and you need to know the baseline of lookups, but spikes might turn out interesting to investigate.
Here is a search in Splunk that you can use to determine whether someone posted credentials without ever requesting the login page:
sourcetype=access_comined (login_form.php OR sales.php) | stats count by clientip | search count=1
This assumes you have a page, sales.php, which you can only access once you logged in via the login_form.php. For more complicated Web site architectures, you will have to build a more sophisticated search that uses transactions, but more on that another time.
By Raffael Marty