Correlation search throttling is specifically intended to suppress repeated results that represent the same or substantially equivalent detection condition within a defined period. It is therefore the appropriate setting when a correlation search generates multiple findings for what analysts consider one potential incident.
Throttling is generally based on one or more result fields and a suppression period. For example, if repeated executions identify the same user and dest, the search can suppress additional findings matching that combination during the configured interval. This reduces redundant analyst workload while allowing materially different entities or events to generate new findings.
The engineering requirement is to select throttling fields carefully. Overly broad suppression can conceal genuinely distinct security events, while overly narrow suppression may fail to reduce duplicate findings. The suppression period likewise should reflect the behavior being detected and the expected recurrence pattern.
Correlation search priority affects prioritization rather than duplication. An adaptive risk modifier adds or modifies risk-related information but does not directly solve repeated notable generation. Adaptive response actions control downstream outcomes rather than the duplicate-suppression behavior requested.
Study Guide topics: correlation-search throttling, duplicate findings, notable suppression, detection tuning, analyst workload, false-positive reduction.
