✕ Close Menu
🚀
Quick Start Guide

Follow these five steps to get SYSMarshal protecting your Windows Server within minutes.

01
Install SYSMarshal
Download and run the installer. SYSMarshal installs as a Windows Service and desktop application.
02
Enter Your API Key
Go to Settings → Licensing and enter your API Key. This connects SYSMarshal to the cloud reputation database.
03
Whitelist Your IPs
Before activating, add your office, VPN, and admin machine IPs in Settings → White Listing to avoid locking yourself out.
04
Configure Email Alerts
Set up your notification email address and choose Immediate, Daily, or Weekly alert mode.
05
Start the Service
Click Start Service. SYSMarshal begins monitoring Windows event logs and will block attackers automatically.
âš ī¸
Important Before You Start
Always whitelist your own IP addresses (office, VPN, development machine) before starting the service. This is the single most important pre-activation step — it prevents you from accidentally blocking your own access to the server.
📋
Feature Overview

SYSMarshal includes 17 integrated features. Click any card to jump to its full documentation.

01
đŸ›Ąī¸
Auto-Block Engine
Continuously monitors logs and blocks attackers without human intervention.
02
đŸ—‚ī¸
Event Log Monitoring
Reads Windows Security & Application logs for suspicious activity.
03
🌐
IP Reputation
Cross-checks every IP against a global threat intelligence database.
04
📍
Geo-Location & Maps
Visualises attacker locations on interactive and email-embedded maps.
05
🔐
Whitelist
Protects trusted IPs from ever being blocked.
06
📧
Email Alerts
Instant, daily, or weekly HTML reports sent automatically.
07
🔄
Firewall Capacity
Self-manages Windows Firewall rule capacity automatically.
08
🐕
Watchdog Service
Independent guardian that alerts you if SYSMarshal stops.
09
🌍
Global Baseline
Live community threat feed from all SYSMarshal installations worldwide.
10
🤖
AI Assistant
Ask plain-English security questions about your own data.
11
đŸ”Ŧ
Diagnostics
Discovers which event logs contain suspicious IPs on your machine.
12
📊
Reports
Executive summaries, country rankings, and attack pattern reports.
13
🔌
Port Monitor
Live snapshot of all open TCP/UDP ports on your server.
14
🔑
Licensing
API key + hardware fingerprint licensing with a 12-hour grace period.
15
âŦ†ī¸
Auto Updates
Checks for new versions on startup and applies them automatically.
16
📋
Audit Policy
Self-healing Windows audit policy enforcement every 24 hours.
17
đŸ—„ī¸
Data Explorer
Built-in SQL browser for your complete local security history.
đŸ›Ąī¸
Auto-Block Engine
Feature 01 of 17

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.

1
Scan Cycle
The engine runs on a configurable interval (default every 5 minutes). On first start it runs every 2 seconds to establish a baseline immediately.
2
IP Extraction
For each monitored event, SYSMarshal reads matching Windows event records and extracts every IP address found in the event data.
3
Banning Decision
When an IP exceeds Max Wrong Tries, SYSMarshal checks: Is it whitelisted? Is it a private IP (if private blocking is off)? Is it trusted? Then it queries the Central API for a reputation score.
4
Firewall Block Rule
SYSMarshal writes the offending IP to the "SYSMarshal IP Jailhouse" rule in Windows Firewall — a single dedicated block rule that keeps the rest of your firewall configuration untouched.
5
Desktop Notification
A toast notification with a sound alert appears on the desktop the moment a new IP is blocked.
6
Full Logging
Every block is recorded: IP address, event ID, timestamp, geo-location, source/destination port, protocol, direction, and abuse confidence score.

Configurable Parameters — adjust these in Settings to match your environment's risk tolerance:

SettingWhat It ControlsDefault
Max Wrong TriesHow many times an IP must appear in event logs before it is blocked3
Wrong Try SpanThe time window (in minutes) in which attempts are counted99999 (all-time)
Minutes to PauseGap between each scan cycle5 minutes
Allow Private IPsWhether local network IPs (192.168.x.x, 10.x.x.x) can be blockedOff
4th Octet Attack CountThreshold for blocking at the subnet level25
â„šī¸
IPv4 & IPv6 Support
SYSMarshal fully supports both IPv4 and IPv6 addresses throughout — IP validation, range checking, whitelist lookup, and firewall rule insertion all handle both address families transparently.
đŸ—‚ī¸
Windows Event Log Monitoring
Feature 02 of 17

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 IDLogDescriptionWhat It Catches
4625SecurityAccount failed to log onBrute-force attacks on Windows login and RDP
5152SecurityWFP blocked a packetIP-level intrusion attempts at the firewall layer
5157SecurityWFP blocked a connectionActive port scanning activity
4723SecurityPassword change attemptUnauthorised attempts to change account passwords
1102SecurityAudit log clearedClassic attacker tactic to hide evidence
4719SecurityAudit policy changedAttempts to disable logging or weaken Windows auditing
18456ApplicationSQL Server login failureBrute-force attacks on SQL Server
5140SecurityNetwork share accessedUnauthorised access to shared folders
5158SecurityOutbound connection requestedLateral movement or command-and-control beaconing
💡
Custom Event IDs
You can add any Windows Event ID from any log (Security, Application, System, etc.) through the monitored events configuration. Use the Diagnostics screen (Feature 11) to discover which event IDs on your specific machine contain suspicious IP activity.
🌐
Global IP Reputation
Feature 03 of 17

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.

1
Reputation Query
SYSMarshal sends the IP to the Central API endpoint. The response is either Blacklisted;<score> or TrustedIp;<score>.
2
Blacklisted Response
The IP is added to the Windows Firewall block rule and logged with its abuse confidence score.
3
Trusted IP Response
The IP is recorded as "TrustedIP" and is not blocked — even if it appears repeatedly in event logs. This prevents legitimate services from being locked out.

Abuse Confidence Score — every blocked IP is tagged with a score from 0–100, colour-coded for instant threat assessment:

75–100🔴 Critical
50–74🔴 High Risk
25–49🟠 Medium-High
10–24🟠 Medium
5–9🟡 Low Risk
1–4đŸŸĸ Minimal
0✅ No Score
🔍
WhoIs Lookup
Every IP in the Baseline screen has a WhoIs button that opens a detailed report showing public registration, ownership, and abuse history for that IP.
📍
Geo-Location & Map Visualisation
Feature 04 of 17

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 CollectedExample
CountryUnited States
CityLos Angeles
Latitude / Longitude34.0522 / -118.2437
Postal Code90001
Google Maps URLDirect 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.

🔐
Whitelist & Trusted IPs
Feature 05 of 17

Two independent protection mechanisms ensure that legitimate IPs are never blocked: your Whitelist (manually defined) and Trusted IPs (automatically populated via the reputation API).

MechanismHow It's PopulatedFormat Supported
WhitelistManually via Settings → White ListingSingle IP, IP Range (e.g. 192.168.1.10-192.168.1.100), IPv4, IPv6
Trusted IPsAutomatically when the reputation API returns "TrustedIp"Any single IP, IPv4 or IPv6
Remote WhitelistVia the Central API — changes pulled every service cycle without opening the appSingle 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.

âš ī¸
Critical First Step
Always add your own office IP, VPN IP, and any remote admin machine IPs to the whitelist before starting the SYSMarshal service. Failure to do so may result in blocking your own access to the server.
📧
Email Alert System
Feature 06 of 17

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.

ModeWhen It SendsBest For
⚡ ImmediateWithin seconds of an action being takenHigh-security environments requiring instant escalation
📅 Daily SummaryOnce per day at a configured timeTeams reviewing security during daily standups
📆 Weekly SummaryEvery Saturday, covering the full prior weekLow-noise environments or executive-level reporting

What's included in every email report:

ElementDescription
Subject LineReport type, date/period, and action taken
Activity TableIP address, country, city, timestamp, action, and hostname
Geographic MapStatic Google Maps image with red markers at each threat IP's location
Interactive Map LinkClickable link to explore the threat map in Google Maps
Branded FooterProfessional SYSMarshal Dynamic Firewall Security sign-off
🐕
Watchdog Alerts
A separate alert is triggered if the SYSMarshal service stops unexpectedly. The Watchdog sends a maximum of one alert per hour to prevent inbox flooding.
🔄
Firewall Capacity Management
Feature 07 of 17

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.

1
Capacity Monitoring
SYSMarshal tracks the entry count in the "SYSMarshal IP Jailhouse" rule and displays live usage in the status bar as FireWall bytes: X (Y%).
2
90% Threshold Triggered
When the rule reaches 90% capacity, automatic relief begins.
3
Archive Oldest 20%
The oldest 20% of blocked IPs are removed from the active firewall rule and marked as "Archived" in the database. No data is deleted — history is fully preserved.
4
Headroom Restored
The firewall rule now has ~20% free capacity again. The most recently active threats remain actively blocked.
💡
Data Is Never Lost
Archived IPs remain fully searchable in the Data Explorer. Only the active firewall rule entry is removed — the oldest, least-recently-active offenders are retired first, while current active threats stay protected.
🐕
Watchdog Service
Feature 08 of 17

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.

StateWatchdog Behaviour
Service RunningWatchdog logs the status and does nothing — all is well.
Service StoppedWatchdog sends an email alert immediately. Check interval: every 50 seconds.
Continued Stopped StateWatchdog 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.

🌍
Global Baseline
Feature 09 of 17

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 SeeDetail
Blacklisted IPsContributed by other SYSMarshal users globally
Confidence ScoreColour-coded from Green (minimal) to Dark Red (critical)
LocationCountry, city, latitude, longitude of each threat IP
Reported DateWhen the IP was added to the global database
WhoIs LookupOne click to open a detailed IP ownership report
Embedded MapClick 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 TierBaseline Access
IndividualFull global data visible; reporter hostnames anonymised
All-Data (Business)Same as Individual — global data with anonymised hostnames
Site-LicenseFull hostnames, plus "View All Data" toggle for the complete global dataset
🔍
Search & Navigation
The Baseline view supports full-text search across all columns, paginated results (up to 10,000 records per page), column sorting, and multi-row selection for bulk operations.
🤖
AI Security Assistant
Feature 10 of 17

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.

ModeWhat It DoesExample
đŸ’Ŧ General ChatAsk questions about your security data in plain English"How many IPs were blocked yesterday?" / "Which country attacked me most?"
⚡ DEFCON 1One-click full vulnerability scan of your machine, analysed by AI automaticallyRuns a PowerShell scan, sends output to AI, returns a plain-language security assessment
🔑
Setup Required
The AI Assistant requires an AI API Key, configured in Settings → Licensing → AI API Key. Your available credit balance is shown in the chat interface and updated after each conversation. You can purchase AI credits at sysmarshal.com/ai-topup.
đŸ”Ŧ
Diagnostics & Event Discovery
Feature 11 of 17

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.

1
Full Log Scan
SYSMarshal scans all Windows event logs in parallel, using regex matching to find any log entry containing an IP address.
2
Ranked Results
Events containing IPs are grouped by Event ID and sorted by total IP count (highest first). Already-monitored events are flagged.
3
IP Drilldown
Click the IP count for any event to see every individual IP found, with geo-location and appearance count for each.
4
Add to Monitoring
Check any event ID and click Save. SYSMarshal adds it to your monitored events list immediately — no manual event ID lookup needed.
📊
Security Reports & Dashboards
Feature 12 of 17

SYSMarshal includes a built-in report engine and a live status bar dashboard that updates every 10 seconds.

Report TypeWhat's Included
📋 Executive SummaryTotal threats blocked, top attacking countries, most targeted ports, and attack frequency trend lines
🌍 Top Attack CountriesRanked breakdown of countries generating the most blocked IP traffic, with counts and percentages
🔍 Attack Pattern AnalysisDetailed 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:

SYSMarshal SVC
Running / Stopped / Not Installed
IPv4 / IPv6
Local machine IP addresses
FireWall bytes
X (Y%) — current rule capacity
Hostname
Machine name
License
License type in use
RDP Port
Auto-detected configured RDP port
Blacklisted IPs
Live count of currently blocked IPs
Whitelisted IPs
Count of whitelisted entries
CentralDBstatus
Running / Not Running / Bad API key
LocalDBstatus
Online / Offline
Chk Open Ports
Clickable — opens the Port Monitor
SYSMarshal V.
Current installed version
🔌
Port Connection Monitor
Feature 13 of 17

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.

🔑
Service & Licensing
Feature 14 of 17

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 StateWhat Happens
✅ Running (Valid)Full functionality active — all features available
âš ī¸ Bad API KeyInvalid key — reputation lookups fail; service continues with local monitoring only
âš ī¸ Not RunningAPI unreachable — service continues without cloud intelligence
❌ ExpiredCore monitoring tabs disabled; renewal is required
â„šī¸
12-Hour Grace Period
If your license becomes invalid (e.g. during a brief API outage), SYSMarshal continues to operate normally for 12 hours. After 12 hours, the service stops to enforce the license. This prevents disruption from temporary connectivity issues.

Choose the tier that fits your needs:

Individual
$99 / year
Full local IP blocking
Global Baseline (anonymised)
All 17 core features
Email alerts
AI Assistant (with credits)
Get Individual
Site-License
From $90 / year
Everything in All-Data
Full hostnames in Baseline
"View All Data" global toggle
Cross-site data visibility
Volume pricing available
Get Site-License
âŦ†ī¸
Automatic Updates
Feature 15 of 17

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.

1
Version Check
On startup, SYSMarshal queries the Central API for the latest available version number.
2
Comparison
The installed version is compared to the latest using semantic versioning.
3
Update Prompt
If a newer version is available, you are prompted: "There is a new version (X.Y.Z) available, do you want to update?"
4
Automatic Apply
If confirmed, the Patcher launches with elevated privileges and applies the update automatically.
📋
Audit Policy Enforcement
Feature 16 of 17

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:

âš™ī¸
Automatic Policy Restore Command
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.
🚨
Why This Is Critical
Attackers frequently disable Windows audit logging as one of their first steps — to hide their activity from security tools. SYSMarshal detects this through event ID 4719 (Audit Policy Changed) and reverses it automatically. Without this protection, SYSMarshal's data feed could be silently disabled.
đŸ—„ī¸
Data Explorer
Feature 17 of 17

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.

TableWhat It Contains
Recent ActivitiesFull history of every IP action: blacklisted, whitelisted, trusted, archived
WhitelistCurrent whitelist entries with timestamps
Monitored EventsConfigured event IDs, names, log names, and enabled/disabled status
LogsInternal application activity and debug log
SettingsCurrent configuration values
Range ListConfigured IP range entries
Firewall BackupSnapshots of the firewall rule state

In-app actions available from the Recent Activities view:

ActionWhat It Does
ViewOpen the full detail record for any IP action
Mark as WhitelistedChange a previously blacklisted IP to whitelisted status
Mark as TrustedPromote an IP to trusted status
Open Google MapsView the IP's geographic location in a browser
❓
Frequently Asked Questions
Before activating the service, go to Settings → White Listing and add your own IP addresses — your office connection, VPN, and any remote admin machine IPs. This prevents SYSMarshal from accidentally blocking your own access to the server. This is the single most critical setup step.
No. SYSMarshal creates and manages a single dedicated firewall rule called "SYSMarshal IP Jailhouse". All blocked IPs are written exclusively to this rule. Your existing firewall rules, policies, and configurations are left completely untouched.
SYSMarshal includes a 12-hour grace period. If the license becomes invalid, the service continues operating normally for 12 hours — protecting against brief API outages. If the API is simply unreachable (but the key is valid), the service continues running using local data only, without cloud intelligence. After 12 hours of an invalid license, the service stops to enforce the subscription.
Go to the Data Explorer (Feature 17), open the Recent Activities table, find the IP address, and click "Mark as Whitelisted". SYSMarshal will remove it from the firewall block rule automatically and add it to the whitelist to prevent re-blocking. Alternatively, add the IP directly via Settings → White Listing.
Yes. SYSMarshal monitors Windows Application event log entry 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.
Individual and All-Data licenses show the global Baseline threat feed with anonymised reporter hostnames. The Site-License additionally shows the full hostnames of machines reporting each IP globally, and includes a "View All Data" toggle for access to the complete global dataset. Site-License is designed for organisations managing multiple servers who need cross-site visibility.
Yes. SYSMarshal fully supports both IPv4 and IPv6 throughout the entire pipeline — event log extraction, whitelist checking, reputation lookup, and Windows Firewall rule insertion all handle both address families transparently and automatically.
Use the Diagnostics screen (Feature 11). It performs a parallel scan of all Windows event logs, groups results by Event ID sorted by IP count, and flags which events are already monitored. You can then check any Event ID in the results and click Save to add it directly to monitoring — no manual lookup required.