What Kali and Parrot Security are, and why they wait

02Read the distributions' purpose

Kali's developers describe it as designed for professional security testing and auditing. Their guidance recommends learning Linux foundations first if you are unfamiliar with Linux or want a general-purpose desktop. A security-focused distribution can have different defaults and support assumptions from the desktop you already use.

Parrot has different editions. Home is intended for ordinary use without the security tool collection; Security includes security tools. Record the edition when comparing environments rather than assuming every image contains the same programs.

Ubuntu is sufficient for the next file-navigation lesson. Later tool lessons explain why another environment might help, what it requires and which target is permitted. Keep the current baseline until you have a specific reason to change it.

03Try task-to-environment choices

Use the task cards without downloading another distribution. Compare needed capabilities with available ones.

Choose an environment from the task
Fictional task cards; no installation or benchmark is involved.

Distribution: an operating system supplied with selected software
and defaults. A package is software supplied as an installable unit.
Ubuntu: the course environment for desktop and shell foundations.
Kali: designed for security-testing work; learn Linux foundations first.
Parrot Home: ordinary use, without the security tool collection.
Parrot Security: an edition including security tools.
Tools still require permission for their actions and targets.

Activity A: navigate personal guest folders and make a harmless note.
Activity B: a later lesson names a tool for a specific authorized lab.
For each, record the needed capability and what you would check before
changing environments. A security label alone is not a reason to install.

Separate question case:
The next beginner lesson uses the Ubuntu shell to navigate local files.
Is Ubuntu sufficient, or is Kali required for this task?
Answer format: sufficient or required.

1. For Activity A, list the capabilities needed to navigate your own folders and make a harmless note. Compare them with Ubuntu's file manager, editor and shell. Expected: no additional security tool collection is needed.
2. For Activity B, write what you would need from the later lesson before choosing another environment: tool name, prerequisites, compatible resources, permitted target and a way to stop or reset the lab.
3. Give one reason to wait and one reason a second guest might later help. For example, another guest uses resources now but could keep a particular later tool setup separate from the baseline.
4. Finish your note without installing anything. If you opened a guest to read the card, shut it down normally. Otherwise this paper activity needs no cleanup.

04The lab recovery case

Use the recovery card below to combine the whole stage. Write a short note using its fictional evidence, or use clearly labelled observations from your own setup. The site does not grade this note; review it using the following rubric.

Name the host and guest separately, and record architecture and resources. Distinguish the saved editor program, its running process, saved task.txt and unsaved working data. Identify the guest viewer as the client requesting the remote note. Predict that restoring clean removes the later guest temporary folder while the earlier practice folder remains. Exclude the host receipt and remote service.

Finish by choosing Ubuntu for the next local-file task and stating a stop rule for unclear permission or disk targets. Say whether installation and restoration were actually observed or are still deferred. Keep passwords and personal identifiers out of the note. If practical setup is deferred, use the next stage's text alternatives until you have a suitable environment.

Computers: your setup and recovery note
Fictional case; no installation or restore was observed.

Owned Windows 11 x86-64 host; compatible hypervisor assumed.
Ubuntu 24.04 LTS Desktop guest; new normal disk; no host sharing.
NAT network mode; no port forwarding. Terminal belongs to the guest.
Saved editor program; one running editor process, PID 81.
Saved guest task.txt and unsaved editing data are separate.
Snapshot clean: guest Documents/practice exists and is empty.
Later: guest practice/temporary is created; a host receipt is saved;
the guest viewer requests a note from a remote service.

Use this case, or clearly separated observations from your own setup.
Record: permission; host/guest identity; architecture and resources;
saved files and running work; requester/responder; restore prediction;
host and remote exclusions; next Ubuntu file-navigation task.
Explain why another tool distribution can wait.
Include a stop rule for unclear disk targets or permission.
If using the fictional case, write installation and live restore deferred.

05Optional challenge

Read the official Kali and Parrot descriptions below. Compare their purposes and Parrot editions. Explain one task where a separate tool guest could help and one where Ubuntu already supplies the needed capability. No image download or security test is required.

06Carry forward an evidence note

Keep five headings in later practice notes: task and permission; environment; action; observed result or prediction; next check and safe stopping point. The next stage begins with commands and local files. If you completed the text route, carry its deferred setup steps forward honestly; a sound prediction and a performed operation are different kinds of evidence.

07Fresh cases for the checks

Use these fictional cases for the checks below. They have different inputs from the worked examples. Read them here or make notes; no installation or external service is needed.

Current baseline: an Ubuntu guest with a shell, file manager and text editor.
Separate checked guest: Kali with the fictional Case Reader tool already supplied.
For this case, its compatibility, resources and recovery plan have been checked.
Parrot Home: ordinary-use edition without the security tool collection.
Parrot Security: edition including security tools; no particular tool is established here.
 
A1: Read two owned local .txt notes and save a comparison. Keep the current baseline.
A2: A later authorized lab explicitly requires Case Reader in the separate checked guest.
A3: A later activity is described only as security work; its tool and prerequisites are not yet named.
For A3, decide whether there is enough information to choose an additional guest now.
These are fictional planning cases. No installation or tool use is requested.

Niko owns the disposable lab guest museum.
The course scope permits Niko to inspect only the supplied local file trace-one.cap
using Case Reader. It permits no network requests and no other capture files.
Case Reader is installed. Its menu can open capture files or send test traffic.
Other available items: trace-two.cap, not included in this permission;
the guest museum as a possible network target; and a public demonstration service.
Decide from this written scope. Do not open a file or send traffic.

Authorization: the learner may set up a disposable guest on this owned host.
Recorded observation: the host VM manager displays an entry named Ubuntu-study.
Its details show a virtual disk and an attached installer ISO.
No guest desktop, installed-disk boot or restore inspection has been recorded.
 
Separate fictional recovery model, not an observation of Ubuntu-study:
A powered-off snapshot start includes a normal guest disk.
At start, guest Documents/reading exists and is empty.
Later, guest Documents/reading/draft is created.
The model assumes no further changes and excludes host storage.

This is a new supplied record for a different disposable guest, Cedar.
Before a change, its normal-disk snapshot ready records Documents/case empty.
After the change, an inspection records Documents/case/extra present.
Recorded action: shut down, restore ready, then start Cedar.
Recorded inspection after that action: the same Documents/case exists and is empty.
No host-drive failure or independent-backup recovery was attempted.

08Carry an honest setup and recovery note

Optional self-check: write a short note for card C using these headings: task and permission; environment; action; observed result or prediction; next check and stopping point. State what extra evidence would be needed before claiming a successful installed-disk boot or a completed restore.

Check your note: distinguish the host manager from the guest, preserve the supplied permission, and keep the separate fictional model labelled as a prediction. A guest boot needs its own evidence; a restore needs a recorded action and inspection of the intended guest path. Choose tools from a named task and record the edition when comparing distributions. Keep installation and live restoration deferred where the record does not establish them.