Feeds

Zombie tactics threaten to poison honeypots

Hive minds vs bot herders

Secure remote control for conventional and virtual desktops

Innovations in botnet technology threaten the usefulness of honeypots, one of the main ways to study how bot herders control networks of zombie PCs.

Computer scientists led by Cliff Zou and colleagues at the University of Central Florida warn that bot herders can now avoid honeypots - unprotected computers outfitted with monitoring software - set up by security firms.

Ethical concerns mean that security firms do not allow their infrastructure to be used in sending spam or running attacks against victims. By monitoring such instructions it's therefore possible for cybercrooks to program command and control servers to disable or simply ignore these machines, thus depriving security firms of vital intelligence in how zombie botnets are operating in the real world.

Zou and his team are working on techniques to make stealthier honeypot traps to trick bot herders. "Honeypot research and deployment still has significant value for the security community, but we hope this paper will remind honeypot researchers of the importance of studying ways to build covert honeypots, and the limitation in deploying honeypots in security defence," Zou said. "But all that effort will be for naught if honeypots remain as easily detectable as they are presently."

Preliminary findings from the Florida team's research were published in a recent edition of the International Journal of Information and Computer Security, as explained here.

Security and anti-virus firms say that the problem is already on their agenda.

Luis Corrons, PandaLabs technical director at Spanish anti-virus firm Panda Security, explained: "While you can and must filter the traffic generated by the bot inside a honeypot, you can filter and decide what will go out, and what does not. For example, if the bot herder is telling the bot to send spam, you can let the bot receive all the information, and even let him send out the spam messages but redirect them with a proxy to avoid it reaching any victims.

If the bot then contacts the Command and Control server to say the messages have been sent, you can let that info pass through, so the bot herder will think everything works fine.

There are some other ideas the bot herder could take, such as being one of the recipients to check that the spam is really being sent. In this case, there’s little that can be done from our side, as we won’t participate in letting threats spread.

Amichai Shulman, CTO at database security firm Imperva, suggested that rather than monitoring the behaviour of infected machines miscreants could instead attempt to identify virtual machines. "Most honeypot machines are based on a virtualisation platform (most often VMWare). By detecting this attribute of the infected platform, malware developers will probably be able to detect most honeypots out there,” he said.

While conceding that building a honeypot is tricky Shulman suggested a number of approaches designed to camouflage such systems from the eyes of cybercrooks:

Many Honeypot researchers are contemplating on the question of how to impersonate infected behaviour while not taking part in any evil, destructive activity.

I do think however that the problem described by the researchers is much exaggerated. There are many techniques that Honeypot developers employ that would make it very difficult for the malware / botnet to detect honeypot behaviour. Some examples include unlimited outbound communications for a relatively short period of time, deflecting outbound communications to known attack targets, outbound bandwidth control and outbound signature detection.

Most often the time of infection and the time when a recruited zombie becomes maliciously active are far apart, thus there is no need to immediately shutdown any outbound communications of the infected computer upon infection.

®

Remote control for virtualized desktops

Whitepapers

Designing and building an open ITOA architecture
Learn about a new IT data taxonomy defined by the four data sources of IT visibility: wire, machine, agent, and synthetic data sets.
The total economic impact of Druva inSync
Examining the ROI enterprises may realize by implementing inSync, as they look to improve backup and recovery of endpoint data in a cost-effective manner.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Business security measures using SSL
Examines the major types of threats to information security that businesses face today and the techniques for mitigating those threats.