A junior security analyst repeatedly executes threat hunts without appropriately bounding the search parameters by time, asset criticality, or specific indicators. What is the most significant operational consequence of this specific practice?
Pick A–D or press 1–4, then give this panel ten seconds: the verdict, and why each of the four options is right or wrong.
Using broad, unbounded queries returns massive data volumes, forcing analysts to sift through results without context. This leads directly to investigator fatigue and increases the likelihood of missing true positives. Read-only queries do not disable protocols, corrupt indexing architectures, trigger automated isolation playbooks, or alter identity access permissions.
- ARunning queries does not change the analyst's permissions.
- BSearches are read-only and do not launch playbooks.
- CBroad queries are slow but do not corrupt the index.
- DCorrect: unbounded hunts return huge result sets without context, causing fatigue and missed true positives.
More below: why each option is right or wrong — scroll this panel