What it is
netsa does not sit in your traffic path; it reads the logs of your WAF, nginx, firewalls, hosts and DNS to work out which attacks were blocked, which reached the backend, which actually succeeded, and what the attacker did next. A single binary or one container with maps and geolocation built in, so teams without a dedicated SOC can install it and understand what they see.
Screenshots








The screenshots show demo data from netsa's built-in simulator; IPs and sites are simulated.
Compared with common in-house setups
| Log platform + hand-written rules | Host security platform (multi-component) | netsa | |
|---|---|---|---|
| Deployment | Search cluster + collectors + dashboards, many components to run | Console + index + dashboards + an agent on every host | A single binary / one container |
| Log onboarding | Write a parser for every format | Mainly host logs | 50+ formats detected automatically |
| Alert quality | Every rule hit is an alert | Every rule hit is an alert | Evidence review rules out "false successes" |
| Chinese software | Write it yourself | Write it yourself | 261 signatures for Chinese OA / middleware |
| Gets more accurate | People maintain allow lists | People maintain allow lists | Self-learning and self-correction loop |
| Offline on private networks | Depends on the components | Depends on the components | Fully offline |
Use cases
SMEs and public organizations
No dedicated SOC; you need a posture wall and a response list you can understand right after installing
MLPS and compliance
Raw log retention, tamper-proof hash chains, audit, weekly and monthly reports and an MLPS 2.0 self-check
Data centers, cloud workloads and public websites
Find the attacks that really reached a service and really succeeded among lots of background scanning
Security and blue teams
Attack chains, ATT&CK mapping, same-source correlation and decoys for fast triage and tracing
Deployment
Runs with Docker / Docker Compose (amd64, arm64), as a plain binary, or from an offline image bundle for private networks. Try the demo with its built-in attack log simulator in one command:
git clone https://github.com/sreyun/netsa.git && cd netsa
docker compose -f docker-compose.demo.yml up -d --build
# open http://localhost:8080
For production run docker compose pull && docker compose up -d; by default it reads /var/log/nginx and /var/log on the host, and network devices send syslog to port 5514 (UDP / TCP). You can also analyze existing logs without deploying: netsa analyze access.log -o report.json.
FAQ
Do my logs leave my network? No. All analysis happens locally; online tracing and AI triage are optional, it runs fully offline without them, and data can be masked before it is sent to an external model.
How does it relate to a WAF? They complement each other. netsa reads WAF, nginx and firewall logs to answer whether an attack succeeded and what the attacker did next.
Open-source license
netsa is released under the Apache License 2.0 and can be used commercially, modified and redistributed freely. For commercial services such as rule and intelligence subscriptions, deployment and MLPS assessment support, see pricing.