No kernel driverSingle executableNative Windows Firewall

Brute force protection for Windows Server, in real time.

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.

WinLogGuard in numbers

0ready-made source presets
0kernel drivers required
0single self-contained executable
0protection with persistent bans

How it works

Three steps, zero noise

From event to ban, without ever reading a log by hand.

  1. Watches

    Push subscriptions on Event Viewer (with persisted bookmarks) and log file tailers: no missed events, no duplicates.

  2. Detects

    Threshold rules of N events in T seconds per IP: RDP brute force, failed SQL logins, failed SSH logins, custom regex patterns.

  3. Blocks

    IP banned with a named Windows Firewall rule, progressive bantime for repeat offenders and automatic reconcile at boot.

Features

Everything a sysadmin expects

A complete IDS/IPS engine with the ergonomics of a modern WebUI: every feature is manageable from the interface, not just from YAML.

Driverless enforcement

Bans via the Windows Firewall in user mode (COM INetFwPolicy2): reliable, reversible, never touching the kernel network stack.

Event Viewer + log files

Unified sources: Event Viewer channels with XPath/event IDs and plain-text files of any format via named-group regex.

Targeted accounts

A “who attacks whom” view: usernames extracted from 4625 events and presets, with top targets always on the dashboard.

GeoIP and country bans

Block entire countries with dedicated rules; per-country summary on the dashboard and country filters in rules.

Progressive bantime

Repeat offenders stay banned longer: duration grows with every reoffense, expirations handled automatically.

Persistent bans

Bans and cursors in SQLite: after a reboot (or a crash) everything is reapplied with reconcile against the actual rules.

Embedded WebUI

Live dashboard with SSE: events, rules, sources, whitelist, notifications and configuration — nothing to install.

Multi-user with roles

Admin and viewer users with sessions, PBKDF2 passwords and brute-force lockout on the WebUI itself.

Notifications & reports

Email, webhook and Telegram for events; daily or weekly digest with top offenders and most targeted accounts.

SIEM-ready

Prometheus /metrics endpoint and syslog or Event Log output: your bans land in the monitoring you already have.

Dry-run / IDS mode

Test rules in observe-only mode before enforcing: see who would have been banned without blocking anything.

Cloudflare backend

Beyond the local firewall: bans as Cloudflare IP Access Rules, protecting services exposed behind the CDN too.

Comparison

Why fail2ban (or CrowdSec) is not enough

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.

FeatureWinLogGuardfail2banCrowdSecEvlWatcher
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

Built for servers, not for demos

  • .NET 10self-contained LTS runtime, single file
  • SQLitebans, cursors and users without a DB server
  • REST + SSEbuilt-in APIs with streamed events
  • YAMLdeclarative, validated configuration
  • CLI--validate, --once, console management
  • Windows Serviceauto-start, recovery, LocalSystem

Pricing

Choose how you protect your servers

Start free with Community: full engine, GeoIP included, no credit card required. Pro is an annual per-server subscription with volume discounts.

Free

Community

€0forever

For homelabs, testing and your first server. Full engine, no credit card required.

  • 1 server with the full engine and all presets
  • Bans via Windows Firewall + GeoIP included
  • WebUI with admin user and live dashboard
  • Persistent bans in SQLite
  • Community support
Download

Recommended

Pro

€149/server/year · volume discounts

For companies with several servers: visibility, reporting and role control.

  • Everything in Community, unlimited servers
  • Daily/weekly email reports
  • Multi-user admin/viewer roles
  • SIEM integrations: Prometheus, syslog
  • Webhook and Telegram notifications
Request Pro

For MSPs

MSP

€99/managed server/year · from 10 servers

For those who run Windows Server on behalf of clients: one console, many clients, your brand.

  • Central multi-server console (coming soon)
  • White-label: your logo, name and notifications (coming soon)
  • Per-client summary reports
  • Pooled, reassignable Pro licenses (coming soon)
  • Dedicated support
Contact us

* 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

Frequently asked questions

Quick answers to the questions sysadmins actually ask us.

Is WinLogGuard an antivirus?

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.

Does it need a kernel driver or an external agent?

No. Enforcement happens in user mode through the Windows Firewall APIs (COM INetFwPolicy2). No drivers, no third-party services: one self-contained executable.

Which log sources does it support?

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).

Is an audit policy required for the RDP preset?

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.

What happens if the server reboots?

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.

Can I block an entire country?

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.

What if it bans an important IP (VPN, office)?

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.

What is the resource impact?

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.

How does it differ from fail2ban or CrowdSec?

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.

Your next brute force ends in a ban.

Install WinLogGuard, open the WebUI, watch attackers drop. Your server won't even remember they came.