Project ideas for final-year networking and security students
In short: A strong final-year project answers a clear question, uses a lab you control, and is evaluated with real measurements. This note lists ideas across networking, security, cloud and IoT, and shows how to turn an idea into a proposal your supervisor will approve.
Goal and requirements
The goal of a final-year (honours) project is to show you can investigate a problem independently, not just build something. Markers usually look for a clear aim and objectives, a review of existing work, a sound design, an implementation, a critical evaluation and reflection. Practical requirements:
- A question you can answer in the time available, usually one academic year alongside other modules.
- Equipment you control: virtual labs, simulators, your own hardware or free cloud credits with a budget.
- Ethical approval if you involve people (surveys, interviews) or any real data. No testing of systems you do not own.
- A link to the jobs you want, so the project doubles as portfolio evidence.
Ideas and how to scope them
| Idea | Build | Evaluate by |
|---|---|---|
| Zero trust segmentation for a small business | Lab with a next-generation firewall, identity-based rules and VLANs | Lateral movement tests before and after; rule count; user impact |
| Comparing open-source IDS engines | Suricata and Snort on the same traffic replays | Detection rate, false positives, CPU at set traffic rates |
| Automated compliance checking | Python or Ansible tool that audits lab devices against a hardening baseline | Time saved versus manual checks; accuracy on seeded faults |
| Detecting cloud misconfigurations | IaC scanning in a CI pipeline on deliberately flawed templates | Findings caught, false positives, pipeline time |
| Securing an MQTT-based IoT system | Sensors, broker with TLS and ACLs, VLAN isolation | Latency and battery cost of TLS; attack tests in the lab |
| Post-quantum TLS performance | Test server and client using hybrid ML-KEM key exchange where supported | Handshake time and message size versus classical TLS |
| Enterprise Wi-Fi with 802.1X | RADIUS server, WPA3-Enterprise, certificate-based authentication | Onboarding time, failure cases, policy enforcement tests |
Notice the pattern: each idea has something to build and something to measure. Avoid titles like "a study of firewalls", which have neither.
Build plan
- Shortlist three ideas, and for each write an aim, three to five objectives and a one-paragraph method.
- Check feasibility: hardware, software licences, images, cost, and time for each objective.
- Discuss with your supervisor and choose one. Agree the scope in writing.
- Read widely: standards (for example NIST SP 800-207 for zero trust), recent papers and vendor-neutral sources. Keep references as you go.
- Build in stages and keep a weekly log with screenshots and configs in Git.
- Plan the evaluation before building: what you will measure, how often, and what would count as success.
- Leave at least a month for evaluation and writing.
Deliverables and how to present it
- The dissertation or report, with design diagrams, results tables or charts, and honest discussion of limitations.
- A demonstration or viva, often with a short live demo; record a backup video in case the lab misbehaves.
- A cleaned public repository and a short write-up for your portfolio.
On a CV: "Final-year project: designed and evaluated a zero trust segmentation model for an SME in a virtual lab; reduced reachable hosts from a compromised client from 40 to 3." One clear result with a number is worth more than a paragraph of description. Common mistakes that cost marks: too wide a scope, no measurable evaluation, a weak literature review, and leaving the write-up to the end.
Practice
What turns a topic into a good final-year project?
Why plan the evaluation before building?
When do you need ethical approval?
Key takeaways
- Pick a topic that links to the jobs you want.
- Every idea needs something to build and something to measure.
- Agree a tight scope and objectives with your supervisor early.
- Plan the evaluation first and keep a weekly log.
- Present one clear, measured result on your CV.
Original content written by Mohamed Fayas for FM TecHub. © 2026 FM TecHub. You're welcome to share a link to this page; please don't copy the text elsewhere without permission.