Is your company prepared for a DDOS attack?
Discussion
jammy_basturd said:
Considering the list of high-profile websites that have been taken down as a result of DDOS attacks, I don't think there is much someone like you or I could do!
I wondered that but it did seem there were things that could be done such as filtering certain IPs out if you know they aren't genuine? (I did some very, very basic googling.)There's only so much that can be done to restrict a DDOS attack on any site. More often than not, there will be thousands of unique IP addresses making the requests so the toolkit that the everyday business will need would be pretty prohibitive in terms of cost. All being well, hosting in a respectable datacentre will give you the protection you need (whether this be physical, the 'cloud' or whatever).
Whilst I don't really know the complex inner workings of how a CDN works, as far as I'm aware the basic definition is that they're just a network of web servers around the world serving up static resources (images, CSS, etc). So a DDOS can still overload a CDN as they're still just web servers.
Technically you can still apply the same to a CDN, but the good ones have the distributed servers and available bandwidth to suck up several 100Gbps of traffic, the monitoring to detect attacks and the expertise to improvise against specific attacks. IIRC Amazon EC2's CDN bandwidth costing used to be the same as direct traffic making it an easy choice to enable.
It seems meetup.com are now working with Cloudflare to resolve it.
It seems meetup.com are now working with Cloudflare to resolve it.
It depends on the DDOS. Sheer volume is hard without some fairly expensive kit, or a service provider who offers that service. Attacks based on web server vulnerabilities are easier in one way (firewalls, good config and patching) but may be harder to identify. Without a DDOS mitigation service, using a big hosting company will often end up with your server(s) being blackholed while the support team work with other ISPs to kill the source of the attack. The worst I've seen took some days to finally kill off, and started on Christmas Day which wasn't fun.
If you're a larger company, or asset rich online, you need to use Akamai's services (www.akamai.com), their online platform handles around 35% of all web traffic and they protect various intel agencies, banks and other businesses from DDoS attacks. Those guys can't be wrong.
Otherwise some service providers use their services so you can check if yours does.
Otherwise some service providers use their services so you can check if yours does.
Hoofy said:
How do you kill the source?
All the ISPs have teams (or key individuals) that deal with DDOS attacks, and they talk to each other to initially identify regions or specific ISPs that the bulk of the DDOS originates from. Often these are in Russia... Then they can find blocks of IP addresses or specific routes to blackhole, and eventually the source ISP will take down the connection to the individual source. The other method (which can be used at the same time) is to blackhole traffic to the destination, or route it down a sacrificial connection, so moving the traffic away from other customer systems. Then it can be rate shaped, cleaned (if you've paid for Arbor or something similar) and analysed.
mr_spock said:
All the ISPs have teams (or key individuals) that deal with DDOS attacks, and they talk to each other to initially identify regions or specific ISPs that the bulk of the DDOS originates from. Often these are in Russia... Then they can find blocks of IP addresses or specific routes to blackhole, and eventually the source ISP will take down the connection to the individual source.
The other method (which can be used at the same time) is to blackhole traffic to the destination, or route it down a sacrificial connection, so moving the traffic away from other customer systems. Then it can be rate shaped, cleaned (if you've paid for Arbor or something similar) and analysed.
Ah! Makes sense.The other method (which can be used at the same time) is to blackhole traffic to the destination, or route it down a sacrificial connection, so moving the traffic away from other customer systems. Then it can be rate shaped, cleaned (if you've paid for Arbor or something similar) and analysed.
I read somewhere that it's getting more difficult as mobile devices are starting to be able to be used for DDOS?
The only way to mitigate the effect of a dDoS attack is to use a network provider with massive capacity and automated tools which identify traffic anomalies and automatically block it. Companies like Akami and Prolexic do this but it's very expensive. Cloudflare offer a cheaper service, a half way house perhaps but it's still not cheap for a small business.
The main problem for a lot of smaller businesses is that they host their web sites or systems in data centres with small capacity connections to the Internet - mentioning no names it's common to see connections at 100MBit/sec to the Internet from some smaller web hosting companies and it obviously doesn't take much to swamp 100 meg. Even some data centres often only have a couple of 10 gig links or one 10 gig and one 1 gig and these again are frequently swamped by dDoS attacks. Gaming companies are usually the recipient but the traffic volume affects everybody else in that data centre for a while until the traffic is isolated.
The larger data centre operators and network providers have much bigger connections to the Internet but often won't tell you exactly what they have, preferring to "suggest" they have more than they do or that it's "adequate".
One indicator for smaller companies is the peering connections a company has at LINX, the London Internet Exchange. https://www.linx.net/pubtools/member-techlist.html shows you how many connections and what speed a particular company has. They may have additional private peering connections and connections to other exchanges too so this doesn't mean that XYZ Ltd only has one connection as that's all that's shown above but it is a good indicator - look at Akami and Prolexic in particular.
The main problem for a lot of smaller businesses is that they host their web sites or systems in data centres with small capacity connections to the Internet - mentioning no names it's common to see connections at 100MBit/sec to the Internet from some smaller web hosting companies and it obviously doesn't take much to swamp 100 meg. Even some data centres often only have a couple of 10 gig links or one 10 gig and one 1 gig and these again are frequently swamped by dDoS attacks. Gaming companies are usually the recipient but the traffic volume affects everybody else in that data centre for a while until the traffic is isolated.
The larger data centre operators and network providers have much bigger connections to the Internet but often won't tell you exactly what they have, preferring to "suggest" they have more than they do or that it's "adequate".
One indicator for smaller companies is the peering connections a company has at LINX, the London Internet Exchange. https://www.linx.net/pubtools/member-techlist.html shows you how many connections and what speed a particular company has. They may have additional private peering connections and connections to other exchanges too so this doesn't mean that XYZ Ltd only has one connection as that's all that's shown above but it is a good indicator - look at Akami and Prolexic in particular.
I beg to differ a little. Having a small sacrificial connection to an upstream provider or (preferably) a peering point and advertising a specific route to divert inbound traffic down that link will, at least, protect other customers from a targeted DDOS on a specific host. If the DDOS is aimed at your host, then yes, a scrubber will help a bit if it's a volume attack, but an attack against a vulnerability (buffer overflow etc) may not be that high volume so may not trigger and automatic scrubber response.
mr_spock said:
I beg to differ a little. Having a small sacrificial connection to an upstream provider or (preferably) a peering point and advertising a specific route to divert inbound traffic down that link will, at least, protect other customers from a targeted DDOS on a specific host. If the DDOS is aimed at your host, then yes, a scrubber will help a bit if it's a volume attack, but an attack against a vulnerability (buffer overflow etc) may not be that high volume so may not trigger and automatic scrubber response.
The most common dDoS attacks are usually against a single host or a small range of hosts so you can't easily re-route that given the smallest block is usually a /24. If the attack is larger than that then you're black holing a much larger range of customers and that's going to be just as bad.It sounds like a good idea to have a small connection to route troublesome traffic to but in reality it's not possible unless you allocate a large block to each customer. (We're talking small web hosters and services/cloud companies who get their address space from another company)
If you are IBM or some other large business then yes, potentially you could do this.
Gassing Station | Business | Top of Page | What's New | My Stuff


