The phases of a security assessment

An assessment is a short sequence of steps, and each one depends on the one before it. This set checks that you know what each phase is for and that you can run the first one on your own device.

4 questions 1 task Read the lesson

Questions

Each one is marked as you go, and the explanation arrives straight after, which is the part worth reading.

4 questions, marked as you go.

1 Why does an assessment begin with scope rather than with a scan?
2 What does the id command tell you that matters for an assessment?
3 Why record a timestamp and the kernel release before you change anything?
4 In the enumeration phase, an empty ss -tln listing is:

Tasks

These need your own device. Run the command in Termux, then paste what it printed. The marking looks at what the output means, so spacing, version numbers and ordering do not matter. If you have not installed anything yet, the lesson covers the setup.

Record the scope of your assessment

This prints the name of your device, your user id and groups, and the kernel name, release and machine type. It is the scope line of an assessment: what you are looking at, and as whom. Paste the three lines it prints.

Run this in Termux On your own device. Nothing on this page executes it. The command runs in your terminal, and this box only reads what you paste back.

hostname; id; uname -srm
Marking your own work Both halves of this are checked in your browser, with no server involved, so nothing stops you from pasting output you did not run. The tasks are written so that the easiest way to pass one is to actually do it and read the result, which is the whole intention.

All sets Read the lesson