Question 1
An analyst encounters this security situation: Firewall and identity logs disagree by seven minutes during a suspected account takeover, making the sequence of events unreliable. What is the MOST appropriate next investigation or control action?
Explanation
Correct Answer
The decisive gap is “Firewall and identity logs disagree by seven minutes during a suspected account takeover, making the sequence of events unreliable.”. “Synchronize logging sources to a trusted time reference and normalize event timestamps before correlating the activity.” addresses that gap directly. The expected confirmation is “The reconstructed timeline orders firewall, endpoint, and identity events consistently against the same UTC reference.”; merely noticing an indicator would not establish the corrective outcome.
Incorrect Answers
This action could help for “A cloud application relies on a shared administrator account, preventing attribution of privileged configuration edits.”, but the present gap is “Firewall and identity logs disagree by seven minutes during a suspected account takeover, making the sequence of events unreliable.”. The required validation “The reconstructed timeline orders firewall, endpoint, and identity events consistently against the same UTC reference.” would remain unresolved by “Replace shared privileged access with individually attributable federated identities and audited elevation.”.
The proposed “Disable or restrict legacy authentication paths and enforce strong conditional access for privileged identities.” addresses “A passwordless pilot still permits weak legacy authentication on the same privileged identities.”, not the investigation or control required by “Firewall and identity logs disagree by seven minutes during a suspected account takeover, making the sequence of events unreliable.”, where success must demonstrate “The reconstructed timeline orders firewall, endpoint, and identity events consistently against the same UTC reference.”.
The alternative “Verify log export permissions, collector ingestion health, and the relevant parser before declaring the cloud workload monitored.” focuses on “A new cloud workload sends detailed audit events but the central SIEM shows none of its authentication failures.” rather than the documented condition “Firewall and identity logs disagree by seven minutes during a suspected account takeover, making the sequence of events unreliable.”. It is not the best action for the specific evidence goal “The reconstructed timeline orders firewall, endpoint, and identity events consistently against the same UTC reference.”.