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.
ATT&CK names observed adversary behaviors. Use a technique only when the evidence supports its behavior, and keep the observation separate from actor attribution. A delivered attachment can support a spearphishing attachment hypothesis; a failed login alone cannot prove stolen credentials. A mapping is a navigation aid for analysis, not a verdict or a guarantee of complete coverage.