Question 130
An Azure security engineer investigates the following incident: A Sentinel query compares raw account aliases against a watchlist using exact case-sensitive strings and misses known risky user variants. Which safeguard would best prevent this issue from recurring?
Explanation
Correct Answer
This guardrail addresses sentinel watchlist match normalization: Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. The prevention measure is: Retest analytic watchlist joins after source schema or naming normalization changes. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. “Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated” would address that alternative cause, not the condition in this question: watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality.
“Review playbook connection identities and least-privilege rights before enabling automated containment” responds to this separate finding: playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. This question instead needs “Retest analytic watchlist joins after source schema or naming normalization changes”, so the alternative does not meet the stated condition.
Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. “Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators” applies to that separate problem. The observed case is a Sentinel query compares raw account aliases against a watchlist using exact case-sensitive strings and misses known risky user variants; choosing this alternative would address the wrong failure mode.