Direct Network Flood
Parent: T1498
Description
Adversaries may attempt to cause a denial of service (DoS) by directly sending a high-volume of network traffic to a target. This DoS attack may also reduce the availability and functionality of the targeted system(s) and network. [Direct Network Flood](https://attack.mitre.org/techniques/T1498/001)s are when one or more systems are used to send a high-volume of network packets towards the targeted service's network. Almost any network protocol may be used for flooding. Stateless protocols such as UDP or ICMP are commonly used but stateful protocols such as TCP can be used as well. Botnets are commonly used to conduct network flooding attacks against networks and services. Large botnets can generate a significant amount of traffic from systems spread across the global Internet. Adversaries may have the resources to build out and control their own botnet infrastructure or may rent time on an existing botnet to conduct an attack. In some of the worst cases for distributed DoS (DDoS), so many systems are used to generate the flood that each one only needs to send out a small amount of traffic to produce enough volume to saturate the target network. In such circumstances, distinguishing DDoS traffic from legitimate clients becomes exceedingly difficult. Botnets have been used in some of the most high-profile DDoS flooding attacks, such as the 2012 series of incidents that targeted major US banks.(Citation: USNYAG IranianBotnet March 2016)
Mapped SPARTA techniques
5 techniques
Mapped by SPARTA, not curated by SafeMode Space.
Mapped by SPARTA, not curated by SafeMode Space.
Mapped by SPARTA, not curated by SafeMode Space.
Jamming is conceptually a direct flood of the RF channel with high-power noise; T1498.001 'Direct Network Flood' covers the specific direct-flooding pattern at sub-technique level. Cross-tactic moderate.
Mapped by SPARTA, not curated by SafeMode Space.
Cross-framework references
Relationships published by the source frameworks themselves, reproduced here with attribution. They are not SafeMode Space mappings and carry no confidence rating of ours.
Countered by 11 in MITRE D3FEND (Defensive Techniques)
- D3-APCAApplication Protocol Command Analysis
- D3-CSPPClient-server Payload Profiling
- D3-ISVAInbound Session Volume Analysis
- D3-ITFInbound Traffic Filtering
- D3-NTCDNetwork Traffic Community Deviation
- D3-NTFNetwork Traffic Filtering
- D3-NTSANetwork Traffic Signature Analysis
- D3-PHDURAPer Host Download-Upload Ratio Analysis
- D3-PMADProtocol Metadata Anomaly Detection
- D3-RTSDRemote Terminal Session Detection
- D3-UGLPAUser Geolocation Logon Pattern Analysis
Cite as SafeMode Space, mitre-attack-enterprise T1498.001.