Here's a full project story for your submission:


NetProbeSec — IoT Network Security Scanner

What Inspired Us

Every day, millions of home and office networks run dozens of connected devices — smart cameras, routers, printers, IoT sensors — with zero visibility into whether they are secure. Most people never know their CCTV camera is broadcasting an open RTSP stream, or their router still uses the default password admin/admin.

We built NetProbeSec because real network security should not require a cybersecurity degree. Anyone should be able to scan their network, find vulnerabilities, and fix them — in minutes.


What We Built

NetProbeSec is a professional desktop security scanner for Windows that:

  • Discovers all devices on your network via ARP broadcast
  • Checks 12 dangerous ports including RTSP (554), Telnet (23), RDP (3389), MQTT (1883)
  • Queries live CVE data from the NIST National Vulnerability Database (NVD API v2.0)
  • Performs red team tests — default credential checks, anonymous FTP, MQTT, SMB null sessions
  • Generates a full PDF report with risk scores, CVE details, and fix recommendations
  • Isolates compromised devices instantly via Windows Firewall rules
  • Monitors live traffic for SYN floods, ARP spoofing, and port scans
  • Watch Mode — continuous background scanning with email alerts

How We Built It

Layer Technology
GUI Python + CustomTkinter (dark theme)
Network Scanning Scapy (ARP + TCP connect)
CVE Intelligence NIST NVD REST API v2.0
OS Detection Nmap + ICMP TTL fingerprinting
PDF Reports FPDF2 + Matplotlib
Database SQLite (scan history + device labels)
Installer PyInstaller + NSIS
Traffic Monitor Scapy live packet capture

The architecture is split into 14 focused modules — each responsible for one layer: scanning, intelligence, assessment, red teaming, reporting, alerting, and lockdown.


Challenges We Faced

1. False Positives in Port Scanning TCP connect scans on IoT devices produced unreliable results. We solved this with a double-verification system — a port must respond positively in 2 out of 3 attempts before being flagged.

2. NVD API Rate Limiting The NIST NVD API enforces strict rate limits. We implemented 3-retry logic with increasing timeouts (8s → 12s → 15s) and batch request spacing to stay within limits reliably.

3. CVE Scoring After Red Team Running the CVE risk engine before red team results were available meant compromised devices were under-scored. We restructured the pipeline so Module 8 always runs after red team, incorporating confirmed exploits into the final network health score.

4. Windows Firewall Integration Generating the exact netsh advfirewall commands that work reliably across Windows 10/11 versions required extensive testing. The final implementation uses precise inbound + outbound rules targeting both IP and port simultaneously.

5. Installer Integrity Bundling Npcap, UAC manifests, and a multi-module Python app into a single clean .exe required careful coordination between PyInstaller, NSIS, and Windows SDK manifest tools.


What We Learned

  • Real-world IoT devices expose far more attack surface than most users realise
  • CVE data alone is not enough — active verification (red teaming) reveals what static analysis misses
  • Building security tools responsibly means ethics consent dialogs and audit logs are not optional
  • A great security tool is useless if it is too complex — UX matters as much as the engine

Try It

net-probesec.com — Download the free installer and scan your network in under 2 minutes.

Built With

Share this project:

Updates