Question 540
While validating an Azure workload, the security team finds: A Sentinel incident includes high-risk authentication events from multiple hosts but the analyst reviews only its headline before dismissing the incident. Which remediation best addresses the specific issue?
Explanation
Correct Answer
The cause is: Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. The appropriate change is: Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition. Verify it with this outcome: The case includes a clear event chronology and evidence-backed conclusion or documented containment steps.
Incorrect Answers
This action concerns sentinel microsoft entra sign in connector, where Microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions. The reported incident instead involves Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation.
This action concerns azure monitor transformation for sensitive fields, where Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained. The corrective response here is “Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition”; this alternative does not provide that response.
This action concerns sentinel watchlist match normalization, where Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. The stem reports a Sentinel incident includes high-risk authentication events from multiple hosts but the analyst reviews only its headline before dismissing the incident; this control addresses a different failure condition.