Agent Foskett Academy • Microsoft Sentinel • Module 4 • Lesson 43

Lesson 43 — Adding Evidence and Investigation Notes

The investigation is not finished just because you understand what happened.

Can another analyst follow your evidence, challenge your reasoning and continue the case?

Good investigation notes turn individual discoveries into a defensible case record.
Agent Foskett Academy Microsoft Sentinel evidence documentation
What you will learn

Document the investigation so your findings survive a shift change.

✓ Record evidence and provenance
✓ Separate facts from hypotheses
✓ Document response actions
✓ Prepare an analyst handover

Learning objectives

  • Write clear, chronological incident notes.
  • Record evidence sources, timestamps, entities and query context.
  • Separate observations, inferences and unresolved questions.
  • Document analyst decisions and response actions.
  • Prepare a reproducible investigation handover.

Why this lesson follows bookmarks

Lesson 42 preserved important hunting findings. This lesson explains how to turn those findings, alerts, KQL results and entity pivots into a coherent case narrative.

A saved result is evidence. A note explains its relevance.

Five questions every investigation note should answer

WHAT did we observe? WHEN did it happen? (event time and timezone) WHERE did the evidence come from? WHY does it matter to this incident? WHAT remains unverified?

Keep the source of each conclusion visible. A reader should not have to guess which alert, bookmark or log row supports your statement.

Evidence is not interpretation

Observed: SigninLogs recorded a successful sign-in for alex@contoso.com at 01:57 UTC from 203.0.113.50.

Interpretation: This sign-in may be connected to the mailbox activity detected at 02:08 UTC.

Do not turn a hypothesis into a fact

“The attacker signed in at 01:57” may be too strong without corroboration.

“A successful sign-in preceded the mailbox alert; attribution remains under investigation” is more defensible.

The Agent Foskett evidence record

FieldWhat to capture
TimeEvent timestamp, timezone and when the analyst observed it if relevant
SourceTable, alert, bookmark, product or other evidence location
EntityUser, device, IP, application or resource
ObservationWhat the telemetry actually shows
ReproductionQuery, filters, time window and result identifier where available
AssessmentRelevance, confidence and competing explanations
Next stepQuestion or action still outstanding

Example — a useful incident note

[Evidence] 2026-10-07 01:57 UTC Source: SigninLogs User: alex@contoso.com IP: 203.0.113.50 Result: Successful sign-in [Assessment] Occurred 11 minutes before the mailbox alert. Possible connection; not yet confirmed. [Next steps] Validate sign-in context and compare audit activity. Check whether other accounts used the same IP.

Example values are illustrative, not a real incident.

Use incident comments purposefully

Incident comments provide a place to record findings, decisions and handover context. Use clear headings and concise entries; do not paste an entire unfiltered log export into a comment.

Know the difference: comments and activity history

Comments explain what the analyst learned or decided. The incident activity history records changes and actions associated with the case. Both are useful, but neither replaces source telemetry.

Use KQL to make findings reproducible

Evidence query — preserve the time window
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11
SigninLogs
| where UserPrincipalName =~ "alex@contoso.com"
| where TimeGenerated between (
    datetime(2026-10-07 01:30:00) ..
    datetime(2026-10-07 02:30:00)
)
| project TimeGenerated, UserPrincipalName, IPAddress,
          AppDisplayName, ResultType, ConditionalAccessStatus
| order by TimeGenerated asc

Record the query and time window used, then identify the specific rows that support the note. Avoid assuming that a later rerun will return identical data after retention or ingestion changes.

Capture negative findings carefully

“No related process events found in the queried table and time window” is useful.

“No other malicious activity occurred” is not supported by that limited search.

Preserve uncertainty

Label findings as confirmed, suspected or unresolved. Explain what additional evidence would change your assessment.

Never use a severity label as a substitute for reasoning.

Record the investigation decision trail

02:08 Mailbox alert reviewed 02:19 Related sign-in discovered 02:23 Evidence preserved and note added 02:28 Device activity queried 02:35 Escalated for containment decision For each decision: Evidence → Assessment → Action → Outcome

The investigation timeline explains environmental activity; the decision trail explains what the SOC did in response. Keep those concepts distinct.

Record containment decisions

If an account was disabled, a device isolated or a session revoked, document the reason, authorisation, execution time, scope and observed outcome.

Protect sensitive information

Use approved case systems and access controls. Avoid copying credentials, tokens, unnecessary personal data or secrets into incident comments.

Handover — what the next analyst needs

IncludePurpose
Incident status and priorityWhat needs attention now
Confirmed findingsWhat the evidence establishes
Entities and scopeWhat has been investigated
Key timestamps and evidence linksHow to reproduce the story
Actions already takenAvoid duplicate or conflicting response
Unanswered questions and next stepsContinue without restarting

Agent Foskett exercise

Your incident contains a suspicious sign-in at 01:57, mailbox activity at 02:08 and PowerShell execution on DEVICE-27 at 02:14.

  1. Write one confirmed evidence statement for the sign-in.
  2. Write one hypothesis linking the sign-in and mailbox alert.
  3. Identify which query, time window and entities must be recorded.
  4. Document a decision to escalate, including the reason.
  5. Write a three-sentence handover that makes the next investigation step obvious.

Common mistakes

  • Writing “malicious” without showing supporting evidence.
  • Omitting timestamps or timezones.
  • Recording conclusions but not source queries.
  • Mixing case actions with attacker activity.
  • Leaving the next analyst without a clear question.

Agent Foskett takeaway

If the next analyst cannot reconstruct your reasoning, the investigation is not properly documented.

Capture the evidence. State the uncertainty. Explain the decision. Leave a trail somebody else can follow.

Lesson summary
Build clear, reproducible incident notes that distinguish telemetry from interpretation, record decisions and support reliable handover.
Sentinel Academy Home

Related Agent Foskett learning

Turn preserved findings into a coherent case record.