Back to portfolioPROJECT CASE STUDY / 02
AI-ASSISTED NETWORK SECURITY

ENGINEERING PROJECT / 02

NetSec Agent.

CASE STUDY
2026

A Python-based assistant for authorized network assessments, combining Nmap discovery with an interface that helps explain scan results.

PROJECTNetSec Agent
TYPEAI-ASSISTED NETWORK SECURITY
TECHNOLOGIES6 core tools
PythonNmapStreamlitLangGraphMCPGroq

01 / CONTEXT

THE WHY

The challenge

Raw scan output can be difficult to interpret, especially when learning network security. The goal was to build a guided workflow that makes the scan scope explicit and turns technical findings into explanations without hiding the underlying evidence.

02 / SYSTEM DESIGN

THE STRUCTURE

How the pieces fit together

A high-level view of the documented workflow and component boundaries.

01

Scoped target input

Accepts private IPv4 targets within a bounded assessment scope.

02

Nmap discovery

Performs host discovery, TCP port scanning and service-version detection.

03

Structured findings

Makes discovered hosts, ports and services available to the interface.

04

AI-assisted explanation

Uses the agent workflow to explain observations and estimated risk while preserving scan evidence.

05

Streamlit interface

Presents the assessment flow and results for analyst review.

03 / ENGINEERING LOG

THE BUILD SEQUENCE

How the work took shape

A transparent sequence of engineering milestones. Status labels describe documented work—not a live completion percentage.

  1. 01
    01 · SCOPEImplemented

    Constrain the assessment target

    Designed the workflow around approved private IPv4 targets, with a documented maximum scope of 256 addresses.

  2. 02
    02 · DISCOVERYImplemented

    Connect Nmap reconnaissance

    Added host discovery, TCP port scanning and service-version detection as the source of technical observations.

  3. 03
    03 · PRESENTATIONImplemented

    Structure findings for review

    Used a Streamlit interface to present discovered hosts, ports and services while keeping scan evidence available.

  4. 04
    04 · EXPLANATIONImplemented

    Add AI-assisted interpretation

    Connected the agent workflow to explain observations and potential risk without treating generated explanations as a replacement for scan evidence.

  5. 05
    05 · VALIDATIONDocumented

    Document test coverage and safe use

    The repository documents pytest and Ruff checks. Use only against systems and networks you own or are explicitly authorized to assess.

04 / DESIGN JUDGMENT

TRADE-OFFS & REASONS

Decisions behind the design

The engineering choices that shape the system—and the reason each boundary exists.

01

Keep Nmap as the source of observations

The scan output remains the technical evidence. AI explanations can help interpret it, but they must not silently replace or rewrite discovered ports and services.

02

Bound the target scope to private IPv4

An explicit private-address boundary and maximum range make the authorized assessment use case clearer and reduce accidental scope expansion.

03

Use a guided Streamlit workflow

A compact interface makes target selection, scan execution and review visible instead of hiding the process behind an opaque agent.

05 / NEXT INVESTIGATION

THE NEXT USEFUL TEST

What I would test next

Add a downloadable assessment report that preserves the raw Nmap findings beside the AI explanation, records the exact target scope and scan options, and clearly labels any generated risk interpretation as advisory.

06 / IMPLEMENTATION

THE HOW

Engineering approach

The work is broken into practical building blocks, from initial design through to validation.

  1. 01

    Accepts user-defined targets within a private IPv4 scope and applies bounded scan limits.

  2. 02

    Uses Nmap for host discovery and TCP port and service detection.

  3. 03

    Presents scan results through a Streamlit interface.

  4. 04

    Uses an AI-assisted workflow to explain discovered services and potential risks while keeping the scan output available for review.

07 / VERIFICATION

THE CHECKS

Validation & evidence

Specific checks documented for this project. Results are scoped to the recorded lab or test run.

Target scopeBounded

The documented workflow limits discovery to approved private IPv4 ranges of up to 256 addresses.

Scan engineNmap

Host discovery, TCP port scanning and service-version detection provide the underlying observations.

Test workflowPytest

The repository documents pytest and Ruff checks as part of its development workflow.

08 / RESULTS

THE VALUE

What this project demonstrates

01

A practical workflow linking network discovery, structured scan results and natural-language explanations.

02

A clear interface for reviewing hosts, ports and services.

03

A project that explores how AI can assist analysis without replacing the original technical evidence.

09 / EVIDENCE

THE BUILD

Project in practice

Original project captures and walkthrough media. Each item is labelled to explain what it demonstrates.

The video is an existing repository-hosted walkthrough of the application. It is a recorded demonstration, not a live hosted instance; use the README to reproduce the local setup.

Recorded NetSec Agent walkthrough — hosted in the project repository.

10 / ENGINEERING NOTES

TRANSPARENCY

Scope, assumptions & limitations

Clear boundaries matter. These notes describe what the current project does—and what it does not claim to do.

  • Use only on networks and systems you own or are explicitly authorized to assess.
  • The tool is designed for private IPv4 targets with a maximum scope of 256 addresses.
  • Risk scores and AI explanations are advisory and should be checked against the underlying scan evidence.
  • TShark packet analysis and Wazuh integration are not implemented.
  • It is a learning and assessment tool, not a replacement for a professional vulnerability-management platform.