OBJECTIVE

Turn the academy findings into prioritized defensive work for Android and Termux.

TIME PLAN

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

Working boundary

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

Practical mission

  1. Group findings into Android, Termux, storage and network areas
  2. Prioritize changes by risk reduction and effort
  3. Add a verification and rollback step for each change
  4. Identify updates that require user approval or backups
EVIDENCE TO PRODUCE

A 30-day hardening backlog with verification and rollback for every proposed change.

Quality gate

The deliverable states a clear scope and date for Produce a Device Hardening Plan.
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 “Schedule quick wins separately from disruptive changes” would need more evidence before it could support an operational decision?

Complete in Termux

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

15 · Identity & Hardening

Continue learning

Back to Smartphone Academy