A DDoS attack is one of the most visible attacks: a site or online service simply stops responding, and customers notice at once. According to the review by Ukraine’s National Cybersecurity Coordination Center, in Ukraine pro-Russian pseudo-hacktivist groups most often targeted defence industry enterprises, banks, logistics companies and local authorities. In 2025 they added targeted intrusions into industrial control systems to basic DDoS attacks and website defacements.
Below: what a DDoS attack is, what types there are, how to recognise one and what to do before and during an attack.
What a DDoS attack is
NIST defines denial of service (DoS) as the prevention of authorized access to resources or the delaying of time-critical operations. DDoS (Distributed Denial of Service) is a denial of service technique that uses numerous hosts to perform the attack.
In practice, traffic or requests to your service come from numerous infected devices — computers, routers, cameras — joined into a botnet. The goal is to stop real customers from using the site, customer portal or API. Because there are so many sources, blocking a single address does not help.
Types of DDoS attacks
Joint guidance by CISA, FBI and MS-ISAC splits DDoS attacks into three categories:
| Type | What it targets | How to defend |
|---|---|---|
| Volumetric | Bandwidth: the link is flooded with traffic | Filtering before your link — at the ISP or a DDoS protection service, CDN |
| Protocol | Vulnerabilities in network protocols, network equipment resources | NGFW configuration, connection rate limits, a DDoS protection service |
| Application | Specific applications and services: sign-in pages, search, APIs | WAF, request rate limits, CAPTCHA challenges |
Application-layer attacks are the trickiest: each request looks normal, and the server goes down because it cannot keep up with expensive operations.
How to tell it is a DDoS attack
The CISA, FBI and MS-ISAC guidance lists typical signs:
- a site or service is unavailable or has slowed down sharply;
- traffic has suddenly grown or the link is congested;
- unusual patterns in the logs: many requests from certain addresses or to one page;
- servers and applications crash for no apparent reason;
- CPU, memory or bandwidth use rises sharply and stays high;
- other services are unavailable — DNS or firewalls, for example;
- an alert has come from a DDoS protection service.
Not every outage is an attack: it may be a fault, a failed update or a rush of real visitors. That is why you need to know in advance what your normal traffic looks like. One more thing: DDoS is sometimes combined with other attacks, so watch other events more closely while it is going on.
How to prepare in advance
- Assess the risks. Which online services are critical, how much downtime the business can tolerate, who depends on them.
- Filter volumetric attacks before your link. A large flood of traffic has to be filtered before it reaches your network — at your ISP or a specialised DDoS protection service. A CDN spreads the load across many sites.
- Put the site and APIs behind a WAF. Request rate limits and CAPTCHA challenges filter out bots at the application layer.
- Configure the NGFW. Filtering suspicious traffic, connection rate limits, blocking known malicious addresses.
- Restrict direct access to servers, so that traffic goes only through the protection, not around it.
- Know your normal. Traffic and resource monitoring with alerts on deviations.
- Build in redundancy. Several servers or sites, load balancing, a backup connection — more in “Blackouts: how to keep business IT running”.
- Keep systems updated. Vulnerabilities can be used to amplify an attack.
- Prepare a response plan: roles, contacts at your ISP and hosting provider, playbooks, message templates for customers.
What to do during an attack
- Confirm the attack from monitoring data and logs.
- Activate the response plan and bring the responsible people together.
- Notify your ISP or hosting provider: they may have their own filtering.
- Turn on protection: a DDoS protection service, CDN, stricter NGFW and WAF rules, request rate limits.
- Gather evidence: times, addresses, logs, alerts from protection tools. You will need them for the investigation and for law enforcement.
- Keep in touch with employees, customers and partners: what has happened and when to expect recovery.
- After the attack, review what worked and update the plan and settings.
Whom else to notify about an incident is on the “Security incident” page.
NBU requirements
For insurers, credit unions, finance companies and pawnshops connected to the internet, NBU Resolution No. 143 explicitly requires protection against denial-of-service attacks and other known network attacks (paragraph 29). More in “NBU Resolution 143: cybersecurity rules for NBFIs”.
Checklist
- Critical online services and acceptable downtime are defined
- Volumetric attacks are filtered before your link — at the ISP or a protection service
- The site and APIs run behind a WAF with request rate limits
- The NGFW is configured to filter suspicious traffic
- Direct access to servers that bypasses the protection is closed
- Normal traffic is known, monitoring and alerts are in place
- There is redundancy: several servers or sites, a backup connection
- There is a response plan with provider contacts and a customer message template
How Bereg-IT can help
We protect sites and web applications with a WAF: protection against DDoS attacks, OWASP Top 10 attack categories and mass exploitation of vulnerabilities. We set up network security and NGFW — perimeter protection and traffic filtering. And SOC as a Service collects events from network equipment, NGFW, web applications and WAF to spot an attack in time and respond according to an agreed playbook.
If an attack is happening right now, see the first steps on the “Security incident” page.
The first consultation is free. Send a request and an information security specialist will get in touch.
Sources
- NIST CSRC Glossary, denial of service: https://csrc.nist.gov/glossary/term/denial_of_service; distributed denial of service (definition from NISTIR 7711): https://csrc.nist.gov/glossary/term/distributed_denial_of_service
- CISA, FBI, MS-ISAC, Understanding and Responding to Distributed Denial-of-Service Attacks (21.03.2024): https://www.cisa.gov/resources-tools/resources/understanding-and-responding-distributed-denial-service-attacks
- National Cybersecurity Coordination Center at the NSDC of Ukraine, Review of the National Cybersecurity System of Ukraine 2025 (in Ukrainian) — section on hacktivist activity: https://www.rnbo.gov.ua/files/2026/NATIONAL_CYBER_SCC/kiber_2025.pdf
- Resolution of the Board of the National Bank of Ukraine of 09.12.2025 No. 143, paragraph 29 of the Regulation (in Ukrainian): https://bank.gov.ua/admin_uploads/law/09122025_143.pdf