Reconstruct a Web Request
Break down a supplied request into method, path, headers, body and trust boundaries.
Break down a supplied request into method, path, headers, body and trust boundaries.
Prepare 20m · Build 110m · Verify 30m · Document 20m
Work only inside the folder created by Smartphone-Academy.py prepare request-anatomy. 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.
python Smartphone-Academy.py prepare request-anatomyNo root. Use the supplied files and keep the workspace under $HOME.Practical mission
- Label every request component and its origin
- Mark values controlled by the user or network
- Identify where authentication and authorization differ
- Describe safe logging choices for sensitive fields
An annotated request map and a list of validation responsibilities.
Quality gate
Analyst reflection
Which result from “Describe safe logging choices for sensitive fields” would need more evidence before it could support an operational decision?
After checking the evidence, run python Smartphone-Academy.py complete request-anatomy. Progress is stored locally in the Termux home directory.