Differences

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

--- en:dpi:dpi_options:opt_ddos:ddos_description [2024/09/26 15:29] – external edit 127.0.0.1
+++ en:dpi:dpi_options:opt_ddos:ddos_description [2026/02/19 13:24] (current) – elena.krasnobryzh
@@ Line 1: / Line 1: @@
-====== General description ======
+======Description of Tools and Architecture======
 {{indexmenu_n>1}}
-DoS attack (for Denial of Service) and DDoS attack (for Distributed Denial of Service) are the types of computer systems attacks. Their goal is to prevent or complicate legit users to access the resources provided by the system.
-DoS attacks can be performed by a hacker using one computer. DDoS attack involves many computers. Typically, they are computers of ordinary trustful users. Their computers run the software that allows to control computers remotely - by a hacker.
+**VAS Experts offers a solution to combat DDoS attacks on telecom operators and their infrastructure, which can result in the operator being unable to serve its subscribers. Consequences include mass subscriber churn, financial and reputational losses.**
-<note important>The separate physical platform (other than operator's one) is required to use some protection functionality. The present system version currently does not allow to tune it individually for each of protected resources. Therefore we advise to rent the platform commercially to owners of resources to be protected.</note>
+VAS Experts provides several options for DDoS protection:
+  - Using SSG only with auto-protection against SYN Flood, UDP Flood, and HTTP Flood. Requires SSG with the Anti-DDoS Auto-protection option (**ddos**). **[[en:dpi:dpi_options:opt_ddos:ssg_ddos|More about configuring DDoS protection using SSG DPI]]**
+  - Using a combination of SSG and QoE to detect all types of DDoS attacks with the ability to fully block incoming traffic (**blackhole**) and clean it on SSG. Requires SSG with the option to collect and export protocol and direction statistics in IPFIX format (**ipfix**) and QoE with the option Traffic detection and cleaning (**blackhole and flowspec**) from BotNet and DDoS attacks (**antiddos**). For traffic cleaning, existing SSGs can be used (available in versions: BASE, BNG with mark and channels options, COMPLETE), or a dedicated SSG BASE server can be deployed to handle part of the traffic. **[[en:dpi:dpi_options:opt_ddos:qoe_ddos|More about configuring DDoS and BotNet detection based on QoE]]**
+<note tip>
+Licensing of the AntiDDoS option within SSG and QoE is described [[en:dpi:licensing|here]].\\ \\
+Requirements:
+  * QoE and GUI latest version. QoE license — any, AntiDDoS purchased as a separate option
+  * SSG license BASE / COMPLETE / BNG with additional options [[en:dpi:dpi_options:opt_priority|mark]] and [[en:dpi:dpi_options:opt_shaping|channels]]
+  * QoE installed on a separate server or VM, **NOT on the SSG server**
+  * For 1Gb/s peak incoming traffic, 8.4 GB is required for statistics storage
+</note>
+=====Most Common Forms of Attacks on Telecom Operators=====
+  - Input channel saturation
+    * Amplification attacks (DNS, NTP, UDP flood, etc.)\\ Protection: blackhole the targeted addresses or use flowspec on the uplink channel; other protection methods are ineffective.
+    * BotNet attacks — each bot generates relatively small traffic similar to legitimate traffic, but cumulatively the traffic exceeds operator input channel capacity; source address spoofing is not performed (see also item 2)\\ Challenge: often up to a thousand IPs are targeted, not just one\\ Protection: blackhole targeted addresses, flowspec on uplink channel (for some traffic types), create BotNet address list and block them on SSG (for some traffic types)
+  - High PPS attack:
+    * Flood, SYN flood, usually with source IP spoofing\\ Protection: use source IP spoofing protection mechanisms: [[en:dpi:bras_bng:bras_l2_options:bras_l2_vlan_ipsg|]] and [[en:dpi:bras_bng:bras_l2_options:filtering|]]. Redirect traffic to SSG for filtering or enable blackhole for targeted addresses
+  - Compromise of operator network elements: detected by the presence of SSH and other sessions from operator service addresses, which are pre-configured and not in the whitelist\\ Protection: detect such sessions and block by external address
+=====AntiDDoS Solution Architecture Based on SSG and QoE=====
+FastMitigator — an intelligent network attack protection system. It is a distributed traffic analysis module providing real-time detection and mitigation of a wide range of cyber threats.
+{{ :en:dpi:dpi_options:opt_ddos:antiddos.png?nolink&900 |}}
+====Operation Principle====
+  - Deep traffic analysis (DPI) and statistics export
+    * All traffic passes through DPI (SSG), operating in-line or on a traffic mirror.
+    * Full NetFlow in IPFIX format is sent to QoE for detailed analysis.
+  - Statistical analysis and baseline creation
+    * Analyzer processes Full NetFlow and creates a "normal profile" — a baseline of "healthy" traffic (without attacks or BotNet activity).
+    * Profile is stored in distributed QoE tables for fast access.
+  - Anomaly detection
+    * Detector based on neural networks and machine learning algorithms identifies deviations, classifies threats, and determines their sources.
+  - Traffic cleaning based on dynamic rules
+    * When an attack is detected, QoE creates an Attacks container containing:
+      * IP addresses of attacking hosts
+      * Ports used for attacks
+    * Container is sent to SSG DPI, where special Attack protocols (or protocol groups) are created for each threat type. It is recommended to use a dedicated SSG in in-line mode, which constantly passes all traffic or receives only part of it for cleaning.
+    * DPI pre-configures protection profiles (e.g., via "18. Session Policing") where Attack protocols are applied if operator channel capacity is not exhausted:
+      * Drop (full block)
+      * Policing (bandwidth limitation)
+    * Attacks container is updated in real-time: if the attack stops, IP hosts are removed from the list.
+  - Protection via BGP using blackhole and flowspec
+    * If operator channel capacity is exhausted, Attacks container can be sent to a special script that automatically adds subscriber IPs to blackhole, ensuring maximum infrastructure protection. Incoming traffic to these subscribers is dropped on the uplink channel.
+    * To allow subscribers on blocked public IPs to access the internet, their IP can be temporarily replaced — enable CG-NAT on SSG (using the previously announced public IP pool). This avoids changing the subscriber device IP during the attack. Access is temporarily via a different public IP, and after the attack ends, the original IP is restored — disable CG-NAT on SSG.
+====FastMitigator Advantages====
+  - Distributed architecture — high fault tolerance
+  - Adaptive protection — automatic rule updates
+  - Deep analytics — neural network algorithms + DPI
+  - Flexibility — supports different blocking scenarios
+====Organic AntiDDoS System====
+The development of DDoS protection aims to clean traffic before it reaches the internet. Deploying SSG AntiDDoS complexes across multiple operators will stop BotNet traffic inside the operator network. Centralized management via VAS Cloud allows lightning-fast reaction to any attacks while leaving transport channels between operators, IX, and data centers untouched. Upon detecting an attack on any resource with SSG, parameters for mitigation can be forwarded to the operator from which the illegitimate traffic originates.
+{{ :en:dpi:dpi_options:opt_ddos:antiddos-2.png?nolink&900 |}}
+<note tip>[[en:dpi:qoe_analytics:cases:network_health:flood|Use cases of the solution]]</note>

Differences

What were you trying to find?