Follow these five steps to get SYSMarshal protecting your Windows Server within minutes.
SYSMarshal includes 17 integrated features. Click any card to jump to its full documentation.
The beating heart of SYSMarshal. A continuous monitoring loop that reads Windows event logs, identifies IP addresses that have exceeded your attack threshold, checks them against a global reputation database, and instructs Windows Firewall to block them â all automatically, with no human involvement required.
Configurable Parameters â adjust these in Settings to match your environment's risk tolerance:
| Setting | What It Controls | Default |
|---|---|---|
| Max Wrong Tries | How many times an IP must appear in event logs before it is blocked | 3 |
| Wrong Try Span | The time window (in minutes) in which attempts are counted | 99999 (all-time) |
| Minutes to Pause | Gap between each scan cycle | 5 minutes |
| Allow Private IPs | Whether local network IPs (192.168.x.x, 10.x.x.x) can be blocked | Off |
| 4th Octet Attack Count | Threshold for blocking at the subnet level | 25 |
SYSMarshal reads directly from Windows Security and Application event logs using the Windows Event Log API, monitoring specific Event IDs and extracting attacker IP addresses from those events.
Default monitored events â active from the moment you install SYSMarshal:
| Event ID | Log | Description | What It Catches |
|---|---|---|---|
4625 | Security | Account failed to log on | Brute-force attacks on Windows login and RDP |
5152 | Security | WFP blocked a packet | IP-level intrusion attempts at the firewall layer |
5157 | Security | WFP blocked a connection | Active port scanning activity |
4723 | Security | Password change attempt | Unauthorised attempts to change account passwords |
1102 | Security | Audit log cleared | Classic attacker tactic to hide evidence |
4719 | Security | Audit policy changed | Attempts to disable logging or weaken Windows auditing |
18456 | Application | SQL Server login failure | Brute-force attacks on SQL Server |
5140 | Security | Network share accessed | Unauthorised access to shared folders |
5158 | Security | Outbound connection requested | Lateral movement or command-and-control beaconing |
Before blocking any IP, SYSMarshal checks it against a central cloud reputation database shared across all SYSMarshal installations worldwide. This prevents false positives and enriches every block decision with a confidence score.
Blacklisted;<score> or TrustedIp;<score>.Abuse Confidence Score â every blocked IP is tagged with a score from 0â100, colour-coded for instant threat assessment:
Every IP action is automatically geo-located and stored. This data is used in the desktop application for interactive maps, and embedded in your email reports to provide immediate geographic context on every threat.
| Data Collected | Example |
|---|---|
| Country | United States |
| City | Los Angeles |
| Latitude / Longitude | 34.0522 / -118.2437 |
| Postal Code | 90001 |
| Google Maps URL | Direct link to the precise location |
In-app map: Clicking any row in the Baseline or Recent Activity grid renders a live Google Maps panel directly inside SYSMarshal â no browser required.
Email maps: Reports include a static Google Maps image embedded in the email body, with red markers at each blocked IP's location, auto-centred on the average geographic position of all current threats.
Two independent protection mechanisms ensure that legitimate IPs are never blocked: your Whitelist (manually defined) and Trusted IPs (automatically populated via the reputation API).
| Mechanism | How It's Populated | Format Supported |
|---|---|---|
| Whitelist | Manually via Settings â White Listing | Single IP, IP Range (e.g. 192.168.1.10-192.168.1.100), IPv4, IPv6 |
| Trusted IPs | Automatically when the reputation API returns "TrustedIp" | Any single IP, IPv4 or IPv6 |
| Remote Whitelist | Via the Central API â changes pulled every service cycle without opening the app | Single IPs |
When you save a new whitelist entry, SYSMarshal automatically removes that IP from the firewall block rule if it was previously blocked. On every scan cycle, the whitelist is checked before any banning decision is made.
SYSMarshal sends professionally formatted HTML security reports to any number of recipients â delivered via the SYSMarshal Cloud Mail Service. No local SMTP server or email configuration is required.
| Mode | When It Sends | Best For |
|---|---|---|
| ⥠Immediate | Within seconds of an action being taken | High-security environments requiring instant escalation |
| đ Daily Summary | Once per day at a configured time | Teams reviewing security during daily standups |
| đ Weekly Summary | Every Saturday, covering the full prior week | Low-noise environments or executive-level reporting |
What's included in every email report:
| Element | Description |
|---|---|
| Subject Line | Report type, date/period, and action taken |
| Activity Table | IP address, country, city, timestamp, action, and hostname |
| Geographic Map | Static Google Maps image with red markers at each threat IP's location |
| Interactive Map Link | Clickable link to explore the threat map in Google Maps |
| Branded Footer | Professional SYSMarshal Dynamic Firewall Security sign-off |
Windows Firewall block rules have a practical limit of around 10,000 IP entries. SYSMarshal monitors this capacity and automatically manages it so there is always room to block new threats â without requiring any manual intervention.
FireWall bytes: X (Y%).A separate, lightweight Windows service (SYSMarshal.Watchdog) that runs independently from the main SYSMarshal service. Its job is to monitor whether SYSMarshal itself is running â and to alert you immediately if it stops.
| State | Watchdog Behaviour |
|---|---|
| Service Running | Watchdog logs the status and does nothing â all is well. |
| Service Stopped | Watchdog sends an email alert immediately. Check interval: every 50 seconds. |
| Continued Stopped State | Watchdog sends a maximum of one alert per hour â no inbox flooding. |
Secondary function: The Watchdog also restores the required Windows Audit Policy settings once every 24 hours using AuditPol /restore â ensuring SYSMarshal always has the correct events flowing from Windows even if another tool or user has changed the policy.
The Baseline screen shows a live feed from the SYSMarshal Central Database â a globally shared list of IP addresses flagged as malicious by SYSMarshal installations around the world. This gives you proactive intelligence about threats that haven't attacked you yet.
| What You Can See | Detail |
|---|---|
| Blacklisted IPs | Contributed by other SYSMarshal users globally |
| Confidence Score | Colour-coded from Green (minimal) to Dark Red (critical) |
| Location | Country, city, latitude, longitude of each threat IP |
| Reported Date | When the IP was added to the global database |
| WhoIs Lookup | One click to open a detailed IP ownership report |
| Embedded Map | Click any row to show that IP's location on an in-app Google Map |
Proactive blocking: Select one or more IPs from the Baseline grid and immediately add them to your local Windows Firewall block rule â even if those IPs haven't yet attacked your server. Protect yourself based on the global community's experience.
| License Tier | Baseline Access |
|---|---|
| Individual | Full global data visible; reporter hostnames anonymised |
| All-Data (Business) | Same as Individual â global data with anonymised hostnames |
| Site-License | Full hostnames, plus "View All Data" toggle for the complete global dataset |
An integrated chat interface backed by a large language model hosted on the SYSMarshal cloud. Ask security questions in plain English â no SQL knowledge or Windows expertise required. The AI uses your actual local security data as context.
| Mode | What It Does | Example |
|---|---|---|
| đŦ General Chat | Ask questions about your security data in plain English | "How many IPs were blocked yesterday?" / "Which country attacked me most?" |
| ⥠DEFCON 1 | One-click full vulnerability scan of your machine, analysed by AI automatically | Runs a PowerShell scan, sends output to AI, returns a plain-language security assessment |
An investigation tool that helps you understand exactly what is happening in your Windows event logs â especially useful when setting up SYSMarshal for the first time, or when tuning it for your specific environment.
SYSMarshal includes a built-in report engine and a live status bar dashboard that updates every 10 seconds.
| Report Type | What's Included |
|---|---|
| đ Executive Summary | Total threats blocked, top attacking countries, most targeted ports, and attack frequency trend lines |
| đ Top Attack Countries | Ranked breakdown of countries generating the most blocked IP traffic, with counts and percentages |
| đ Attack Pattern Analysis | Detailed attack vectors, unique attacking IPs, patterns grouped by source characteristics, full blocked IP grid with geo-location and network detail |
All reports can be exported to PDF, XLS, DOCX, HTML, or printed directly from the built-in report viewer.
Live Status Bar â updates every 10 seconds, visible at the bottom of the SYSMarshal application at all times:
A live snapshot of all open TCP and UDP ports on your server â similar to running netstat, but presented in a clean, filterable grid for quick network exposure assessment.
What it shows: TCP listeners, UDP listeners, the local IP each port is bound to, and the port number and protocol. Access it via the "Chk Open Ports" shortcut in the status bar.
Use cases: Identify unexpected open services, confirm which port RDP is listening on, and discover ports that may be unnecessarily exposing your server.
SYSMarshal uses an API key combined with your machine's hardware fingerprint (BIOS serial number) to validate and enforce its subscription. The desktop application manages the service lifecycle directly.
| License State | What Happens |
|---|---|
| â Running (Valid) | Full functionality active â all features available |
| â ī¸ Bad API Key | Invalid key â reputation lookups fail; service continues with local monitoring only |
| â ī¸ Not Running | API unreachable â service continues without cloud intelligence |
| â Expired | Core monitoring tabs disabled; renewal is required |
Choose the tier that fits your needs:
SYSMarshal includes a lightweight Patcher (Patcher.exe) that checks for new versions on every startup and applies them automatically â keeping you protected with the latest threat intelligence and feature improvements.
SYSMarshal depends on Windows Security Auditing to generate the event log entries it monitors. If audit policies are disabled â accidentally or deliberately â key Event IDs stop appearing in the logs, and SYSMarshal cannot detect attacks.
To protect against this, SYSMarshal ships with a pre-configured Audit Policy file (POL_MMC\policy.csv). On every application launch and every 24 hours via the Watchdog, SYSMarshal runs:
AuditPol /restore /file:policy.csv â this restores the required audit policy to the correct configuration, even if another tool, administrator, or attacker has changed or disabled it.A full data browsing interface built into SYSMarshal. Gives administrators direct read access to all data in the local SQL Server database â without needing SQL Server Management Studio or any external tool.
| Table | What It Contains |
|---|---|
| Recent Activities | Full history of every IP action: blacklisted, whitelisted, trusted, archived |
| Whitelist | Current whitelist entries with timestamps |
| Monitored Events | Configured event IDs, names, log names, and enabled/disabled status |
| Logs | Internal application activity and debug log |
| Settings | Current configuration values |
| Range List | Configured IP range entries |
| Firewall Backup | Snapshots of the firewall rule state |
In-app actions available from the Recent Activities view:
| Action | What It Does |
|---|---|
| View | Open the full detail record for any IP action |
| Mark as Whitelisted | Change a previously blacklisted IP to whitelisted status |
| Mark as Trusted | Promote an IP to trusted status |
| Open Google Maps | View the IP's geographic location in a browser |
18456 (SQL Server login failure) by default. Any IP triggering repeated SQL login failures will be automatically blocked according to your configured threshold. This protects on-premises SQL Server instances from brute-force attacks without any additional configuration.