TPS-based Attack Vectors and Stress-based Attack Vectors
F5 ASM/AWAF employs several strategies to mitigate DDoS and other traffic-based attacks, including TPS-based and Stress-based attack vectors. These vectors identify and manage suspicious traffic based on different criteria and apply mitigation techniques to protect the web application and infrastructure.
TPS-based Attack Vectors:
TPS (Transactions Per Second) attack vectors are designed to detect and block excessive requests from various sources based on their rate of traffic. These are the key methods for mitigating TPS-based attacks:
By Source IP:
Mitigation Methods: The system can apply three different mitigation techniques to offending IP addresses that generate excessive requests.
By Device ID:
Mitigation Methods: The system can track requests from specific device IDs (often tied to user-agent or fingerprinting) and apply three different mitigation methods to manage excessive traffic from these devices.
By Geolocation:
Country-based Blocking: The system uses geolocation data to determine whether traffic from a specific country should be treated as suspicious or part of an attack. Mitigation can be applied to countries that generate abnormal traffic levels.
By URL:
Specific URL Protection: This method focuses on detecting and mitigating excessive requests to specific URLs. If a URL is being targeted with high TPS, mitigation can be applied to prevent overloading the application.
Site-Wide:
Entire Site Mitigation: This method monitors and mitigates traffic across the entire Virtual Server or website. If the overall TPS exceeds thresholds, mitigation can be applied site-wide.
Stress-based Attack Vectors:
Stress-based attack vectors focus on detecting and mitigating server-side stress caused by excessive or abnormal traffic. These vectors provide different approaches to identify and mitigate attacks that cause resource exhaustion on the application or server.
By Source IP:
Similar to TPS-based mitigation, this approach applies mitigation techniques to offending IP addresses that cause excessive stress on the server by generating high traffic.
By Device ID:
Identifies stress caused by specific devices (through device IDs) and applies mitigation measures for abnormal traffic patterns originating from these devices.
By Geolocation:
Similar to the TPS-based geolocation method, this strategy can apply mitigation to traffic from specific countries that exhibit behavior associated with attack traffic.
By URL:
This method focuses on detecting stress caused by high traffic targeting specific URLs, applying mitigation to prevent the server from being overwhelmed by requests to those URLs.
Site-Wide:
Mitigation can also be applied site-wide (across the entire virtual server) based on excessive stress detected in the system, ensuring that the entire application or site does not get affected by an overload of traffic.
Behavioral:
Behavioral Stress Detection: This approach uses the Anomaly Detection Engine to monitor the normal traffic behavior of the application. If traffic deviates from expected patterns, suggesting stress, the system can trigger mitigation.
The Behavioral DoS (BaDoS) feature is a self-adjusting and adaptive engine that measures normal traffic behavior and applies mitigation techniques when server stress occurs.
Behavioral DoS (BaDoS):
Behavioral DoS (BaDoS) is an advanced feature that analyzes the normal traffic patterns to the server and uses this baseline to detect and mitigate potential Denial of Service (DoS) attacks based on observed deviations.
4 Available Mitigation Options:
No Mitigation (Default): No action is taken, and normal traffic continues.
Conservative: A more cautious approach to mitigation, reducing traffic volume gradually and avoiding false positives.
Standard: The default mitigation option that balances between performance and aggressive mitigation.
Aggressive: This method aggressively blocks or rate-limits offending traffic to prevent service degradation.
Self-Adjusting and Adaptive:
The BaDoS engine adapts to changing traffic patterns, adjusting its mitigation techniques based on observed traffic shifts. This helps ensure that legitimate traffic is not mistakenly blocked, while still responding to abnormal spikes that could indicate a DoS attack.
Summary of Key Concepts:
TPS-based Attack Vectors: Focus on blocking or mitigating attacks based on excessive requests per second from various sources, including IP addresses, device IDs, geolocation, specific URLs, and site-wide traffic.
Stress-based Attack Vectors: Focus on detecting and mitigating server overloads caused by excessive traffic. These vectors also address source IP, device ID, geolocation, URLs, and site-wide traffic, with an additional behavioral detection method that identifies deviations from normal traffic behavior.
BaDoS (Behavioral DoS): A dynamic, self-adjusting feature that uses the system’s baseline traffic patterns to detect and mitigate potential DoS attacks based on abnormal traffic behavior. It offers different levels of mitigation, from No Mitigation to Aggressive.
Last updated