Back to Blog
Cybersecurity

DDoS Protection for Enterprise: What to Do Before, During and After an Attack

DDoS attacks are bigger, cheaper, and more targeted than ever. A 4-hour attack can cost over $1 million. This three-phase playbook shows you how to prepare, respond, and harden — so your business stays online.

Cybersecurity
Use Case
9 min read
42 views

Why DDoS Attacks Are Now an Enterprise-Level Threat

A DDoS attack can take down your website, portal, or API in seconds. In 2024, the largest attack on record hit 5.6 Tbps — enough to flood any network on earth. But size is only part of the story. DDoS protection enterprise teams now face attacks that are cheaper to launch, harder to stop, and often used as a cover for data theft.

Specifically, a DDoS-for-hire service costs just $10 to $50 per attack (Europol 2024). So the barrier for attackers is nearly zero. At the same time, 65% of DDoS attacks now target the app layer — not just raw bandwidth. As a result, standard firewalls miss most of them. This article gives you a three-phase playbook: what to do before, during, and after a DDoS attack.


DDoS Attacks Are Bigger, Faster and Cheaper

DDoS attacks grew 20% from the year before in 2024 (Cloudflare). Indeed, attacks now mix bandwidth floods with app-layer tricks. Previously, only large groups could launch big attacks. But today, anyone with $10 and a browser can rent a botnet. As a result, every public enterprise is a target — not just banks and governments.

What a DDoS Attack Costs Indian Enterprises

Gartner puts the average cost of IT downtime at $6,000 per minute. So a 4-hour DDoS attack costs roughly $1.44 million in lost revenue and recovery. On top of that, India saw a 30% rise in DDoS attacks on BFSI and e-commerce in 2024 (CERT-In). Furthermore, RBI requires 99.5% uptime for internet banking. Even one unblockd DDoS can breach that SLA.

5.6Tbps
Largest DDoS attack recorded in 2024 (Cloudflare)
$6K/min
Average cost of enterprise downtime (Gartner)
$10
Cost to rent a DDoS-for-hire attack (Europol 2024)

Can a Firewall Stop DDoS Attacks?

In short, no. Firewalls are built to filter traffic by rules — allow this port, block that IP. But a DDoS attack sends millions of requests that each look normal on their own. So the firewall lets them through one by one. Eventually, your server or app crashes under the volume.

Moreover, app-layer DDoS attacks (Layer 7) mimic real user traffic. They send valid HTTP requests — just millions of them. As a result, your firewall cannot tell the difference between a real customer and an attacker. You therefore need cloud-based scrubbing that stops the flood before it reaches your network.

Why Firewalls Fail Against DDoS

Firewalls inspect packets one at a time. But DDoS attacks work by sending millions of normal-looking requests. So the firewall approves each one — until the server behind it collapses. Cloud DDoS scrubbing stops the flood before it ever reaches your firewall.

DDoS Protection Enterprise Phase 1 — Before the Attack

The best DDoS protection enterprise teams can have is planning ahead. Most damage from DDoS happens because there was no plan, no tooling, and no rehearsal. Here is what DDoS protection enterprise teams should set up before an attack ever hits.

Know Your Attack Surface

First, list every public site or app: websites, APIs, portals, DNS servers, and email gateways. Then check which ones have DDoS protection and which ones don’t. Obviously, you can’t protect what you haven’t mapped. Also, include branch office internet links — attackers target the weakest entry point.

Turn On Always-On Cloud DDoS Protection

On-demand scrubbing takes 5 to 15 minutes to start. But modern attacks peak in under 60 seconds. So always-on protection is now the baseline. In short, route your traffic through a cloud scrubbing provider (like Cloudflare, Akamai, or AWS Shield Advanced) that filters bad traffic 24×7. As a result, attacks are absorbed before they reach your network.

Set Up Rate Limiting and Geo-Blocking

Rate limiting caps how many requests one IP can make per second. This stops simple floods fast. Also, if your customers are mostly in India, geo-blocking can block traffic from countries you don’t serve. Together, these two controls stop a large share of attacks before they cause harm.

Build a DDoS Attack Response Plan

A plan on paper is better than no plan at all. But a tested plan is better still. Your DDoS attack response plan needs four things:

  • Escalation contacts: Who to call in the first 5 minutes — ISP, scrubbing provider, internal teams
  • Runbook steps: What to do in what order — activate scrubbing, block known bad IPs, scale systems
  • Communication plan: How to update leadership, customers, and the regulator (CERT-In requires 6-hour reporting)
  • Roles and ownership: Who makes decisions — not a committee, one person with power to act
Test Before You Need It

Run a practice drill once a quarter. Simulate a DDoS attack and walk through your response plan step by step. The gaps you find in a drill are the gaps that would have cost you during a real attack.

What to Do During a DDoS Attack — Phase 2

The first 15 minutes of a DDoS attack decide the damage. With proper DDoS protection enterprise planning, you act fast. If you don’t, you scramble — and the attacker wins. Here is what to do during a DDoS attack, step by step.

Activate Scrubbing and Escalate Immediately

First, confirm the attack is real — not just a traffic spike from a marketing campaign. Then activate your scrubbing service if it’s not always-on. At the same time, escalate to your ISP and your managed security provider. Speed matters more than perfection here. So act first, then refine.

Update With Stakeholders

Next, notify your leadership team, customer support, and legal. If the attack impacts customers, post a status update. Also, start the CERT-In reporting clock — you have 6 hours for critical setup. Don’t wait for full details before you communicate. Instead, give what you know and update as you learn more.

Watch, Adjust and Log

Meanwhile, watch your dashboards. DDoS attacks often shift tactics mid-attack — from network-level to app-layer, or from one target to another. So be ready to adjust your rules. Also, log everything: timestamps, traffic volumes, actions taken, decisions made. This evidence is essential for the team review and for regulators.

DDoS as a Diversion

About 40% of DDoS attacks are used as a cover for data theft (Netscout 2024). So while your team fights the flood, attackers may be quietly stealing data through another channel. Always check for secondary attacks during a DDoS incident.

After the DDoS Attack — Phase 3: Learn and Harden

The attack is over. Your systems are back online. But the work is not done. In fact, Phase 3 is where most firms fail — they go back to normal without learning anything. Here is how to use every attack as a chance to get stronger.

Run a Team Review

Within 48 hours, gather everyone involved and answer three questions. First, what worked? Second, what didn’t? Third, what would we do differently? Be honest. Blame-free reviews find the real gaps. Also, document the attack profile — type, size, duration, target, and how it shifted over time.

Update Your DDoS Attack Response Plan

Every real attack teaches you something your tabletop exercise missed. So update your plan with the new lessons. In short, fix the slow alerts, the update gaps, and the tool limits you discovered. Then test the updated plan within 30 days.

Test Your Defences Regularly

Finally, schedule DDoS practice tests at least twice a year. Use a test service that sends safe attack traffic to your scrubbing layer. As a result, you verify that your protection works — not just that it’s turned on. This is the difference between a plan and a proven defence.

Key Takeaway

DDoS protection enterprise success comes from three phases — not just one. Prepare before the attack with always-on scrubbing and a tested plan. Respond during the attack with speed and clear roles. Then learn after the attack by reviewing, updating, and testing again.

How Signisys Delivers Managed DDoS Protection for Enterprise

Signisys provides managed DDoS protection and WAAP services for enterprises that need always-on defence without building an internal DDoS team.

Managed WAAP and DDoS Protection

Signisys deploys cloud-based DDoS scrubbing and web application protection across all your public sites and apps. In short, this covers bandwidth floods, app-layer attacks, API abuse, and bot traffic. Protection is always-on — so there is no 15-minute start-up wait when an attack starts.

24×7 DDoS Response

Our SOC team monitors for DDoS around the clock. When an attack hits, we escalate in under 5 minutes. Also, we handle CERT-In reporting, stakeholder updates, and review reports. As a result, your team focuses on business recovery while we handle the defence.

India Compliance Built In

All DDoS protection controls map to RBI uptime requirements, CERT-In reporting mandates, and SEBI cyber resilience guidelines. So audit-ready evidence comes as part of the service.

Talk to an ExpertSpeak with a Signisys Network Security Architect About Managed DDoS Protection

Common Questions About DDoS Protection for Enterprise

Frequently Asked Questions
How do you protect against DDoS attacks?
First, deploy always-on cloud DDoS scrubbing across all public-facing assets. Then add rate limiting and geo-blocking. Also, build and test a DDoS response plan with clear roles and who to call.
What should you do during a DDoS attack?
Right away, activate scrubbing and escalate to your ISP and security provider. Next, notify key people and start the CERT-In reporting clock. Meanwhile, monitor dashboards and log all actions for post-incident review.
Can a firewall stop DDoS attacks?
No — firewalls check packets one at a time. But DDoS attacks overwhelm with millions of normal-looking requests. So the firewall approves each one until the server crashes. Cloud-based scrubbing is needed to absorb the flood.
How long do DDoS attacks usually last?
Most DDoS attacks last 45 to 68 minutes (Netscout 2024). However, multi-vector attacks can go on for hours or even days. With always-on scrubbing, the impact is absorbed no matter how long it lasts.
What is the cost of a DDoS attack on an enterprise?
Gartner estimates IT downtime costs $6,000 per minute on average. So a 4-hour DDoS attack can cost roughly $1.44 million in lost revenue and recovery — not counting reputation damage and regulatory penalties.
Weekly Briefing
Security insights, delivered Tuesdays.

Join 1 million+ security professionals. Practical, vendor-neutral analysis of threats, tools, and architecture decisions.