Which flood type is described as masking multiple HTTP requests within one packet to remain undetected?

Which flood type is described as masking multiple HTTP requests within one packet to remain undetected?

• A. Single-Request HTTP Flood Attack
• B. Random Recursive GET Flood Attack
• C. Single-Session HTTP Flood Attack
• D. Slowloris

Answer: (C)

The type described works by hiding multiple HTTP requests inside a single session, using one connection to send a burst of requests rather than opening many separate ones. In a single-session HTTP flood, the attacker keeps the connection alive (often with HTTP keep-alive or pipelining) and streams multiple requests over that same session. To defenders, this can look like normal traffic from one user, so the flood isn’t as easily spotted by checks that count requests per separate connection or per IP. The server ends up processing a high number of requests, exhausting resources, even though the traffic appears to come from a single source and session. This differs from other techniques: a single-request flood sends limited requests per interaction and would be easy to spot by per-packet or per-request rate. A random recursive GET flood targets many resources in a more erratic pattern rather than packing multiple requests into one session. Slowloris keeps many connections open with partial headers to tie up server resources, not by multiplexing multiple requests in one packet.

The type described works by hiding multiple HTTP requests inside a single session, using one connection to send a burst of requests rather than opening many separate ones. In a single-session HTTP flood, the attacker keeps the connection alive (often with HTTP keep-alive or pipelining) and streams multiple requests over that same session. To defenders, this can look like normal traffic from one user, so the flood isn’t as easily spotted by checks that count requests per separate connection or per IP. The server ends up processing a high number of requests, exhausting resources, even though the traffic appears to come from a single source and session.

This differs from other techniques: a single-request flood sends limited requests per interaction and would be easy to spot by per-packet or per-request rate. A random recursive GET flood targets many resources in a more erratic pattern rather than packing multiple requests into one session. Slowloris keeps many connections open with partial headers to tie up server resources, not by multiplexing multiple requests in one packet.