Reference no: EM134013792

Assessment:

Overview

Assessment tasks Learning Outcome Mapping

Project Report - Group Introduction

This guide helps you set up a closed virtual lab for the group penetration test. You will run an attacker VM (Kali Linux) and one or more target VMs (instructor-supplied OVAs such as Metasploitable2 or other target images). All testing must stay inside this isolated lab network.

Students working on Data Communication And Networking projects should ensure the lab environment remains fully isolated during testing activities.

Important:

Do not scan or attack live campus/Internet hosts.
Only test the provided VMs or instructor-approved lab images.

Files you must have:

Kali Linux OVA or installer image (Kali current release).
Target OVA(s) - e.g., Metasploitable2 OVA or instructor-supplied target images.Use official sources for Kali and Metasploitable2 as directed by your instructor in the step-by-step guide.

VirtualBox: create the lab network (recommended)

We recommend an Internal Network named labnet (isolated from your real network).

1. Open VirtualBox -) File -+ Host Network Manager (optional if using Host-Only).
2. For simplicity use Internal Network: when configuring each VM's network adapter set Attached to -) Internal Network and Name -) labnet. (Alternative: use Host-Only Adapter if instructor prefers.)
3. No Internet is required. Keep it isolated.

Importing OVAs (Kali & targets)

1. In VirtualBox: File -) Import Appliance -) select the OVA file Next -) Import.
2. Repeat for each target OVA.
3. After import, check each VM's settings:
o System -) ensure enough RAM (Kali: 2-4 GB min; targets per instructor).
o Network -) Adapter 1: Internal Network (Name: labnet).
o Storage -) verify disks are present.

Starting the lab VMs

1. Start the target VM(s) first.
2. Start the Kali VM last (attacker).
3. Log in to each VM. For Linux targets, find their IP with ip a or ifconfig (inside the VM). On Kali you can also use arp -a or an initial nmap -sn 192.168.56.0/24 to discover live hosts.

Practical exercises using Linux environments can help students better understand penetration testing workflows and virtual machine management.

Recommended IP addressing

Use subnet:
- Subnet: 192.168.56.0/24
- Kali: 192.168.56.100
- Target1: 192.168.56.101
- Target2: 192.168.56.102
But it's fine to use DHCP inside the internal network or rely on discovery commands to learn IPs.

Take snapshots BEFORE testing

Critical: Take a snapshot of every target VM before you begin any active testing. This allows reset if something breaks.
- VirtualBox Right-click VM -) Snapshots -) Take Snapshot name pre-test.

Basic tools students will use (Kali)

nmap (scanning)
netcat nc (banner probing)
enum4linux smbclient (SMB enumeration)
wget, curl (file retrieval)
Nikto nikto (web vuln scans)
sqlmap (SQL injection testing, only on lab targets)
Burp Suite / OWASP ZAP (web app testing)
Metasploit (controlled exploitation)
John the Ripper, Hydra (password testing, with lab-only credentials)
Nessus or OpenVAS (vulnerability scanner) - optional/if instructed
Wireshark (packet capture)
msfconsole, msfvenom (Metasploit tooling)

Database testing and query-based vulnerabilities may also relate to concepts covered in Database Management Dbms assignments.

Recommended lab workflow (high-level)

1. Snapshot targets.
2. Host discovery: nmap -sn 192.168.56.0/24
3. Port & service scan: nmap -sS -sV -p- -T4 192.168.56.101
4. Targeted scans: nmap -sC -sV --script vuln 192.168.56.101
5. Banner grabs / simple probes: nc -v 192.168.56.101 80 or curl -I https://192.168.56.101/
6. Enumerate SMB: enum4linux -a 192.168.56.101 or smbclient -L //192.168.56.101 -N
7. Web testing: browse locally or use Burp/Nikto/sqlmap on discovered web apps.
8. Nessus scan (if permitted): run host discovery and vulnerability scans, export results to HTML/PDF for evidence.
9. Research CVEs for top findings (link Nessus problem to CVE details).
10. Controlled exploitation: use a PoC exploit against the vulnerable lab target (only use Metasploit or manual exploit as allowed by RoE). Keep it safe and document every step.
11. Remediate: patch, change config, and re-scan to demonstrate remediation where required. Then restore snapshot if needed.

Useful command examples (students should save outputs)

• Host discovery (ping sweep): nmap -sn 192.168.56.0/24 -oN outputs/nmap_ping_sweep.txt
• Full TCP port scan + service version + OS detection: nmap -sS -sV -O -p- -T4 192.168.56.101 -oN outputs/nmap_full_101.txt
• Quick vulnerability script scan: nmap --script vuln -sV 192.168.56.101 -oN outputs/nmap_vuln_101.txt
• SMB enumeration: enum4linux -a 192.168.56.101 | tee outputs/enum4linux_101.txt
• HTTP header (banner) grab: nc -v 192.168.56.101 80 then GET / HTTP/1.1\r\nHost: 192.168.56.101\r\n\r\n
• Download a file with wget: wget https://192.168.56.101/index.html -O outputs/index_101.html
• Start Metasploit and search exploits: msfconsole search name_of_service
• Use sqlmap (lab-only): sqlmap -u "https://192.168.56.101/vuln.php?id=1" --batch --dump
• Save terminal activity (script): script outputs/session_kali_YYYYMMDD.txt -> run your commands exit to save.

Students exploring system-level configurations may also benefit from concepts discussed in Operating System coursework.

How to capture reproducible evidence

• Save all command outputs to files (>, tee, or script).
• Use clear file naming: groupX_nmap_full_target1.txt, groupX_nessus_highs.pdf, groupX_exploit_screenshot1.png.
• Screenshots: include terminal + command visible. Filename format: G1_exploit_STEP1.png
• Nessus: export HTML/PDF for the report.
• Include timestamps and the VM IPs used in the evidence appendix.

Rules of Engagement (ROE) - required for Project Demonstration & Presentation

Task Description

Using the penetration testing lab environment developed in Part A, each group is required to conduct a live demonstration of a controlled cybersecurity assessment within the isolated virtual lab environment. The demonstration will assess the student's ability to perform reconnaissance, vulnerability assessment, controlled exploitation, remediation, and professional presentation of findings while following ethical and safe testing practices.

Demonstration Requirements

Each group should demonstrate the setup of the attacker and target virtual machines, including connectivity verification and reconnaissance activities using appropriate tools such as Nmap, Wireshark, Netcat, or similar approved tools. Students are also expected to perform vulnerability scanning, identify key vulnerabilities, and explain relevant CVEs and their potential impact.

The demonstration must include at least one web-based exploitation example and one system or network exploitation example within the approved lab environment. Students should clearly explain the methodology, tools used, and exploitation outcomes. Remediation strategies and re-testing after applying fixes should also be demonstrated where possible.

Evidence such as screenshots, scan outputs, command results, or logs should be presented during the demonstration. All testing activities must strictly follow the Rules of Engagement (RoE) and remain limited to the approved virtual lab systems.