SUSA / EVENT LOG EXPLORER / ELE-01 / PUBLIC TRAINING SAMPLE Save this note as notes\finding.txt inside your case. Fill in one activity at a time. Use your observed results, not guessed values. Question: Do the two records show the same member being added twice? ACTIVITY 1: SETUP Case folder: Viewer version and edition / installer source / download date: Sample source URL and revision / date obtained: Original EVTX path and SHA-256 (or reference evidence\sha256.csv): Working EVTX path and SHA-256 (or reference evidence\sha256.csv): Source Computer / channel / loaded event count: Displayed time zone / previous setting to restore: Any XML or log-loading restrictions, load warnings or missing descriptions: ACTIVITY 2: VIEW CHECKS My prediction before reading XML / field I plan to compare: Active saved-file path: Event IDs 4732 / other restrictions / visible event count: Event IDs 4732,4733 / other restrictions / visible event count: General Filter cleared / visible event count: ACTIVITY 2: RECORD COMPARISON First record Computer / channel / EventID / EventRecordID: TimeCreated SystemTime (full XML UTC value): MemberSid: TargetUserName / TargetSid: SubjectUserName / SubjectLogonId: Saved XML text filename (results\191029-xml.txt): Second record Computer / channel / EventID / EventRecordID: TimeCreated SystemTime (full XML UTC value): MemberSid: TargetUserName / TargetSid: SubjectUserName / SubjectLogonId: Saved XML text filename (results\191030-xml.txt): Same or different members / field values supporting my answer: Bookmarked record IDs: What the missing-removal check does and does not establish: ACTIVITY 3: EXPORT CHECK Report filename (results\group-changes.txt) / format: Filter / displayed time zone / export scope / descriptions included: Verified event count / how I matched both events to their source records: Fields absent from the report / where I saved them in XML text: ANSWER TO THE RESPONSE LEAD 1. What happened? Answer the question and cite both source records. 2. What is still unknown? State the limits of these two events. 3. What should be checked next? Name one source and the question it could answer. HANDOVER (complete before running closeout) Required files opened and checked: Planned retained case-folder location: Manifest filename: package-sha256.csv (created by closeout) Warnings or failed attempts kept / explanation: This public sample contains two events from 2019. It is not an acquisition from your workstation or a complete incident history.