Build a Cybersecurity Lab and Run a Scan

Set up Kali Linux in VirtualBox and run your first Nmap network scan.

Introduction

30 Second Summary

Every time you connect to Wi-Fi, dozens of services are silently listening on your device. Security professionals use specialized tools to discover these services and assess whether they pose a risk. That discovery process is called network scanning.

In this project, you will build a cybersecurity lab on your laptop using Kali Linux inside a virtual machine, learn to navigate the Linux terminal from scratch, then run your first real network scan using Nmap and document what you find in a security report.

What You'll Build

You will boot into Kali Linux, type a single command, and watch as Nmap maps out a remote server's open ports, running services, and operating system in real time.

By the end of this project, you'll have:

A reusable Kali Linux VM you can launch anytime to practice security tools in a safe, isolated environment.
Completed Nmap scans that discover live hosts, open ports, and the services running behind them.
The ability to read scan output and explain what open, closed, and filtered ports mean for a target's security posture.
A security findings report that documents your discoveries the way a professional analyst would.
Secret Mission: Run a service version detection scan and identify the exact software versions running on the target.

Are there any prerequisites?

None. This guide walks you through installing every tool from scratch, including VirtualBox and Kali Linux. You just need a Windows laptop with at least 16 GB of RAM and around 15 GB of free disk space.

Before We Start

Before we dive in, let's lock in what you're about to build and why it matters. Naming your goal up front turns a walkthrough into a mission.

Set Up Your Cybersecurity Lab

Security tools like Nmap can probe networks and discover vulnerabilities. Running them directly on your Windows system risks accidental scans of devices you do not own. You need an isolated sandbox where you can safely experiment without affecting your laptop or anyone else's network.

A virtual machine solves this problem. You will install VirtualBox to run a complete Kali Linux operating system inside a window on your desktop. Kali comes pre-loaded with hundreds of security tools, including the scanner you will use in the next steps.

In this step, get ready to:

Install 7-Zip and VirtualBox on Windows.
Download and extract the Kali Linux VM image.
Import and boot the Kali VM.

Install 7-Zip and VirtualBox on Windows

You need two tools before you can run Kali Linux. 7-Zip extracts the compressed VM image, and VirtualBox runs the virtual machine itself.

Let's check whether you already have 7-Zip installed.

Press the Windows key and type 7-Zip.

✔️ I see 7-Zip in my search results

You already have 7-Zip installed. You are all set for the extraction step later.

ⓧ I don't see 7-Zip

Open your browser and go to https://www.7-zip.org/download.html.
Download the 64-bit x64 .exe installer (1.6 MB, version 26.02).
Run the downloaded installer.
Click Install and accept all default settings.
Click Close when the installation finishes.

7-Zip is now installed on your system.

Now let's check whether you already have VirtualBox installed.

Press the Windows key and type VirtualBox.

✔️ I see VirtualBox 7 or newer

Open VirtualBox.
Click Help in the menu bar, then click About VirtualBox.
Confirm the version number starts with 7. If it does, you are ready to proceed.

Close the About dialog and continue to the next substep.

ⓧ I see an older version (6.x or earlier)

The Kali Linux 2026.2 VM requires VirtualBox 7 or newer. You need to upgrade.

Uninstall your current VirtualBox from Settings > Apps > Installed apps.
Restart your computer.
Follow the full install instructions in the next tab to install VirtualBox 7.2.14.

ⓧ VirtualBox is not installed

Open your browser and go to https://www.virtualbox.org/wiki/Downloads.
Under Platform Packages, click Windows hosts to download the installer (approximately 170 MB).
Run the downloaded installer.
Click Next through each screen, accepting all defaults.
When prompted to install network adapters, click Yes to allow the installation. Your network may briefly disconnect.
Click Install, then Finish when it completes.

VirtualBox 7.2.14 is now installed.

VirtualBox installer failed or VM won't start?

The most common cause is Hyper-V conflicting with VirtualBox. Windows sometimes enables Hyper-V by default, and it blocks VirtualBox from using your CPU's virtualization features.

Open Task Manager, click the Performance tab, and look at the CPU section. If "Virtualization" shows as Disabled, you need to enable VT-x in your BIOS. Restart your computer and press F2, F10, or Del during startup to access BIOS settings.

If virtualization is already enabled but the VM still fails, disable Hyper-V by pressing the Windows key, typing Turn Windows features on or off, unchecking Hyper-V and Windows Hypervisor Platform, then restarting your computer.

Help me fix VirtualBox not starting on my Windows machine.

Why VirtualBox instead of WSL?

Windows Subsystem for Linux (WSL) can run Linux tools, but it only gives you a command line. VirtualBox provides full isolation and the complete Kali desktop experience, including GUI tools you will use later in your degree.

Managing virtual machines is also a core skill in cybersecurity. Professionals spin up isolated VMs to test exploits, analyze malware, and replicate client environments safely.

Confirm VirtualBox opens by pressing the Windows key, typing VirtualBox, and pressing Enter.

You should see the VirtualBox Manager window with an empty list of virtual machines. Leave it open for the next substep.

Download and extract the Kali Linux VM image

Kali Linux provides a pre-built VM image so you do not need to install the operating system from scratch. The image is a compressed archive that contains a ready-to-run virtual machine.

Open your browser and go to https://www.kali.org/get-kali/.
Navigate to the Pre-built Virtual Machines section.
Download the VirtualBox image file named kali-linux-2026.2-virtualbox-amd64.7z (approximately 3.7 GB).

This download takes time

The file is 3.7 GB. Depending on your internet speed, this could take anywhere from 5 minutes to over an hour. This is a good time to grab a coffee or review what you have learned so far.

Once the download completes, open File Explorer and navigate to your Downloads folder.
Right-click the kali-linux-2026.2-virtualbox-amd64.7z file.
Select 7-Zip > Extract Here.
Wait for the extraction to complete. This creates a folder containing a .vbox file.

Open the extracted folder. You should see a file ending in .vbox inside it. This is the virtual machine configuration file you will import next.

Don't see the 7-Zip option in the right-click menu?

On Windows 11, right-click the file and select Show more options to see the full context menu with the 7-Zip entry.

If 7-Zip still does not appear, the installation may not have completed. Re-run the 7-Zip installer and restart File Explorer.

Help me extract the Kali .7z file on Windows.

Import and boot the Kali VM

With the VM image extracted, you can now import it into VirtualBox and boot your cybersecurity lab for the first time.

Switch to the VirtualBox Manager window you opened earlier.
Click Add in the toolbar (not New).
Navigate to the extracted folder in your Downloads directory.
Select the .vbox file and click Open.

The Kali Linux VM now appears in your VirtualBox list on the left side.

Before you boot it, what do you think you will see when the VM starts? A login screen? A desktop? An error message?

Select the Kali VM in the list and click Start (the green arrow).
Wait for the VM to boot. A login screen appears after 30-60 seconds.
Enter the username kali.
Enter the password kali.
Press Enter to log in.

You should now see the Kali Linux desktop with a dark theme, a taskbar at the top, and the Kali dragon logo on the wallpaper. Your cybersecurity lab is running.

VM won't start or shows a virtualization error?

If you see a message about VT-x not being available, your CPU's virtualization feature is either disabled in the BIOS or claimed by another Windows service (like Hyper-V or Memory Integrity).

First, open Task Manager (press Ctrl+Shift+Esc), click Performance, and check the CPU section. If "Virtualization" says Disabled, restart your computer and enter BIOS (press F2, F10, Del, or Esc during startup). Enable Intel VT-x or AMD-V under the CPU or Advanced settings. Save and reboot.

If virtualization shows as Enabled but the VM still fails, disable Hyper-V and Memory Integrity. Press the Windows key, search for Turn Windows features on or off, uncheck Hyper-V and Windows Hypervisor Platform, then restart.

My Kali VM won't boot in VirtualBox. Help me fix it.

Your cybersecurity lab is up and running. Next up, you will learn to navigate the Linux terminal and confirm your scanning tools are ready to go.

Learn to Navigate the Linux Terminal

Your cybersecurity lab is live. You have Kali Linux running inside VirtualBox and you are sitting at the desktop.

Every security tool you will use in your degree runs from the command line. You cannot launch a scan, save results, or navigate your file system without knowing how to type commands into a terminal and read what comes back.

In this step, get ready to:

Open the Linux terminal and run your first commands.
Navigate directories and create a folder to store your scan results.
Confirm that Nmap (your scanning tool) is installed and ready.

Open the terminal and learn your first commands

The terminal is where you type commands and read their output. Think of it as a text-based way to control your computer.

On your Kali Linux desktop, right-click anywhere on the empty desktop background.
Select Open Terminal Here from the menu that appears.

A black window appears with a blinking cursor. This is your terminal.

Alternative way to open the terminal

You can also click the terminal icon in the taskbar at the top of the screen. Both methods open the same application.

Find out where you are in the file system by running this command:

pwd

You should see /home/kali printed on the next line. This is your home directory.

What does pwd mean?

It stands for "print working directory." It tells you exactly which folder you are currently inside. You will use this command constantly to stay oriented.

See what files and folders exist here by running:

ls

You should see folder names like Desktop, Documents, and Downloads listed in the output.

What does ls do?

The ls command lists the contents of your current directory. It is short for "list." Any time you want to see what is inside a folder, run ls.

Terminal not opening?

If right-clicking the desktop does not show the Open Terminal Here option, try clicking the terminal icon in the top taskbar instead. If the taskbar is not visible, move your mouse to the very top of the screen.

help me open the terminal in Kali Linux

Practice navigating and creating files

Now that you can see where you are and what is around you, it is time to move between folders and create a new one for your scan results.

Move into your Desktop folder by running:

cd Desktop

Confirm you moved to the right place by running:

pwd

You should see /home/kali/Desktop printed. The cd command stands for "change directory" and moves you into the folder you name after it.

Create a new folder called scan-results by running:

mkdir scan-results

Confirm the folder was created by running:

ls

You should see scan-results listed in the output. This is the folder where you will save your Nmap scan output later.

What does mkdir do?

The mkdir command stands for "make directory." It creates a new empty folder with whatever name you give it.

Move into your new folder by running:

cd scan-results

Verify your current location by running:

pwd

You should see /home/kali/Desktop/scan-results printed. You are now inside the folder where all your scan output will be saved.

Seeing 'No such file or directory'?

This means you typed the folder name differently than what exists. Linux is case-sensitive, so Desktop and desktop are two completely different names. Run ls to see the exact folder names available, then re-run your cd command with the exact spelling shown.

help me fix a 'No such file or directory' error in the Linux terminal

Confirm Nmap is ready

Your terminal skills are working. The last thing to confirm before you start scanning is that Nmap, your network scanning tool, is installed and accessible.

Before you run the next command, what do you think will happen? Nmap comes pre-installed on Kali Linux. Do you expect to see an error, or version information?

Check that Nmap is installed by running:

nmap --version

You should see output showing Nmap version 7.99 (or similar) along with a list of compiled features. This confirms your scanning tool is ready to use.

What is Nmap?

Nmap is a free, open-source network scanner used by security professionals to discover devices on a network and find open ports. It is the most widely used reconnaissance tool in cybersecurity.

Kali Linux comes with Nmap pre-installed because it is considered an essential security tool. You did not have to install it yourself.

Seeing 'command not found'?

This is extremely unlikely on Kali Linux since Nmap is pre-installed. Double-check that you typed nmap in all lowercase with two dashes before version. Make sure there is a space between nmap and --version.

help me fix nmap command not found in Kali Linux

You now have three essential terminal commands in your toolkit: pwd to see where you are, ls to see what is around you, and cd to move somewhere new. Next up, you will use Nmap to discover what is running on a real network target.

Discover What Is on a Network

Before you can assess vulnerabilities, you need to know what actually exists on a network. Which machines are online? Which ports are accepting connections? These are the questions that network reconnaissance answers.

In this step, you will perform your first scans against scanme.nmap.org. This is a server that the Nmap project explicitly authorizes for practice scanning. You will discover whether the host is alive, which ports are open, and what services are listening.

In this step, get ready to:

Run a host discovery scan to confirm the target is online.
Run a basic port scan to find open ports and service names.
Interpret port states (open, closed, filtered) and understand what they reveal.

Run a host discovery scan

The first question in any reconnaissance task is simple: is the target even online? A host discovery scan answers that question without touching any ports.

In your terminal (you should already be in the scan-results folder), run this host discovery scan:

nmap -sn scanme.nmap.org

What does this command do?

The -sn flag tells Nmap to perform a ping scan only. It checks whether the host is alive without scanning any ports.

This is the lightest possible scan. It confirms the target exists and is reachable before you invest time in deeper scanning.

You should see output similar to:

Nmap scan report for scanme.nmap.org (45.33.32.156)
Host is up (0.034s latency).

The Host is up message with a latency measurement confirms the target is online and reachable from your Kali VM.

Not seeing 'Host is up'?

Check that your Kali VM has internet access. Try running ping -c 2 google.com to verify connectivity.
If you see 'Host seems down', your network may be blocking ICMP packets. Try running nmap -Pn -sn scanme.nmap.org which skips ping and assumes the host is up.
Make sure you typed the target correctly: scanme.nmap.org (no typos, no www prefix).

Why can't Nmap reach my target?

Run a basic port scan

You have confirmed the target is alive. The next question is: what doors are open on this machine? Each open port represents a running service that accepts connections from the network.

Before you run the next scan, think about this: what information do you expect a port scan to give you about the target? Will it tell you which specific software versions are running?

Run a basic port scan by entering this command:

nmap scanme.nmap.org

What does this command do?

Without any flags, nmap scans the 1,000 most common TCP ports on the target. For each port, it reports whether the port is open, closed, or filtered.

This takes around 10-30 seconds to complete depending on network conditions.

Wait for the scan to finish. You will see a table like this in your terminal:

PORT      STATE SERVICE
22/tcp    open  ssh
80/tcp    open  http
9929/tcp  open  nping-echo
31337/tcp open  Elite

Your results may vary slightly, but you should see at least ports 22/tcp and 80/tcp listed as open.

Scan seems stuck or shows no results?

Port scans take longer than ping scans. Wait at least 60 seconds before assuming something is wrong.
If the scan times out completely, your network may be throttling outbound traffic. Try nmap -T3 scanme.nmap.org for a slower, more patient scan.
If you see all ports as 'filtered', a firewall between you and the target is blocking probes.

Why is my Nmap port scan not returning results?

Understand port states

Look at the results in your terminal. Each row tells you something specific about the target machine.

What do port states mean?

Open means a program is actively listening for connections on that port. This is what attackers look for because it represents a potential way in.
Closed means the port is reachable but no service is listening. Nothing is running there right now.
Filtered means a firewall is blocking Nmap's probes. You cannot determine whether a service exists behind it.

Your scan revealed that port 22 runs SSH (remote access) and port 80 runs HTTP (a web server). This is real reconnaissance data.

But notice what is missing. You know SSH is on port 22, but which version of SSH? You know a web server is on port 80, but is it Apache, Nginx, or something else? You have no idea what operating system the target runs.

This is the limitation of a basic scan. It tells you which doors are open, but not what is behind them.

Even a simple scan like this reveals what services a target is running. This is the foundation of every security assessment. In the next step, you will run a deeper scan that fills in the blanks: exact software versions, operating system, and the network path to the target.

Run a Deep Scan and Save Your Results

Your basic scan in the previous step confirmed that scanme.nmap.org has open ports. Knowing a port is open is useful, but it tells you nothing about what software is listening behind it.

Without details like the operating system, software versions, and network route, your security report would be incomplete. In this step, you'll use Nmap's -A flag to uncover all of this in a single command and save the results to a file.

In this step, get ready to:

Run an aggressive scan and save the output to a text file.
Review the saved scan results.
Compare the basic scan with the deep scan.

Run an aggressive scan with output saved to a file

Your scan-results folder is still empty. This next command fills it with a comprehensive report about the target.

Scan scanme.nmap.org with OS detection, version detection, script scanning, and traceroute enabled, saving the output to a text file, by running this command:

nmap -A -T4 -oN scanme-deep-scan.txt scanme.nmap.org

What does this command do?

-A enables OS detection, version detection, script scanning, and traceroute all at once.
-T4 adjusts timing to an aggressive level for faster execution.
-oN scanme-deep-scan.txt saves the output in normal human-readable format to a file called scanme-deep-scan.txt.

This scan takes 30 to 60 seconds to complete. Watch your terminal as results stream in.

You'll see much more detail than your basic scan produced: service versions next to each port, OS guesses at the bottom, and the network hops between you and the target.

Scan timing out or not completing?

Make sure your Kali VM has internet access. Try running ping -c 2 scanme.nmap.org to confirm connectivity.
If you see "Failed to resolve" in the output, your VM's network adapter may be disconnected. In VirtualBox, check that the VM's network adapter is set to NAT or Bridged mode under the VM's Settings.

Scan still stuck? Help me troubleshoot why my Nmap aggressive scan isn't completing in Kali Linux.

Review your saved scan results

The scan is done, and the results are saved to a file in your current folder. Before you display it, think about what sections you expect to see that were missing from your basic scan in Step 3.

Display the contents of your saved scan report by running:

cat scanme-deep-scan.txt

You should see the full scan report printed in your terminal. Look for these key sections:

The port table now has a VERSION column filled in, showing the software behind each open port.
An OS detection section showing what operating system the target likely runs.
A TRACEROUTE section showing the network hops between your VM and the target.

Why does this matter for security work?

Each piece of information in this report is something a real penetration tester would use to plan their next steps. Knowing that port 22 runs a specific version of OpenSSH, for example, lets you search for known vulnerabilities in that exact version.

Seeing "No such file or directory"?

Run pwd to check you are still in /home/kali/Desktop/scan-results. If not, run cd ~/Desktop/scan-results to get back there.
If the file does not exist, your scan may not have completed successfully. Re-run the nmap command from the previous substep and wait for it to finish.

Still can't find your scan file? Help me find my saved Nmap scan output.

Compare the basic scan with the deep scan

What did the deep scan add?

Your basic scan from Step 3 only told you that ports 22 and 80 are open. The deep scan tells you WHAT is running on those ports (for example, OpenSSH on port 22 and Apache on port 80), what OS the target uses, and the network path to reach it.

This is why security professionals always run multiple scan types. Each pass reveals more about the target, building a fuller picture for your security report.

You now have a saved scan report packed with actionable intelligence about the target. Next up, you'll turn this raw data into a professional security findings report that documents what you discovered.

Write Your Security Findings Report

Running scans is only half of a security professional's job. The real deliverable is a structured report that communicates what you found to someone who can act on it.

In this step, you will use the nano text editor to write a security findings report. Your report will document the open ports, services, and potential risks you discovered in your scans.

In this step, get ready to:

Create a report file with a professional header section.
Document your scan findings including ports, OS detection, and risk assessment.
Save and verify the completed report.

Create your report file

You will need to reference the details from your deep scan while writing the report. Before opening the text editor, review your scan results so you can scroll back to them later.

Display your scan results by running this command:

cat scanme-deep-scan.txt

Note the open ports, service versions, and OS detection information. You will reference these values in your report.

Open the nano text editor to create your report file by running:

nano security-report.txt

What is nano?

Nano is a simple terminal-based text editor that comes pre-installed on Kali Linux. It lets you create and edit files directly from the command line without needing a graphical application.

You should now see a blank editing screen with a toolbar of shortcuts at the bottom. Type the following header at the top of the file:

SECURITY SCAN REPORT
Date: [[TODAYS_DATE="today's date, e.g. 2026-07-27"]]
Scanner: Nmap
Target: scanme.nmap.org
Analyst: [[YOUR_NAME="your name"]]

What does the header contain?

Every professional security report starts with metadata identifying when the scan was performed, what tool was used, what target was scanned, and who conducted the assessment. This makes the report traceable and accountable.

Document your findings

Below your header, you will add three sections that transform raw scan data into actionable intelligence. Each section answers a different question about the target.

Leave a blank line after the header, then type a FINDINGS section listing each open port you discovered. Use the port numbers, service names, and versions from your scan output. Here is the format to follow:

FINDINGS
Port 22/tcp - OPEN - SSH ([[SSH_VERSION="version from your scan, e.g. OpenSSH 9.8p1"]])
Port 80/tcp - OPEN - HTTP ([[HTTP_VERSION="version from your scan, e.g. Apache httpd 2.4.62"]])

What if my scan showed different ports?

Your scan results may differ slightly from this example. Write one line for every port that showed as open in your deep scan. Copy the exact version strings from your scanme-deep-scan.txt output.

Below your findings, add an OS DETECTION section noting what operating system was identified in your scan.
Below that, add a RISK NOTES section. For each open port, write one sentence about why it could be a security concern. Here is the format to follow:

OS DETECTION
Operating System: [[OS_DETECTED="OS from your scan, e.g. Linux 5.x"]]

RISK NOTES
- SSH on port 22 could allow unauthorized access if weak credentials are used.
- HTTP on port 80 exposes a web server that could be vulnerable to web-based attacks.

Why do risk notes matter?

An open port is a fact. A risk note is your professional judgment about what that fact means for security. This is what separates a useful report from a raw data dump.

In a real engagement, the system owner reads your risk notes to understand what needs fixing and how urgently.

Save and verify your report

Your report is complete inside nano. Now you need to save it to disk and confirm it was written correctly.

Press Ctrl+O to save the file.
Press Enter to confirm the filename security-report.txt.
Press Ctrl+X to exit nano and return to your terminal.

Before you run the next command, what sections do you expect to see in the output?

Display your finished report by running:

cat security-report.txt

You should see your completed report with the header, findings, OS detection, and risk notes all printed in the terminal.

Report is empty or missing sections?

If cat shows nothing, you may have exited nano without saving. Run nano security-report.txt again to reopen the file and check if your text is still there. If it is empty, retype your content and save with Ctrl+O before exiting.

If only some sections appear, reopen the file with nano security-report.txt and add the missing sections. Make sure you pressed Ctrl+O then Enter to confirm the save.

Help me troubleshoot my nano save issue

✔️ Awesome, I've got everything!

Great. Make sure you have saved security-report.txt and confirmed all sections are present.

ⓧ I'd like to double check the full report

Your security-report.txt should contain these sections in order. The exact versions and OS will match your own scan results:

A SECURITY SCAN REPORT header with Date, Scanner, Target, and Analyst fields.
A FINDINGS section with one line per open port showing the port number, state, service name, and version.
An OS DETECTION section noting the identified operating system.
A RISK NOTES section with one risk sentence per open port.

If anything is missing, run nano security-report.txt to reopen the file and add the missing sections. Save with Ctrl+O then Enter, and exit with Ctrl+X.

You have just produced your first security deliverable. In a real engagement, this report would go to the system's owner so they can fix the issues you identified.

Secret mission

Service Version Detection Deep Dive

Real penetration testers do not stop at knowing a port is open. They need exact software versions to search for known vulnerabilities. In this challenge, you will perform targeted version detection and research real-world CVEs associated with what you find.

Clean Up Your Resources

Decide whether to keep your resources running, pause them to come back later, or delete them entirely. This project runs entirely locally on your machine, so there are no ongoing costs.

Resources you used:

Kali Linux VM (running inside VirtualBox, using disk space and RAM when active).
Oracle VirtualBox (installed on Windows).
7-Zip (installed on Windows).
Downloaded Kali Linux .7z file and extracted VM folder on your Windows filesystem.

Keep everything running

No action needed. Choose this if you plan to keep practicing with your cybersecurity lab.

Your Kali VM, VirtualBox, and 7-Zip all stay installed and ready to use.
Your scan results and security report remain saved inside the VM at /home/kali/Desktop/scan-results.
You can launch your Kali VM anytime from VirtualBox to continue learning security tools.

Pause - I'll come back to this later

Shut down the Kali VM to free up RAM. Your files and settings are preserved on disk.

Inside the Kali VM, click the power icon in the top-right corner of the desktop and select Shut Down.
Alternatively, in VirtualBox Manager, right-click your Kali VM and select Close, then Power Off.
The VM stays in your VirtualBox list. Click Start when you want to resume.
VirtualBox and 7-Zip remain installed but use no resources when idle.

Delete - I don't want to use this again

Remove all project resources from your machine entirely.

Shut down the Kali VM if it is still running.
In VirtualBox Manager, right-click the Kali VM and select Remove.
When prompted, select Delete all files to remove the virtual disk from your computer.
Delete the original downloaded kali-linux-2026.2-virtualbox-amd64.7z file and the extracted folder from your Downloads directory.
To uninstall VirtualBox: press the Windows key, type Add or remove programs, press Enter. Find Oracle VirtualBox in the list, click it, and select Uninstall.
To uninstall 7-Zip: in the same Add or remove programs screen, find 7-Zip, click it, and select Uninstall.

Nice Work!

You just built a fully functional cybersecurity lab from scratch and completed your first real network reconnaissance scan. You can now set up professional security tools, operate in a Linux environment, and document findings like a security analyst.

You've learned how to:

Build a cybersecurity lab with Kali Linux running inside VirtualBox and use essential Linux terminal commands to navigate the system.
Use Nmap to perform host discovery, port scanning, and aggressive scanning against an authorized target, then interpret scan results including port states, service versions, and OS detection.
Write a professional security findings report that documents open ports, running services, risk notes, and actionable information for a system owner.
Secret Mission: Perform targeted version detection and research real CVEs associated with the software you discovered.

Ready to quiz yourself?