
The artifact of our USENIX Security submission: Lemon: Network-wide DDoS Detection with Routing-Oblivious Per-flow Measurement Network-wide DDoS (Distributed Denial-of-Service) detection enables early attack detection and mitigates victim losses. However, unpredictable routing of DDoS traffic will invalidate the network administrator's prior knowledge of the network topology, causing existing sketch-based measurement systems to suffer from packet over-counting and processing stage mis-allocating issues. To address this gap, we propose Lemon, a routing-oblivious, resource-friendly, and scalable DDoS detection system that accurately detect DDoS attacks without any assumption on the traffic routing. Specifically, we design a novel data structure (Lemon sketch) that supports over-counting-free and mis-allocating-free measurements in the data plane. Lemon control plane aggregates Lemon sketches from measurement points and leverages per-flow level network-wide measurement results for DDoS attack detection and victim identification. We implement Lemon in both software switch (Bmv2) and programmable switch hardware (Tofino). The evaluation results show that Lemon can achieve consistently high accuracy for DDoS detection in various topology and traffic distribution configurations.
The provided artifacts include the following files: "lemon_bmv2/* ": The P4 source code of Lemon prototype in bmv2. "lemon_hardware/* ": The P4 source code of Lemon prototype in hardware (Tofino). "controlplane/* ": Lemon control plane and relevant scripts for traffic generating. The folder structure is as follows: artifact├── controlplane│ ├── lemon_controller│ ├── per_flow_analysis│ ├── pkt_send│ ├── README│ └── traffic_generation├── lemon_bmv2│ ├── baselines│ ├── divider.p4│ ├── p4app.json│ ├── README│ ├── s1-commands.txt│ ├── measurement.p4│ └── topologies├── Lemon_hardware│ ├── common│ ├── lemon.p4│ └── README└── README
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
