What Is a DDOS Attack? A Complete Guide to DDoS and How to Protect Against Attacks

A Distributed Denial-of-Service (DDoS) attack is a malicious attempt to disrupt the performance of an organization’s server, service, or network by overwhelming it with internet traffic. Some DDoS attacks focus on crashing a server, while others target the entire network, making all connected systems unreachable.

A DDoS attack launches its assault from multiple compromised computer systems, which makes it difficult to block. The goal isn’t usually to steal data, but to knock a service offline. However, cybercriminals sometimes use DDoS attacks as a smokescreen. While security teams battle to contain the surge, attackers attempt to break into the company to steal data and other valuable assets.

Falling victim to such an attack can be devastating. Extended business interruption, financial loss, and unhappy customers are just some of the consequences.

To help you understand the nature of this threat, we explore how DDoS attacks work and share strategies to identify, prevent, and mitigate them.

Let’s break down the typical mechanics of a distributed denial-of-service attack.

The first step in a DDoS attack involves a bad actor creating a botnet. This is a network of internet-connected devices, often dispersed, or “distributed”, across several locations.

Common devices exploited to create botnets include computers, mobile phones, and IoT tech like CCTV cameras, smart fridges, thermostats, toys, and Wi-Fi routers. The rise of IoT gadgets, many of which have minimal built-in security, has made it easier for hackers to build large botnets and launch successful DDoS attacks.

Once the botnet is assembled, the botmaster sends commands to all the compromised devices. These commands instruct the bots to simultaneously flood a specific target (the victim’s server, website, or network) with a massive volume of requests or connection attempts.

The broad goal is always the same: Denial of Service. The target’s network infrastructure, servers, and applications are so swamped by the deluge that they can no longer respond to legitimate network traffic. This achieves the attacker’s objective, which in practice might mean:

  • Website unavailability: Users cannot access your website.
  • Slow performance: Services become incredibly sluggish, which is important because Google Insights shows 53% of visitors will leave a mobile website if it takes longer than 3 seconds to load.
  • Service outages: Applications and online services completely crash.
  • Financial loss: Your company loses revenue, reputation, and customer trust

The botnet malware is inserted into devices via various methods, including:

  • Phishing emails: Phishing deceives victims into clicking on malicious links or attachments that install malware. This is the most common tactic. 
  • Exploiting software vulnerabilities: Hackers take advantage of unpatched security flaws in operating systems or applications.
  • Drive-by downloads: Malware installs silently when users visit compromised or malicious websites.
  • Trojan software: Seemingly legitimate apps or files secretly carry botnet malware.
  • Weak credentials and brute force attacks: Attackers guess or crack weak passwords to gain access and install malware.

Many of these operations are automated, which means they are carried out cheaply and at scale.  

Once the device is infected, the owner no longer has exclusive control of their phone or laptop. The compromised device is now what’s called a “bot” or “zombie”. The attacker (also known as the botmaster or bot herder) is able to remotely control the system without the owner’s knowledge. 

In this way, a botnet of hundreds, thousands, even millions of zombie devices is assembled.

The defining characteristics of a botnet are: 

  • Scale: To provide the volume of traffic needed to overwhelm a target.
  • Distribution: The idea is to make the operation hard to trace and mitigate. For this reason, the botnet might comprise IP addresses distributed across multiple geographical locations.
  • Resilience: If some bots are taken offline, the attack can continue with the remaining ones.
  • Political and consumer activism: Hacktivist groups use DDoS disruption as a form of protest. They typically target government agencies they ideologically oppose, or corporations they believe are acting unethically.
  • Extortion: Cybercriminals launch these attacks to extort businesses. They demand ransom payments to halt the attack.
  • Cyberwarfare: DDoS operations are a weapon of cyberwarfare. Government-authorized attacks may target another nation’s critical assets, such as state websites or power grids.
  • Mischievous hackers: Many distributed denial-of-service attacks have been perpetrated by teenage hackers. They do it for the thrill and challenge, and even out of boredom.
  • Business sabotage: Companies initiate DDoS attacks against rival businesses to render their online services unavailable, especially during high-stakes periods like Cyber Monday. Disgruntled employees also sometimes attempt to cripple their company’s operations using DoS or DDoS tactics.

To appreciate the diversity of motivations and targets, here are examples of notable DDoS attacks:

  • Estonia (2007): A politically motivated cyberattack against the Estonian government crippled banking and media websites.
  • Mirai Botnet (2016): The Mirai malware hijacked hundreds of thousands of IoT devices to perpetrate a record-breaking assault. This “volumetric” DDoS attack disrupted major websites like Twitter, Netflix, and Reddit.
  • US Banks attacks (2012–2013): A hacker group launched large-scale DDoS attacks on major U.S. financial institutions, including JPMorgan Chase and Bank of America. In recent years, financial institutions have been increasingly targeted by DDoS attacks.
  • Google attack (2017, revealed in 2020): Google disclosed in 2020 that it mitigated a 2.54 Tbps DDoS attack in 2017. It’s believed this was carried out by government-sponsored hackers.
  • GitHub attack (2018): GitHub was hit with one of the largest recorded DDoS attacks at the time (1.35 Tbps), briefly compromising the platform’s availability.

While the outcome of a DDoS strike is unmistakable (your server crashed, or your applications grind to a halt), identifying a developing attack isn’t always straightforward.

This is because its symptoms often mimic routine technical issues like traffic spikes and server problems.

The best advice is to fully understand what abnormal system behavior looks like. Then check for a combination of symptoms that suggest significant deviations from the norm. 

Here are the biggest warning indicators to watch for:

This is often the first and most noticeable sign.

  • Unusually slow network performance: Your website, applications, or internal systems become unusually sluggish for no reason. Transactions are delayed, and data transfers crawl.
  • Intermittent website or service unavailability: Your website goes offline sporadically, or users report frequent timeouts or error messages such as “Too many connections.”
  • Difficulty accessing the web: The flood of malicious traffic might consume most of your internet bandwidth, making it hard to access external sites from your internal network.

Deviations from your normal traffic baseline should prompt investigation.

  • Sudden, unexplained traffic surge: A massive, unexpected spike in web traffic is a red flag. This is especially true if it happens during off-peak hours or from unusual locations. 
  • Traffic from a single IP address or range: While DDoS is distributed, some attacks originate from a concentrated set of IPs. Sometimes, a disproportionate volume of requests comes from a specific region or country. If you don’t do much business in that region, alarm bells should be ringing.
  • Requests to a single endpoint: A sudden, overwhelming number of requests to a specific page, login portal, or API endpoint is a definite anomaly, especially if the asset doesn’t usually receive such concentrated demand.
  • Unusual behavioral profiles: A deluge of traffic from users who share a single behavioral profile (e.g. all use the same browser version, device type, or obscure operating system) can indicate bot activity.

Since DDoS attacks aim to exhaust resources, here are the tell-tale signs:

  • Spikes in CPU or memory usage: Your servers’ CPU and memory utilization may suddenly skyrocket without any obvious increase in legitimate activity.
  • Maxed-out bandwidth: Your internet connection bandwidth may show 100% utilization, strangling normal usage. 
  • High number of open connections: Your server logs might show a high number of half-open TCP connections (a sign of a SYN flood) or other connection-related errors.

Sometimes, the first indication comes from your users or providers.

  • Customer and employee complaints: Your customers or employees will be quick to notice if your services are slow or if there are issues accessing internal applications.
  • Alerts from your ISP or hosting provider: Your Internet Service Provider (ISP) or cloud service provider often has advanced monitoring systems. They should alert you if they detect suspicious patterns targeting your networks.
  • Ransom demands: If crippling your services is part a ransomware operation, you’ll likely soon hear from the criminals. They’ll send you direct messages demanding a ransom in exchange for stopping the attack. 

Seeing as attackers use increasingly sophisticated tactics, detection remains a challenge for many companies, making complete prevention an unrealistic expectation.

Here’s an idea of why detection is so complex:

  • The traffic looks legitimate: Because each bot is an actual internet device, separating the attack traffic from legitimate traffic is tricky. Data packets in the flood look just like the regular requests a website receives from real users, making them hard to spot.
  • The assault is distributed: Traffic comes from many different sources globally, making simple IP blocking ineffective.
  • Tactics evolve: Cybercriminals constantly develop new methods and refine existing ones to bypass defenses.

While there may be no silver bullet defense, a layered defense incorporating the following strategies can significantly reduce risks.

A Content Delivery Network (CDN) is a global system of servers that delivers web content to users based on their geographical location. While more widely used to speed up the delivery of images and video through caching, CDNs can also help to prevent DDoS attacks.

When combined with DDoS mitigation features, a CDN is able to absorb and filter abnormal traffic loads before they reach your origin server. By handling high-volume barrages at the network edge, the CDN helps shield core systems from overload while reducing latency (delays in data transmission).

Today, automation and machine learning are effectively deployed to identify and block cyberthreats in real time. Anomaly detection systems continuously monitor traffic patterns and learn what “normal” behavior looks like across your network. When unusual spikes or irregular patterns occur, the system flags the activity as potentially malicious.

By using machine learning algorithms, these tools adapt over time and become better at distinguishing legitimate user traffic from DDoS activity. This enables security teams or an automated system to respond swiftly and act before the attack reaches full impact.

Anomaly detection doesn’t prevent DDoS attacks outright, but it’s a critical part of a proactive, automated strategy that helps safeguard performance and uptime.

Instead of hosting your website and systems on your servers, you can use a professional web hosting provider. Choose a provider that includes DDoS protection as part of its service, whether at the infrastructure, network, or application level. For example, services like Amazon’s AWS Shield can absorb massive attack traffic before it ever reaches your server.

When faced with an unfolding DDoS attack, your priority is to mitigate the disruption and keep your systems available to genuine users.

Here are the mitigation measures you should take:

A high-level approach to minimize distributed denial-of-service attacks is to increase your network’s resilience through redundancy and scalability. This strategy is also known as infrastructure hardening.

  • Redundancy ensures backup systems or servers are in place to maintain operations if one part of the network crashes. This is achieved by using load balancing to distribute traffic evenly across multiple servers. The idea is to prevent a single point of failure from causing a complete shutdown.
  • Scalability ensures your systems can handle sudden, unexpected demand surges. Leveraging cloud-based services with elastic scaling enables you to add resources quickly during an attack. This way, you absorb the malicious efforts and keep your services live.

Anycast routing uses an Anycast network to spread attack traffic across multiple distributed servers.

Rather than overwhelming a single point, the flood is dispersed widely to lessen its impact, providing greater resilience and reduced strain on any single server. Legitimate users are connected to the nearest healthy or least-congested server within the global network to maintain communications.

Anycast is widely used by Content Delivery Networks (CDNs) and DNS providers as a first line of defence against high-volume attacks.

Rate limiting controls the number of requests a user or system can make within a given timeframe. 

Rate limits can be adjusted dynamically in real time. During a DDoS attack, security teams can tighten the limits to slow requests per user or IP address. For example, the permitted flow might be reduced from 3 requests per second to 1 per second. This process is often automated, using rules to detect threatening patterns and respond accordingly.

Rate limiting can help to quickly throttle the flood without completely locking out legitimate users. However, because it’s based on individual user/IP limits, it’s less effective in mitigating a large-scale distributed attack where connection requests come from thousands of sources.

Blackhole routing and sinkholing involve redirecting malicious traffic away from the target system.

Sinkholing redirects the bad traffic to a controlled server (called a “sinkhole”) where it can be analyzed and neutralized. It’s designed to keep your systems available to genuine customers.

Blackhole routing is a blunt force instrument that network administrators are sometimes forced to use. It works by creating a “black hole” route, effectively dropping all the traffic at a router. While quickly stopping the deluge and halting the strike, it achieves the attacker’s goal of denying service. By pushing both legitimate and malicious traffic into the black hole, the network becomes inaccessible to all. 

An Internet Service Provider (ISP) might use black hole routing during severe DDoS incidents to prevent wider network damage, but it’s generally considered a last resort.

More nuanced filtering and management methods are favored to selectively block malicious traffic while trying to keep services available.

Advanced traffic filtering precisely identifies and blocks only malicious requests during a DDoS attack, keeping legitimate users online. This requires real-time analysis and intelligent rules.

Key techniques here include:

  • Geo-blocking: Limits or blocks traffic from specific geographic regions where genuine users are unlikely to be located.
  • IP reputation blocking: Filters traffic from known malicious IP addresses using continually updated threat intelligence databases.
  • Access Control Lists (ACLs): ACLs involve setting rules on network devices that explicitly allow or deny traffic based on criteria like source IP, destination, or port. These can block known attackers or rate-limit suspicious traffic.

These filtering techniques, especially when combined with real-time traffic analysis and machine learning for anomaly detection, have proven very effective in DDoS defense and mitigation.

A Web Application Firewall monitors and controls HTTP traffic between a web application and the internet. It can detect and block malicious traffic patterns, such as those used in application-layer DDoS attacks like HTTP floods, and is especially effective against low-volume events that mimic legitimate user approaches.

WAFs can be set to differentiate between regular and abnormal behavior, reducing the incidence of false positives (false warnings).

Can a small business be targeted by a DDoS attack?

Yes, small businesses are increasingly targeted, especially if they lack strong cybersecurity defenses. DDoS attacks can be used for extortion, competition sabotage, or as a diversion for other attacks.

Is DDoS used as part of ransomware attacks?

How often you scan depends on your risk level, system complexity, and compliance needs. If your systems change often or you’re in a high-risk industry, continuous scanning is advisable.

For critical and public-facing systems, scan at least weekly or even daily. For less critical setups, monthly or even quarterly scans may be enough. Some standards, like PCI DSS, require scans every three months. However, following only the bare minimum can expose you to new threats.

Scanning after major system changes is important. You should also scan when dangerous emerging threats (e.g. WannaCry Ransomware) are identified so you can close new security gaps urgently.

How long do DDoS attacks last?

A vulnerability scan is usually a point-in-time assessment using automated tools to detect known security issues and common vulnerabilities. It is a specific type of security scan.

A security scan also checks for security flaws and critical vulnerabilities, but its scope is larger. It employs more tools and techniques. Besides vulnerability scans, it may also check firewall rules and user permissions. It often incorporates network mapping – a visual representation of all the network’s devices, systems, and connections.

Can a VPN stop a DDoS attack?

Vulnerability scanner tools cannot identify vulnerabilities like the following:

  • Zero-day vulnerabilities: Newly discovered flaws not yet been recorded in vulnerability databases.
  • Advanced attack techniques: Sophisticated methods like well-disguised malicious code can bypass automated scanners.
  • Business logic flaws: Scanners lack the contextual understanding needed to identify issues in application workflows or logic. For example, they might not catch multiple fraudulent transactions of $499 because they only know to refer to amounts of $500+.
  • Polymorphic malware: Attackers modify existing threats to create variants that evade signature-based detection. Vulnerability scanners battle to keep up.