Driverless enforcement
Bans via the Windows Firewall in user mode (COM INetFwPolicy2): reliable, reversible, never touching the kernel network stack.
WinLogGuard is a native Windows IDS/IPS: it reads Event Viewer and the logs of RDP, OpenSSH, SQL Server, IIS, nginx and Apache — and when a threshold trips, it bans the attacker's IP right in the Windows Firewall. No external agents, no drivers.
How it works
From event to ban, without ever reading a log by hand.
Push subscriptions on Event Viewer (with persisted bookmarks) and log file tailers: no missed events, no duplicates.
Threshold rules of N events in T seconds per IP: RDP brute force, failed SQL logins, failed SSH logins, custom regex patterns.
IP banned with a named Windows Firewall rule, progressive bantime for repeat offenders and automatic reconcile at boot.
Features
A complete IDS/IPS engine with the ergonomics of a modern WebUI: every feature is manageable from the interface, not just from YAML.
Bans via the Windows Firewall in user mode (COM INetFwPolicy2): reliable, reversible, never touching the kernel network stack.
Unified sources: Event Viewer channels with XPath/event IDs and plain-text files of any format via named-group regex.
A “who attacks whom” view: usernames extracted from 4625 events and presets, with top targets always on the dashboard.
Block entire countries with dedicated rules; per-country summary on the dashboard and country filters in rules.
Repeat offenders stay banned longer: duration grows with every reoffense, expirations handled automatically.
Bans and cursors in SQLite: after a reboot (or a crash) everything is reapplied with reconcile against the actual rules.
Live dashboard with SSE: events, rules, sources, whitelist, notifications and configuration — nothing to install.
Admin and viewer users with sessions, PBKDF2 passwords and brute-force lockout on the WebUI itself.
Email, webhook and Telegram for events; daily or weekly digest with top offenders and most targeted accounts.
Prometheus /metrics endpoint and syslog or Event Log output: your bans land in the monitoring you already have.
Test rules in observe-only mode before enforcing: see who would have been banned without blocking anything.
Beyond the local firewall: bans as Cloudflare IP Access Rules, protecting services exposed behind the CDN too.
Comparison
The well-known alternatives are born on Linux or drag complex stacks along. WinLogGuard is built for Windows and for the people who run it.
| Feature | WinLogGuard | fail2ban | CrowdSec | EvlWatcher |
|---|---|---|---|---|
| Runs natively on Windows | ✓ | ✗ | ◐ | ✓ |
| No external agent or console | ✓ | ✓ | ✗ | ✓ |
| Reads Event Viewer natively | ✓ | ✗ | ◐ | ✓ |
| Integrated management WebUI | ✓ | ✗ | ◐ | ✗ |
| Targeted accounts & GeoIP dashboard | ✓ | ✗ | ◐ | ✗ |
| Single self-contained executable | ✓ | ✗ | ✗ | ✗ |
| Bans persisted and reapplied at boot | ✓ | ✓ | ✓ | ◐ |
| Built-in scheduled email reports | ✓ | ✗ | ◐ | ✗ |
◐ = possible but with extra components, manual configuration or non-native features. EvlWatcher: development stalled, RDP-only coverage.
Under the hood
Pricing
Start free with Community: full engine, GeoIP included, no credit card required. Pro is an annual per-server subscription with volume discounts.
Free
€0forever
For homelabs, testing and your first server. Full engine, no credit card required.
Recommended
€149/server/year · volume discounts
For companies with several servers: visibility, reporting and role control.
For MSPs
€99/managed server/year · from 10 servers
For those who run Windows Server on behalf of clients: one console, many clients, your brand.
* Pro volume discounts: 2–4 servers −15% · 5–9 −25% · 10–24 −35%. MSP plan from 10 managed servers, white-label +€499/year. Community updates remain free.
FAQ
Quick answers to the questions sysadmins actually ask us.
No. It's an access-focused IDS/IPS: it reads access logs (Event Viewer, RDP, SSH, SQL, web servers) and blocks IPs that exceed failed-attempt thresholds, the way fail2ban does on Linux.
No. Enforcement happens in user mode through the Windows Firewall APIs (COM INetFwPolicy2). No drivers, no third-party services: one self-contained executable.
Event Viewer (RDP 4625/140, OpenSSH, SQL Server 18456, WinRM, PowerShell, Windows Defender and custom channels via XPath) and plain-text log files (nginx, Apache, IIS, sshd and custom formats via named-group regex).
Yes: 4625 events require 'Audit Logon Failures' enabled. WinLogGuard checks the policy at startup, independent of the OS language, and warns you with instructions to enable it.
Active bans are persisted in SQLite and reapplied at startup, with a reconcile that syncs the expected state with the firewall rules actually present. No vulnerability window at boot.
Yes, with the GeoIP module: you can attach a dedicated rule to a country or use it as a filter in existing rules. The dashboard shows the per-country distribution of events.
The whitelist accepts IPs and CIDRs (e.g. 10.0.0.0/8 or management addresses) that are never banned. In dry-run mode you can watch for days what would have been blocked before taking action.
Minimal: a lightweight service, no runtime dependencies, push-based event reads and batched bans. A footprint of a few MB and negligible CPU even under attack.
fail2ban doesn't run on Windows; CrowdSec is great but requires an agent, a console and separate bouncers. WinLogGuard does it all in one executable: log reading, decision, firewall ban, WebUI and reporting — Windows-first from the first commit.
Install WinLogGuard, open the WebUI, watch attackers drop. Your server won't even remember they came.