Question 520
A platform security assessment reveals this issue: A SOC creates a Sentinel workbook showing a spike in denied firewall connections and assumes it will automatically open incidents. What technical cause best accounts for the described behavior?
Explanation
Correct Answer
The described technical condition is: Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. The appropriate corrective action is: Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context. Confirm with: A controlled attack-pattern simulation opens a detection incident and the workbook continues displaying its trend.
Incorrect Answers
Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. “Grant only the necessary supported firewall action permission to the playbook identity and verify the Logic App connection” would address that alternative cause, not the condition in this question: workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows.
“Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics” responds to this separate finding: threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. This question instead needs “Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context”, so the alternative does not meet the stated condition.
Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. “Change the automation rule to the correct incident-created trigger with the intended scoped conditions” applies to that separate problem. The observed case is a SOC creates a Sentinel workbook showing a spike in denied firewall connections and assumes it will automatically open incidents; choosing this alternative would address the wrong failure mode.