 Description An adversary may execute a flooding attack using the HTTP protocol with the intent to deny legitimate users access to a service by consuming resources at the application layer such as web services and their infrastructure. These attacks use legitimate session-based HTTP GET requests designed to consume large amounts of a server's resources. Since these are legitimate sessions this attack is very difficult to detect. Prerequisites
| This type of an attack requires the ability to generate a large amount of HTTP traffic to send to a target server. |
Mitigations
| Design: Use a Web Application Firewall (WAF) to help filter out malicious traffic. This can be setup with rules to block IP addresses found in IP reputation databases, which contains lists of known bad IP addresses. Analysts should also monitor when the traffic flow becomes abnormally large, and be able to add on-the-fly rules to block malicious traffic. Special care should be taken to ensure low false positive rates in block rules and functionality should be implemented to allow a legitimate user to resume sending traffic if they have been blocked. |
| Hire a third party provider to implement a Web Application Firewall (WAF) for your application. Third party providers have dedicated resources and expertise that could allow them to update rules and prevent HTTP Floods very quickly. |
| Design: Use a load balancer such as nginx to prevent small scale HTTP Floods by dispersing traffic between a group of servers. |
| Implementation: Make a requesting machine solve some kind of challenge before allowing them to send an HTTP request. This could be a captcha or something similar that works to deter bots. |
Taxonomy Mappings  CAPEC mappings to ATT&CK techniques leverage an inheritance model to streamline and minimize direct CAPEC/ATT&CK mappings. Inheritance of a mapping is indicated by text stating that the parent CAPEC has relevant ATT&CK mappings. Note that the ATT&CK Enterprise Framework does not use an inheritance model as part of the mapping to CAPEC.Relevant to the ATT&CK taxonomy mapping (also see parent) | Entry ID | Entry Name |
|---|
| 1499.002 | Endpoint Denial of Service:Service Exhaustion Flood |
References  Content History | Submissions |
|---|
| Submission Date | Submitter | Organization |
|---|
| 2014-06-23 (Version 2.6) | CAPEC Content Team | The MITRE Corporation | | | Modifications |
|---|
| Modification Date | Modifier | Organization |
|---|
| 2019-04-04 (Version 3.1) | CAPEC Content Team | The MITRE Corporation | | Updated Related_Weaknesses | | 2020-07-30 (Version 3.3) | CAPEC Content Team | The MITRE Corporation | | Updated Taxonomy_Mappings | | 2021-06-24 (Version 3.5) | CAPEC Content Team | The MITRE Corporation | | Updated Taxonomy_Mappings | | 2022-09-29 (Version 3.8) | CAPEC Content Team | The MITRE Corporation | | Updated Taxonomy_Mappings | | 2023-01-24 (Version 3.9) | CAPEC Content Team | The MITRE Corporation | | Updated Mitigations, References |
More information is available — Please select a different filter.
|
