Preserve and Report¶
Step 03 / make the finding reviewable
Give the next analyst the view and its source¶
An export is useful only when the reader knows what it includes. Keep the source EVTX, then save the relevant rows with the filter, source reference and time basis. Do not treat a report or workspace as a replacement for the log.
- 1 / PreserveOriginal › working copy
- 2 / FilterChoose host, events and time
- 3 / InspectRead XML and compare context
- 4 / ExplainExport, limits and next check
Keep the original log separate from your working copy and reports.
Export the rows you reviewed¶
Use File › Export. Choose an available format and the scope you intend: the current view, selected rows or another supported scope. For the first lab, use Text, a tab-separated export, and include event descriptions. Check the dialog rather than assuming only visible rows will be exported. The export guide explains format, scope and descriptions.
Open the saved output. Compare its count and identifiers with the view you meant to preserve. A description can contain tabs or line breaks; use a table-aware reader when counting records. Keep the exact filter criteria separately, including unset restrictions and the active log path.
Keep the original, checked working copy, source URL or acquisition reference, and hashes.
Save the tool version, filter values, time basis, visible count and export scope.
Open the report and check its rows. Save the XML fields and source record references supporting your conclusion.
Save a workspace for convenience¶
Use File › Save Workspace As to retain the arrangement of sources and filters. The workspace stores settings and source locations; it does not package every EVTX or global preference. Keep the referenced files and written time-zone settings with it. The workspace guide explains what is retained.
Write three short parts¶
- Observation: state what the records show. Include source file, Computer, channel, EventID, EventRecordID and XML UTC time.
- Meaning and limits: explain the change without guessing approval, identity or missing activity. State filter and collection gaps.
- Next check: request one useful source of corroboration and explain what it could resolve.
For a group-change case, you might request the change ticket or related authentication events for the recorded host and session. Do not call an account an attacker simply because a group is privileged. A success-audit event records a successful audited action; it does not label it safe.
Download the case-note starter when you begin the Full Lab.
Before you close the case
Check the original and working hashes again. Retain exports, filter notes, source references and any load/rendering warnings. Store the complete case outside a disposable VM before restoring its snapshot. A clear limitation is a useful result; a screenshot alone cannot preserve the underlying evidence.
Continue to the hands on labs. The browser case uses fictional events; the Full Lab uses a small public EVTX.