OBJECTIVE

Classify changes reported by the integrity-monitor lab in a simulated incident.

TIME PLAN

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

Working boundary

Work only inside the folder created by Smartphone-Academy.py prepare change-triage. 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 change-triageNo root. Use the supplied files and keep the workspace under $HOME.

Practical mission

  1. Compare the incident snapshot with the trusted baseline
  2. Attribute expected changes to documented maintenance
  3. Prioritize unexplained executable and configuration changes
  4. Preserve uncertain items for further review instead of deleting them
EVIDENCE TO PRODUCE

A change register with expected, suspicious and unresolved categories.

Quality gate

The deliverable states a clear scope and date for Triage File Changes.
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 “Preserve uncertain items for further review instead of deleting them” would need more evidence before it could support an operational decision?

Complete in Termux

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

14 · Defensive Monitoring

Continue learning

Back to Smartphone Academy