Kioptrix Beginner Roadmap: Choose Your Next Lab Step

Do now: Check the original image, host support, every enabled adapter and the guest boot state. Keep the original files and a recovery reference.

Save: Save a setup note naming the image, software versions, intended network and recovery point.

Move on when: You can explain the setup, the VM boots and the intended lab connection is reviewed. Record whether restoration has actually been checked.

If blocked: If import or boot fails, repair that layer before target discovery.

Review the five setup checks → · Record this stage

Do now: Match the target VM MAC with its current lease or a discovery result on the confirmed lab segment. Check the Kali route to that address.

Save: Save the matched MAC/IP, source and time of the comparison, and selected Kali interface.

Move on when: You can distinguish the target from the host and DHCP service and explain the intended route.

If blocked: If the address or identity is uncertain, return to the adapter and addressing checks. Do not choose the first IP you see.

Match the VM to its current IP → · Record this stage

Do now: Use the confirmed target and save one baseline scan. Record exact options, selected protocol and ports, and whether it completed.

Save: Keep the original output files and a short explanation of the port states and untested coverage.

Move on when: You can open the saved result, identify its completion state and choose one responding service to inspect. If none is usable, review that result before moving on.

If blocked: A host-down message or interrupted run is not a finished service inventory. Check target identity and route first.

Run and read the first saved scan → · Record this stage

Do now: Choose one observed service. For HTTP, compare a real page with a deliberately missing path, keeping headers, bodies and redirects.

Save: Save the responses and the conditions under which you collected them. Write what differs and what still needs checking.

Move on when: You can explain one observed behavior and select a narrower follow-up. For product research, confirm what product evidence you actually have.

If blocked: If the response cannot be obtained, return to the service and connection observation. Similar error pages require comparison before accepting a discovered path.

Compare browser and curl responses → · Record this stage

Do now: Read the relevant primary documentation or original advisory. Compare product, version evidence, platform, configuration and access requirements.

Save: Write which conditions match, which conflict and which remain unknown, with source and observation references.

Move on when: You can explain why to investigate the lead further, retire it or collect a missing observation. You do not need a successful exploit to complete this research task.

If blocked: If a prerequisite conflicts, set the lead aside and return to the actual service evidence. Do not force a version match.

Research an identified service → · Record this stage

Do now: Use this stage whenever a result is unclear, including during setup. Name the first failing stage and inspect one assumption at a time.

Save: Save the original error, last confirmed observation, one changed or inspected condition and the comparison result.

Move on when: You can return to the affected stage with a better question or keep a specific blocker for help. This review is available throughout the roadmap.

If blocked: Return to the stage where evidence is missing. If the environment or target is uncertain, stop probing and resolve it there.

Open symptom-based troubleshooting → · Record this stage

Do now: Choose one claim from your actual notes. Write its starting conditions, actions, saved observations, interpretation and limits, then check whether those notes allow reproduction.

Save: Keep a short report, any reproduction differences, assistance used and the next skill to practise.

Move on when: The report distinguishes observed, inferred and untested results. An incomplete investigation can be reported honestly; mark an unperformed reproduction as untested.

If blocked: If a step cannot be reconstructed, return to that step and repair the record. Do not fill gaps with invented output.

Write the lab report → · Record this stage

Check only the foundation needed for the next action. These are small exercises, not an admission test.

• Files: create a notes folder, find its path, write a note and read it again.
• Networking: identify Kali’s interface, address and selected target route; use the route-reading example.
• VMs: distinguish the host, Kali and target, then use the setup checks.
• Notes: save an action, literal result, uncertainty and next question; see lab notes.

If a basic operation blocks the exercise, practise it separately in a simpler environment and return with that result.