Network SecurityNetwork SecurityNetwork Security

Examples of everyday tasks

• Design segments that separate everyday users, servers, and administrators.
• Write and review firewall rules.
• Investigate suspicious traffic in network logs or packet captures (recordings of network traffic).
• Troubleshoot connection problems without opening unnecessary access.
• Keep network diagrams and the reason for each allowed connection up to date.

Related job titles

• Network security analyst
• Network security engineer

These are career areas to explore, not a checklist. Some of these job titles usually require experience, and completing a starter project does not by itself make someone ready for them.

Starter project

Build and Test a Segmented Practice Network

Create separate user and administrator areas in a small virtual or simulated network. Define allowed connections and test the rules.

What you’ll use

• Virtual machines on your own computer, or a free network simulator
• A firewall you can configure, such as the one built into a Linux virtual machine or a free open-source firewall such as OPNsense
• Simple tools for testing connections, such as ping and a port-checking utility

Resources to start with

• OPNsense (opens in a new tab)

  A free, open-source firewall and routing platform you can run in a virtual machine.

• Wireshark (opens in a new tab)

  A free tool for capturing and inspecting network traffic while you test your rules.

More projects for this path

Each one comes with the framework to follow, five name ideas and a walkthrough for publishing it on GitHub.

• Segmented Lab Network

  Build two network zones, write default-deny rules and test what really gets blocked.

• Firewall Rule Review

  Audit a messy rule set, find what is redundant or too broad, and rewrite it.

Project walkthrough

1. Sketch two zones, users and administrators, and decide which devices belong in each.
2. Write the connection policy in plain language, for example: administrator devices can reach user devices for support, but user devices cannot reach the administrator zone.
3. Build the network and apply firewall rules that block everything except the allowed connections.
4. Test every rule from both sides, including connections that should fail.
5. Record each test: source, destination, port, expected result, and actual result.
6. Fix any rule that behaved differently than you expected, then test again.

What to publish

• A network diagram
• An explanation of each rule
• Actual connection-test results, including tests that were expected to fail

Optional extension

Demonstrate how the boundaries limit movement from a simulated compromised device.

Example résumé bullet

Numbers are what make a bullet worth reading, so count them while you work: how much data you searched, how many findings you fixed, how many tests you added. Every figure should be one a reader can find in your report. Write the line after the work is done, and leave out impact or experience you cannot show.

Numbers to record while you work

Project name | tools, datasets and frameworks | link

Give the project a name of its own: “Bulkhead” is an example, not a label to copy. List the tools, datasets and frameworks you actually used, since several relevant ones show more than a single tool does. Hyperlink the last part to your published repository or report.

Turn your project into a portfolio piece

A project becomes easier to evaluate when someone can understand what you did, inspect the evidence, and follow your reasoning.

Create a short report, GitHub README, or portfolio page. A clear two-to-four-page report is a useful starting point, not a strict requirement.

Include:

1. Goal: What question or problem did you investigate?
2. Environment: What tools, practice data, or systems did you use?
3. Your work: What did you personally do, and why?
4. Evidence: Include useful screenshots, queries, code, or test results.
5. Findings: What did you discover? What remains uncertain?
6. Fix or recommendation: What should change, and did you test it?
7. Sources and limitations: Credit datasets and guides. Clearly identify simulated work.

Use sample or redacted information in the public version.

Publish the report somewhere accessible without requesting permission, and check the link before putting it on a résumé.

Put numbers in it

Count as you work, and put the figures in the report: records searched, findings confirmed, tests added, checks failing before and after. A reviewer can check every one of them against your evidence, which is exactly why they are worth including. Leave out business impact you cannot show.

Name it, then show your tools

A résumé line works best in three parts: your project’s own name, the tools and frameworks you used, and a link to the work. “Role-Based Access Lab” reads like a class exercise. A name plus a tool list tells a reviewer what you can actually work with, and every tool, dataset or framework you list honestly is another thing an interviewer can ask you about.

Project name | tools, datasets and frameworks | link

• Role-Based Access Lab→Turnstile | Keycloak, RBAC design, NIST SP 800-63, Docker | GitHub
• Login Hunt→Beacon | Python, pandas, Sigma, MITRE ATT&CK | GitHub
• Cloud Project→Bedrock | Terraform, Checkov, AWS IAM, CIS Benchmarks | GitHub

Why link a report?

Your résumé gives a short description of the project. The linked report lets a reviewer inspect your work and gives you concrete evidence and decisions to discuss during an interview.

Not every recruiter will open it, but it makes your work available for review.

Hyperlink the last part to the published work, so “GitHub” or “Project Report” opens your repository or report. Check the link before you send the résumé.

# Project title

> Practice project. Describe the simulated scenario, practice data, or lab used.

## Goal
What question or problem did you investigate?

## Environment
What tools, practice data, or systems did you use? Link datasets and guides.

## My work
What did you personally do, and why?

## Evidence
Screenshots, queries, code, or test results. Use sample or redacted information only.

## Findings
What did you discover?
The numbers behind it (records searched, findings confirmed, tests added).
What remains uncertain?

## Fix or recommendation
What should change, and did you test it?

## Sources and limitations
- Datasets and guides used:
- What was simulated:
- Limitations:

Related paths to explore

• Cloud Security

  Cloud security analysts and engineers make sure services running on platforms such as AWS, Microsoft Azure, and Google Cloud are configured safely, monitored, and kept that way.

• Offensive Security

  Penetration testers and red team operators attack systems with written permission to find weaknesses before real attackers do, then explain how to fix them.

• SOC Analysis

  Security operations center (SOC) analysts review an organization’s security alerts, decide which ones point to real problems, and pass confirmed issues to the people who can act on them.