OBJECTIVE

Merge synthetic file, authentication and network events into a defensible sequence.

TIME PLAN

Prepare 20m · Build 110m · Verify 30m · Document 20m

Working boundary

Work only inside the folder created by Smartphone-Academy.py prepare incident-timeline. Use the supplied samples or systems you personally administer.

Prepare the Termux workspace

Open Termux in the Academy root and prepare this lab with the local companion. It creates safe samples, notes and evidence files under your Termux account.

Android + Termuxpython Smartphone-Academy.py prepare incident-timelineNo root. Use the supplied files and keep the workspace under $HOME.

Practical mission

  1. Normalize all source timestamps before sorting
  2. Keep original source and record identifiers in every row
  3. Mark inferred ordering when timestamps collide
  4. Write a concise narrative that does not exceed the evidence
EVIDENCE TO PRODUCE

A timestamped timeline with source citations, uncertainty and key pivots.

Quality gate

The deliverable states a clear scope and date for Construct an Incident Timeline.
A second learner can reproduce the commands and paths.
Original samples remain unchanged and verifiable.
Limitations are recorded beside the conclusions.

Analyst reflection

Which result from “Write a concise narrative that does not exceed the evidence” would need more evidence before it could support an operational decision?

Complete in Termux

After checking the evidence, run python Smartphone-Academy.py complete incident-timeline. Progress is stored locally in the Termux home directory.

14 · Defensive Monitoring

Continue learning

Back to Smartphone Academy