Member Avatar for JA

I am looking for project ideas for my yearly software project , which has duration of 6 months .

I am very much interested in developing network/security related tool .

Any kind of suggestion will be highly apreciated .

Thank in advance

Edited by JA because: textual improvement
  • 4 Contributors
  • 3 Replies
  • 274 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by ss125

Dani AI

Generated

— a six‑month networking/security project succeeds when it targets one clear problem, delivers a working prototype, and has repeatable evaluation. is right: narrow the scope early. ’ suggestion to research is useful — pick recent papers or tools as inspiration. ’s firewall idea can be expanded into many practical, measurable projects rather than “build a firewall” as a broad goal.

Possible project ideas (each should end with a demoable deliverable and test plan):

  • Application‑aware firewall: policy language, rule engine, packet capture integration, latency/throughput benchmarks, and a small GUI for rule management.
  • Flow‑based anomaly detector: ingest NetFlow/sFlow, extract features, train a model, test with injected anomalies and a dashboard showing alerts.
  • TLS/certificate inventory and hardening tool: network scanner, heuristic checks for weak configs, scheduled reporting and remediation suggestions.
  • IoT discovery + vulnerability auditor: device fingerprinting (mDNS/SSDP), default‑credential checks, basic firmware/version inventory, and PDF reports.
  • SDN security app for Mininet/Open vSwitch: detect/mitigate volumetric floods or suspicious microflows via controller logic and automated test scripts.
  • Pentest orchestration and prioritized reporting: wrap scanners (nmap/nuclei/OpenVAS), normalize findings, create prioritized remediation list and SLA tracking.

Six‑month roadmap (example): months 1–2 requirements, lit review, lab setup; months 3–4 core implementation and unit tests; month 5 integration, performance testing and false‑positive tuning; month 6 evaluation, documentation, writeup and demo script. Success criteria = working MVP, reproducible testbed, quantitative metrics (detection/false‑positive rates, latency, coverage).

Practical tips and cautions: use version control, automated testbed (VMs or containers), keep data labeling realistic, avoid scanning live public networks without permission, and prioritize a small, polished MVP you can demo.

Recommended Answers

All 3 Replies

Member Avatar for rubberman

School assignment - we don't do that. What do you think would be appropriate? In the networking/security domain there are a plethora of issues to deal with. Pick one... :-)

Member Avatar for cmps

i am sure u can find some cool ideas on google ...

Member Avatar for ss125

If your carrier is on networking, then try to moniter protocol with application that can be used to allow/block the functionalities of that particular protocol. In simple, Just develop a firewall on your own.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.