For flood capacity, why rent 100,000 consumer devices over eight high-bandwidth hosts?
answer
- two different products, not one
- bits per second versus address spread
- eight hosts, one or two networks
- per-host value near zero picks the stock
basics
~20 sBecause they are different products. Eight fat hosts sell throughput. A hundred thousand consumer addresses sell source diversity: traffic spread across thousands of networks, each flow indistinguishable from an ordinary customer, that no single coarse decision removes.
solid answer
~50 sAggregate bandwidth and source diversity are bought separately, and a consumer fleet is almost always bought for the second. Eight compromised high-bandwidth hosts can each push tens of gigabits, so the raw total may well beat a hundred thousand home devices trickling a megabit or two each. But those eight sit in one or two provider ranges: one coarse decision removes all of them and costs nothing legitimate. The hundred thousand sit in thousands of consumer networks, each contributing a rate an ordinary customer could plausibly produce, so any rule broad enough to sweep them sweeps real users too. That indistinguishability is the property being paid for, not the bits. It also explains the preferred stock: when bandwidth is a host's only asset, its individual value is near zero, so the fleet must be assembled from things that cost nothing to acquire and stay powered on.
go deeper
Know that a botnet is not simply a big pile of bandwidth. Be able to say that home devices contribute very little each, and that their number is what matters rather than their speed.
Explain the arithmetic and the tradeoff: per-host rate against source count, and why a few fat hosts are removable in one decision while a dispersed fleet is not. This is the mechanics tier and the one being tested.
Show that you ask for source and network counts rather than peak when characterising a flood, and that you can say which supply shape you are facing and what that predicts about how long it will persist.
Frame the collateral cost the attacker is transferring: the decision to sweep a dispersed fleet is a decision to drop paying customers, and owning that tradeoff is a business call, not a technical one.
## Two products that look like one Everybody's first model of a botnet is "lots of machines, therefore lots of bandwidth". That model is wrong often enough to be the standard wrong answer at middle level. Flood capacity is really sold along two independent axes: - **Throughput**: how many bits per second the supply can emit. - **Source diversity**: how many distinct addresses, in how many distinct networks, those bits come from, and how ordinary each individual flow looks. A supply can be strong on one and weak on the other, and the two shapes are chosen for different jobs. ## The arithmetic that surprises people A compromised server on a well-provisioned link can emit tens of gigabits. Eight of them is a supply in the hundreds of gigabits. A consumer device behind a domestic connection has an *upload* path that is a small fraction of its download path, and in practice a fleet host contributes on the order of a megabit or two, often less, because the herder throttles deliberately to avoid the subscriber noticing a sluggish connection. So a hundred thousand of them may total less than the eight. Fleet size is not a bandwidth number. | Supply shape | Per-host rate | Distinct sources | What it actually buys | Persistence | |---|---|---|---|---| | A few high-bandwidth hosts | Very high | Handful, one or two networks | Raw peak, acquired fast | Short: removable in one decision | | Many consumer devices | Very low | Tens of thousands of networks | Indistinguishability from customers | Long: no cheap way to separate | ## What diversity is actually worth Eight sources in two networks is a *list*. It can be enumerated, and removing it costs the target nothing, because no real customer lives there. The supply is therefore fragile in exactly the way that matters: it survives only as long as it takes to make one decision. A hundred thousand consumer addresses cannot be treated as a list. They live in the same networks the target's real customers live in. Each one is sending at a rate a real customer could send at, so per-source thresholds are under-run by construction; the aggregate is just the sum of a hundred thousand individually unremarkable flows. Any rule wide enough to catch them catches paying users, and that collateral is precisely the cost the attacker is transferring onto the target. The fleet is not sized to overwhelm a link, it is sized so that separating it from the customer base is a decision nobody wants to make. This is also why geographic and network spread is advertised as a feature by resellers, and why a fleet concentrated in one country is worth less against a global service than a dispersed one. ## Why the stock is cheap junk There is a valuation argument underneath the choice. When a compromised host's only asset is its bandwidth, its residual value is close to zero: a megabit of upstream for a few weeks. A supply built from assets worth nearly nothing can only be profitable if acquisition costs nearly nothing, which selects hard for: - devices with default or reused credentials reachable from the internet; - firmware that is never updated and often cannot be; - hardware that is always powered on and unattended, so the host stays available and nobody notices; - populations large enough that the attrition of reboots, replacements and address changes is absorbed by volume. Routers, cameras, recorders and set-top boxes fit all four. Corporate servers do not: they are harder to take, more valuable for other purposes, and their loss is noticed. Choosing them for bandwidth alone would be spending an expensive asset on the cheapest possible use. ## The mix in practice Real operations often combine both. A small set of fat hosts provides an opening peak while the diverse fleet provides the part that does not go away, so the target faces a burst it can absorb followed by pressure it cannot cleanly separate. When you hear a description of a flood, asking "how many distinct sources, and in how many networks" separates these two supplies faster than asking for the peak figure. ## Answering well State the distinction in one line: throughput and source diversity are different purchases. Then give the arithmetic that proves fleet size is not bandwidth, then the collateral argument that explains what diversity buys, then the residual-value argument that explains why the fleet is made of cheap devices. That sequence answers the question and pre-empts the two follow-ups.
- When is the eight-host supply the better buy?When raw peak matters more than persistence: a short burst meant to saturate something before any decision can be made. It is also far cheaper to assemble, since taking eight hosts is nothing like holding a hundred thousand. The price is that it is coarse, enumerable, and the entire supply disappears at once.
- Why doesn't a per-source rate limit deal with the consumer fleet?Because every source is under the limit by design. The fleet is deliberately throttled so each device sends at a rate an ordinary subscriber produces, and the aggregate is just the sum of a hundred thousand unremarkable flows. The attacker is buying that arithmetic, not bandwidth.
- Does a bigger fleet always mean a bigger flood?No. Fleet size is a count of sources, not a bandwidth figure. Adding hosts raises diversity and resilience against attrition, but a hundred thousand throttled home devices can total less than a handful of hosts on well-provisioned links. Peak and source count are separate numbers and should be quoted separately.
Eight fat hosts are one very loud person you can point at across a room. A hundred thousand consumer devices are a crowd all speaking at normal volume; the noise is the same, but there is nobody to point at.
saying these in an interview costs you the question
- Equates fleet size with delivered bandwidth
- Assumes more hosts always means more throughput
- Thinks consumer devices are chosen for their uplinks
- Ignores that a few fat hosts share one or two networks
- Cannot say what source diversity buys beyond 'harder to block'