Cybersecurity Workbook For 11th Graders

Why This Matters

Choosing a cybersecurity career is like picking a role on a team defending a city during a storm. Each person has a different job - some build barricades, some scout the horizon, and some analyze what caused damage after the storm. Understanding these roles now helps you pick classes, clubs, internships, and projects that match your strengths and interests.

This chapter introduces common cybersecurity roles, shows what a typical day looks like, and gives you hands-on practice mapping your skills to roles. By the end, you’ll have a clear, measurable way to explore paths such as security analyst, penetration tester, incident responder, and security engineer - and a short exercise to try a role-specific task using a named tool like Wireshark or Nmap.

Skill Builder

Activity: Match a role to a daily task and try a tiny real-world simulation.

Materials: computer with internet, Wireshark (free) installed, a text editor.

Time: 45 minutes.

Steps:

1. Pick one role from this list: Security Analyst, Penetration Tester (Pentester), Incident Responder, or Security Engineer.

2. Read the 3-4 bullet “daily tasks” for that role below and pick one task to simulate.

• Security Analyst: monitor network logs, triage alerts, write a short incident note.
• Penetration Tester: scan a network for open ports (on your own lab/IP), document findings.
• Incident Responder: collect and summarize evidence from a suspicious traffic capture.
• Security Engineer: design a firewall rule and explain why it reduces risk.

3. For a traffic-based task, open Wireshark and capture 60 seconds of traffic on your home network (only on devices you own). Save the capture file (.pcap).

4. For a pentesting task, run Nmap against an authorized local VM or lab IP (example: 192.168.56.101). Use command: nmap -sS -Pn 192.168.56.101

5. Create a one-page report (300-400 words) in your text editor: include role name, task performed, the tool used (Wireshark or Nmap), top 3 findings, and one recommendation.

6. Submit or save the file as role_task_[yourname].txt and compare it to the worked example below.

Worked example:

> Role: Penetration Tester

> Task: Port scan of lab VM 192.168.56.101 using Nmap

> Command: nmap -sS -Pn 192.168.56.101

> Findings: Open ports: 22 (SSH), 80 (HTTP), 3306 (MySQL); SSH shows OpenSSH 7.4; HTTP banner reveals Apache 2.4.18.

> Recommendation: Restrict SSH to admin IPs via firewall; update Apache to latest security patch; move MySQL behind internal-only interface.

What good looks like:

• The report states role and exact command or tool used.
• Top 3 findings are specific (port numbers, service names, or packet summaries).
• Recommendation is actionable (one sentence that could be implemented in a lab).

Going Deeper

Explore variations and advanced paths you can take after this exercise.

• Penetration Tester - Advanced: use Metasploit to attempt an exploit in a controlled lab (requires a deliberately vulnerable VM like Metasploitable2). This adds exploitation steps and post-exploit notes.
• Incident Responder - Advanced: timeline analysis using timestamps from PCAP and system logs to build a 10-minute incident timeline. Add at least 5 timestamped events.
• Security Engineer - Advanced: rule testing by applying a firewall rule on a home router or virtual firewall (pfSense) and documenting latency impact (measure ping before/after).

How to adapt:

• For a school club with limited access, swap live scans for provided sample PCAP files (example: sample.pcap from Wireshark’s sample captures page).
• If you don’t want to install tools, use online sandboxes like TryHackMe (free rooms) to simulate pentest tasks and download lab reports.

Self-Check

1. Which role did I choose, and why does it match my current skills?

______________

______________

______________

2. What exact tool and command (or file name) did I use during the task?

______________

______________

______________

3. List the top three findings from your report with at least one measurable detail (port number, timestamp, version).

______________

______________

______________

4. What is one specific next step you will take to improve (for example: take a TryHackMe room, learn a command, or set up a lab)? Include a deadline (date).

______________

______________

______________

...