Protection against SYN flood attack [Документация VAS Experts]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:dpi:dpi_options:opt_ddos:ddos_dos:ddos_dos_synflood [2020/04/21 14:02] lexx26en:dpi:dpi_options:opt_ddos:ddos_dos:ddos_dos_synflood [2024/09/26 15:29] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Protection against SYN flood attack ======+====== Protection against SYN flood attack ======
 {{indexmenu_n>2}} {{indexmenu_n>2}}
 +
 +<note tip>The service can be configured through the GUI. [[dpi:dpi_components:dpiui:user_guide:ssg_control_section:services#protect_from_ddos|Instruction]]</note>
 +
 SYN flood attack leads to lack of resources on its target system. Indeed, for each SYN packet the system has to allocate some memory resources, or to look up sessions lists, or to generate the specific SYN+ACK reply. The latest contains cryptographic cookie. This requires significant CPU resources. In all cases denial of service happens at incoming rate of SYN packets from 100,000 to 500,000 per second. Note that even 1Gb/s channel allows a hacker to send up to 1.5 million packets per second to the target site. SYN flood attack leads to lack of resources on its target system. Indeed, for each SYN packet the system has to allocate some memory resources, or to look up sessions lists, or to generate the specific SYN+ACK reply. The latest contains cryptographic cookie. This requires significant CPU resources. In all cases denial of service happens at incoming rate of SYN packets from 100,000 to 500,000 per second. Note that even 1Gb/s channel allows a hacker to send up to 1.5 million packets per second to the target site.