The correct approach is to search Enterprise Security for all related events using the significant fields in the risk notable , review those results, and determine which findings should be incorporated into the active investigation. This makes D more complete than simply searching for duplicate values of risk_object or threat_object.
Risk-based detections often aggregate multiple behavioral observations around an entity such as a user, host, or other risk object. A single investigation may therefore involve several risk notables representing different behaviors, techniques, or stages of activity. Correlating only on risk_object can be too restrictive or produce misleading associations because the analyst also needs relevant event context and other identifying fields.
The workflow described by D supports the investigation objective: locate related security events , assess their contextual relationship, and deliberately merge the appropriate findings into the current case so that they are tracked and actioned together.
The uploaded study-guide extract does not contain this exact question, so this selection is based on the Enterprise Security/SOAR case-correlation workflow represented by the terminology in the question.
Study Guide topics: investigation management, risk notables, risk objects, case correlation, SOAR case handling, finding aggregation.
