Lesson 9 of 9

Final Assessment

The final assessment evaluates your ability to analyze network traffic, identify security weaknesses, and recommend appropriate defenses. You will work through a series of practical scenarios that test your knowledge of protocols, packet analysis, attack techniques, and defensive controls. This assessment mirrors the type of analysis performed by network security analysts in the field.

Learning Objectives — Deep Dive

Each objective below is broken down into plain English so you know exactly what you are learning, why it matters, and what you will be able to do when you are done. Mark each one complete as you work through the lesson.

0/4
In plain English

In simple terms: Apply the complete network security methodology independently. This means building enough understanding that you can apply this concept in a real scenario — not just answer a quiz question about it, but actually use it when it matters. Focus on the "why" behind the concept, not just the "what."

Why this matters

Every attack and every defense happens over a network. Understanding how data actually travels between computers gives you the mental model to spot anomalies, intercept traffic, and understand why certain attacks work the way they do.

Real-world analogy

Think of it like learning to drive. You do not need to understand how the engine works to drive safely, but knowing the basics helps you diagnose problems and avoid mistakes that could cause accidents. The same principle applies here — foundational knowledge prevents costly errors.

What you will be able to do

Apply this skill in a real lab environment, explain it clearly to a colleague or client, and use it as a building block for the more advanced techniques that come later in this course.

Beginner tip

Do not try to memorize everything at once. Read through the material once to get the big picture, then go back and work through the lab. The hands-on practice is what makes the concepts stick — passive reading alone will not get you there.

Final Assessment · Objective 1 of 4

VIDEO
Loading video…
1

Network discovery

Run 'sudo nmap -sn 192.168.x.0/24' (replace with your lab subnet) to perform a ping sweep and discover all live hosts on the network. The -sn flag disables port scanning and only checks host availability, making the scan fast and quiet. Document every IP address and hostname returned — this is your target list for the rest of the assessment. A common pitfall is scanning the wrong subnet; run 'ip addr' first to confirm your Kali machine's IP and subnet before launching the discovery scan.

2

Full service enumeration

Run 'sudo nmap -sV -sC -O -p- <target-ip>' against each discovered host to perform a comprehensive service and OS detection scan. The -sV flag detects service versions, -sC runs default NSE scripts, -O attempts OS fingerprinting, and -p- scans all 65,535 ports instead of just the top 1,000. This scan will take several minutes per host — be patient and let it complete fully before analyzing results. Save the output to a file with '-oN scan-results.txt' so you can reference it throughout the rest of the assessment.

3

Protocol analysis

Start a Wireshark capture on your Kali interface and generate traffic between Kali and Metasploitable by running service-specific commands such as 'ftp <target>', 'telnet <target>', and browsing to 'http://<target>'. Identify which protocols are transmitting data in cleartext versus encrypted — FTP, Telnet, and HTTP are all plaintext and will show readable credentials and content in Wireshark. Document each cleartext protocol as a finding, noting the port, service, and what data is exposed. This protocol analysis step bridges the gap between port scanning and vulnerability assessment.

4

Vulnerability assessment

Run 'sudo nmap --script vuln <target-ip>' to execute Nmap's vulnerability detection scripts against the target. These scripts check for known CVEs, misconfigurations, and common weaknesses such as anonymous FTP access and outdated SSL/TLS configurations. For a more thorough scan, install and run OpenVAS (now called Greenbone Vulnerability Manager) which maintains a database of over 50,000 vulnerability tests. Record every finding with its CVE number, CVSS score, and the evidence from the scan output — this forms the technical basis of your report.

5

Write the report

Structure your report with an executive summary (one page, non-technical, suitable for management), a findings section (one entry per vulnerability with severity, evidence, and remediation), and an appendix with raw scan output. Rate each finding using the CVSS scoring system: Critical (9.0–10.0), High (7.0–8.9), Medium (4.0–6.9), Low (0.1–3.9). The executive summary should state the overall risk posture in plain language without technical jargon. A well-written report is what separates a professional penetration tester from a script kiddie — the ability to communicate findings clearly is as important as the technical skill to find them.