Question 710
Blue Haven Media operates creative files and production workspaces under a least-privilege requirement. Its review records the following concern: A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?
Explanation
Correct Answer
An incident query joins an identity event and a network event by matching time and entity attributes. This is the relevant proof because it tests whether the selected corrective action (Use a SIEM such as Microsoft Sentinel to ingest relevant security data into searchable, correlated investigations) addressed the initiating problem (A security operations team collects firewall and sign-in logs in separate products and cannot correlate events across systems) in Blue Haven Media's creative files and production workspaces environment, not merely whether a task was marked complete.
Incorrect Answers
A recent sample identity event is searchable with the expected schema in the connected data source. This is useful evidence for a different situation (A Sentinel deployment has a configured analytic rule but no data connector supplying the expected identity events) and action (Configure the applicable Sentinel data connector and confirm ingestion into the intended workspace). For the reported issue at Blue Haven Media, it does not establish the required outcome: An incident query joins an identity event and a network event by matching time and entity attributes.
A synthetic series meeting the rule criteria creates the expected alert while ordinary sign-ins do not. This is useful evidence for a different situation (A team wants to flag repeated privileged sign-in failures but its Sentinel rule has no query logic or schedule) and action (Create and test an analytics rule using an appropriate KQL query, threshold and evaluation schedule). For the reported issue at Blue Haven Media, it does not establish the required outcome: An incident query joins an identity event and a network event by matching time and entity attributes.
Log analysis surfaces an actionable case while only the approved response workflow can perform a privileged containment step. This is useful evidence for a different situation (A manager equates SIEM and SOAR as identical products and therefore expects a log search query itself to approve a containment action) and action (Separate SIEM aggregation and analysis from SOAR-controlled response orchestration and human approval boundaries). For the reported issue at Blue Haven Media, it does not establish the required outcome: An incident query joins an identity event and a network event by matching time and entity attributes.