The Cedar Harbor incident lead needs a defensible investigation notebook for the next shift. You have fictional email, authentication, endpoint, network, cloud and vulnerability records. Preserve the source event IDs and keep claims within the evidence. The lead authorizes workstation isolation and escalation; risk acceptance belongs to the business owner. Each step adds a search or decision to your saved case record. Done means a scoped finding, evidence-backed response and a handoff that names the remaining uncertainty.
The Cedar Harbor incident lead needs a defensible investigation notebook for the next shift. You have fictional email, authentication, endpoint, network, cloud and vulnerability records. Preserve the source event IDs and keep claims within the evidence. The lead authorizes workstation isolation and escalation; risk acceptance belongs to the business owner. Each step adds a search or decision to your saved case record. Done means a scoped finding, evidence-backed response and a handoff that names the remaining uncertainty.
Work from the raw records before you read the alert label. Keep the source, time boundary and outcome visible in your result. Use the reference panel for the generic search syntax, then test the search against the task. A plausible story can still be wrong: cite the events that support your conclusion and name anything the logs cannot establish. The changed-log check rejects searches tied only to memorized event IDs.
Authentication exports can contain a duplicate of the same event. Count distinct event IDs when the task asks for attempts, and group by the source address. A failed logout must not become a login attempt. The boundary matters because an inflated count can make a benign source cross a detection threshold.