Botnets, vast armies of compromised, robot-like machines, are massing on the digital frontier, waiting for their masters' command to attack.
These hacker-controlled networks -- some numbering in the hundreds of thousands of machines -- are the fastest-growing menaces on the Internet. They have powerful weapons -- overwhelming DDoS attacks, untraceable spam relays and ubiquitous malware distribution. When unleashed, they deliver punishing blows that devastate their targets.
Hackers, malware writers and organized crime groups love bots -- the foot-soldier programs infecting PC networks -- for their power and cloaking abilities. Some bots, such as Agobot and Phatbot, have characteristics similar to Trojans and rootkits, opening back doors to systems and giving attackers control over compromised machines. Attackers only require rudimentary programming knowledge to create and control a botnet army.
Botnet commanders can start with just a handful of compromised computers that are mustered manually by sending targeted, virus-laden e-mails to broadband/DSL users, vulnerable enterprise desktops and mobile machines. Some bot-carrying worms will even patch the vulnerability they exploited. Infected hosts automatically show up in a preprogrammed IRC channel, where they sit in a virtual holding pattern until dispatched. Attackers can "herd" their bots from channel to channel, sifting out the low-bandwidth connections to maximize the machines with the best throughput.
Their ubiquity, power and ease of use make them looming threats on both sides of the enterprise firewall. Understanding botnets will help enterprises defend against in-filtration and, perhaps, survive an invasion (See, Evolution: Rise of the bots).
Enterprises face botnet threats on two fronts: Attackers are trying to compromise their machines and use them for malicious purposes (a breach of integrity) or coordinated attacks such as DDoS (risk of downstream liability).
Once the computer is compromised, bots need to "phone home" to their controller. Generally, this is done through a private channel on a public IRC server or network, with communications running in the clear over the default TCP port 6667. (A prudent botnet defense is blocking and monitoring outbound TCP 6667 traffic.) Also, attackers can use IRC protocols to communicate instructions to their bots.
Attackers can use the bots and their hosts for a variety of purposes, some seemingly innocuous to the compromised enterprise. For instance, botnets have become the distribution method of choice for spam and phishing attacks. According to e-mail security service provider MessageLabs, nearly 70 percent of all spam and phishing e-mails now originate from botnets. Tracing these attacks is difficult due to the many layers between the source machines and the attacker.
Botnets are the ideal mechanism for unleashing malware. Conventional worms are released from a single point and can take hours to circle the globe. Worms released from botnets can appear from multiple points simultaneously without warning, giving enterprises and AV vendors little time to react. Last spring's lightning-quick Witty worm was launched from a relatively small botnet of 4,200 nodes.
The more visible and devastating attack type is the DDoS attack. More than just simple SYN floods, botnet-controlled DDoS attacks can flood a network with seemingly legitimate requests, clogging the pipes, overloading services and denying all legitimate traffic. A moderate-sized botnet could completely disable Web, mail and VoIP communications; a DDoS attack directed at your DNS server could make your enterprise disappear from the Internet.
Your enterprise will most likely become aware of a botnet infiltration through user reports of performance issues; third-party reports of attacks originating in your IP address space; victims' reports of DDoS floods; and the detection of high inbound and outbound scanning, outbound flooding or traffic passing through hosts that should be acting like desktop clients.
To stay ahead of botnets, you need stay current with prevention tools and techniques (e.g., proactive vulnerability scanning, patch management, appropriate use of firewalls and VPNs, user education, and policy enforcement). You also need to have sufficient computer forensics and incident response capabilities to adequately deal with compromises when they occur, and to return compromised machines to a trusted state as quickly as possible.
But, there's no effective defense for a botnet attack -- your only hope is survival (See, Lifecycle: Preventing, detecting and removing bots).
Anticipating bot attacks
Before you connect to the Internet, there are some things you can do to mitigate the effects of botnet attacks. The following are some prudent steps all enterprises should consider:
Define service requirements with ISPs. You should define for your ISP what your expectations and response requirements are in the event of a DDoS attack. This includes network address agility (or switching your address block), which makes it harder to target your network and can reveal attacker reconnaissance; topological changes to compartmentalize your network, protect high-value assets and preserve connectivity to specific network segments; and traffic capture and analysis for tracing attacks and -- perhaps -- prosecuting attackers. Traffic filtering by your ISP or upstream traffic sources (sometimes called traffic blocking or null routing) can also help.
Manage out-of-band network. When your primary (or secondary) network interfaces are flooded, you may lose all ability to communicate with your network devices. If your provider can establish an out-of-band control mechanism -- be it a network connection through a peering point or a DSL line to a terminal server within your network perimeter -- you can regain remote access and reroute critical traffic, such as e-mail, even if your main network paths are unavailable.
Coordinate with peers. Cases of DDoS attacks that involve source-address forgery and traffic reflection off widely distributed servers (e.g., DNS reflection, SYN-ACK reflection off routers and firewalls) may require manual traceback to determine the source. Getting the cooperation of peers using the same upstream provider to block traffic and perform traceback may be very difficult; persuading your upstream provider to commit to working with you, even if the problem is difficult, is the first step.
While not fully effective against botnet DDoS attacks, several open-source and commercial products can provide some measure of response capabilities. Each has some value, but is only one soldier in the information assurance/availability army.
Most defenses are directed at either the host or network level, but rarely both. Host-level defenses, including personal firewalls, antivirus and host-based IDSes, are designed to protect computers, OSes and applications, and to detect and possibly contain intrusions.
Commercial applications from Arbor Networks, Captus Networks, Cisco Systems, Lancope, Mazu Networks and Top Layer identify anomaly traffic and irregular volume flows to detect DDoS attacks. These same applications have had some success in filtering floods by dropping traffic based on source IP address and protocol. But, their success is limited by the size and scope of a botnet flood. DDoS attacks, especially those launched via massive botnets, have a numerical advantage that may overwhelm these tools.
Security solutions that maintain the trusted state of machines, such as those from Tripwire, can monitor deviations in configurations. When a machine falls out of compliance, it can be rapidly detected and restored to a trusted state.
Network-level defenses focus on large sets of computers on a network or routing infrastructure. They may monitor individual or aggregate traffic flows between computers looking for anomalous activity, filter suspicious traffic, manage device configurations or patch systems to prevent exploitation.
Being a good 'netizen
Botnets are marauders waiting at the edge of every network for the one vulnerable machine that will become their key through enterprise fortifications. And, eradicating botnets after an invasion is nearly impossible because their numbers and growth are too great to effectively eradicate.
Only through vigilance and best practices will enterprises stay ahead of, or at least keep pace with, the botnet threat.
- Learn these five steps for beating back the bots.
- Listen to David Dittrich's webcast to learn how to respond to botnet attacks.
- Review these resources for tips on rooting out compromised machines and safeguarding your network from botnet attacks.
About the author
David Dittrich is an Information Assurance researcher at the University of Washington Information School, and has over 20 years of programming, system administration and information security-related experience. Dittrich is also a founding member of the Honeynet Project and co-author of "Internet Denial of Service: Attack and Defense Mechanisms."
Note: This article originally appeared on Information Security magazine.