Arden is a lightweight Windows security monitor built for system administrators and
IT teams who don't have a SOC. 71 detection rules. Real-time dashboard.
Single executable — no agents, no cloud, no six-figure SIEM contract.
[!] COMPOUND RISK: CRITICAL — Active lateral movement detected
Detection Coverage
71 rules. Every attack phase.
From initial access to impact, Arden covers the full MITRE ATT&CK kill chain
with hand-tuned detection rules and self-exclusion logic that minimizes noise.
63 rules work with native Windows event logs — no Sysmon required.
8 additional rules activate automatically when Sysmon is present, detecting
DLL hijacking, process injection, COM hijacking, timestomping, and UAC bypass.
LOLBins, MSHTA, Regsvr32, WMIC XSL, CMSTP, MSI abuse, renamed binaries, BYOVD Drivers, New Services, Special Privileges, UAC Bypass
3
Discovery
Admin Group Enumeration, Directory Access, Reconnaissance Commands (net, whoami, ipconfig)
3
Impact
Shadow Copy Deletion, BCDEdit Recovery Disable, Critical Service Termination
Capabilities
Everything you need. Nothing you don't.
Built for system administrators, MSPs, and small IT teams who don't have
a dedicated security operations center. Run it on one machine or
monitor your entire Windows network — no cloud, no vendor lock-in.
🚀
30-Second Startup
6 parallel PowerShell readers with HashSet filtering parse 50K+ events in under 30 seconds. No indexing, no pre-processing.
📡
Agent Deployment
Push lightweight agents via admin share + WMI. Pull model with heartbeat monitoring. Deploy to your entire network from the dashboard.
🌐
Real-Time Dashboard
Server-Sent Events stream alerts live. Kill chain visualization, dual filtering (host + severity), and full-text search across all fields.
📄
Export & Report
One-click CSV and JSON exports. Filter-aware — exports respect your active severity, tactic, host, and date range filters.
🚫
False Positive Triage
Suppress by rule, rule+host, or rule+user. Reason tracking. Triage dashboard shows what's hidden and why. One-click removal.
🛡
Sigma Rules
14 custom Sigma YAML rules included. Cobalt Strike pipes, Impacket tools, BITS abuse, potato attacks, download cradles, and more.
Getting Started
Three commands. Full visibility.
No installer. No setup wizard. No dependencies to chase.
Download, run, investigate.
1
Download
Single portable executable. 15MB. Runs on Windows 10/11, Server 2016+. No .NET, no Python, no runtime needed.
2
Run
arden.exe --serve reads local event logs, runs all 71 detection rules, and launches the dashboard.
3
Monitor
Dashboard opens at localhost:8080. See alerts by severity, filter by host, deploy agents to other machines, and export findings for your records.
Comparison
Why Arden?
If you're a system administrator or MSP managing Windows networks, you've probably
looked at SIEM pricing and closed the tab. Arden gives you real detection
coverage in 30 seconds, on the machines you're already managing.
Capability
Traditional SIEM / EDR
Arden
Time to first alert
Days to weeks
✓ 30 seconds
Dependencies
Agent + server + DB + cloud
✓ Zero
Deployment
Professional services
✓ Double-click
Monthly cost
$500 – $5,000+/mo
✓ From $29/mo
Cloud requirement
Required
✓ Fully offline
MITRE ATT&CK coverage
Varies by config
✓ 71 rules out of the box
Data leaves your network
Yes (telemetry/cloud)
✓ Never
Multi-host collection
Requires agent per host
✓ Built-in agent deployment
Pricing
Simple, transparent pricing.
No per-endpoint fees. No ingestion limits. No surprise invoices.
Early access members get a discount on their first year.
Practical guides on Windows event log monitoring, threat detection,
and incident response — written for system administrators, not security researchers.
Threat Detection
5 Windows Event IDs every system administrator should be monitoring
You don't need a SIEM to catch the most common attacks. These five event IDs cover brute force, lateral movement, privilege escalation, and credential theft — and they're already in your logs.
Read article →
Incident Response
How to spot lateral movement without a SOC
When an attacker lands on one machine, they move to others. Here's how to read the trail they leave in Windows event logs — PsExec, WMI, RDP, and pass-the-hash artifacts explained.
Read article →
SMB Security
The $29/month alternative to a six-figure SIEM
Enterprise security tools assume enterprise budgets. Here's how small IT teams can get real threat detection coverage with native Windows logs, open rules, and a single executable.
Read article →
Threat Detection
5 Windows Event IDs every system administrator should be monitoring
By Arden Security • April 2026 • 3 min read
If you're managing Windows machines, your event logs are already recording thousands of events every hour. The challenge isn't a lack of data — it's that you're too busy keeping things running to know which events actually matter. The good news: you don't need to monitor all of them. According to Microsoft's own security monitoring guidance, a small set of event IDs covers the most critical attack patterns — and they're already being recorded on every Windows machine in your environment. Here are the five we think every system administrator should start with.
4625
Failed Logon
Five or more 4625 events for the same account in a short window means someone is guessing passwords. If a 4625 burst is followed by a 4624 (successful logon), the attacker got in. Filter out machine accounts (ending in $) and known service accounts to reduce noise. Focus on failures with Logon Type 3 (network) and Type 10 (RDP).
4624
Successful Logon (Type 3 and Type 10)
Not every 4624 matters — your machines generate hundreds daily. Focus on Logon Type 10 (RDP) from unexpected IPs and Logon Type 3 (network) from workstations to servers. If you see a Type 3 logon from a workstation to another workstation, that's lateral movement. Also watch for Type 9 (NewCredentials) which often indicates pass-the-hash or runas /netonly.
7045
New Service Installed
Every new service on a Windows machine gets a 7045 in the System log. This is how PsExec works — it installs a temporary service on the remote host. Any service with a random name, a path pointing to a temp folder, or running as SYSTEM that you didn't install is worth investigating immediately. Also catches persistence mechanisms where attackers install services that survive reboots.
4698
Scheduled Task Created
Scheduled tasks are the most common persistence mechanism in real-world attacks. A 4698 tells you exactly what was created, what it runs, and who created it. Watch for tasks that run PowerShell with encoded commands, tasks created by non-admin users, or tasks that were created and then deleted quickly (4698 followed by 4699 within minutes — a sign of a living-off-the-land attack).
1102
Security Log Cleared
If your Security log gets cleared, this is the one event that survives (it's written as the log is being cleared). There is almost never a legitimate reason to clear the Security log on a production machine. If you see this, treat it as a critical indicator that someone is covering their tracks. Pair it with Event ID 104 in the System log which records System log clearing.
These five events won't catch everything, but they cover brute force, lateral movement, persistence, privilege escalation, and anti-forensics. According to the Picus Security Red Report 2026, which analyzed over one million malware samples, Defense Evasion and Persistence are the dominant tactics used by attackers today, with 80% of the top 10 MITRE ATT&CK techniques focused on staying hidden and maintaining long-term access. The MITRE ATT&CK framework documents these phases based on real-world observations from thousands of intrusions. You can monitor these event IDs manually with Event Viewer, or let Arden do it automatically with 71 detection rules that cover the full ATT&CK kill chain.
Incident Response
How to spot lateral movement without a SOC
By Arden Security • April 2026 • 3 min read
Lateral movement is how a small breach becomes a full compromise. An attacker lands on one workstation — maybe through a phishing email — and then moves across your network to find domain controllers, file servers, and backup systems. If you catch it early, you contain a single machine. If you miss it, you're rebuilding your entire domain.
The good news: every lateral movement technique leaves traces in standard Windows event logs. Here are the four patterns to look for.
PsExec and remote service creation
PsExec is one of the most common lateral movement tools in real-world intrusions. According to the Cisco Talos 2025 Year in Review, RDP, PowerShell, and PsExec are the top three tools used by ransomware actors. On the target machine, look for Event ID 7045 (service installed) with a service name like PSEXESVC or a random string, and Event ID 5145 showing access to the IPC$ share with the svcctl named pipe. The combination of IPC$ access + new service = someone just ran something remotely on that machine.
Pass-the-hash and NTLM relaying
When an attacker dumps credentials from memory (using tools like Mimikatz) and reuses the hash to authenticate, you'll see Event ID 4624 with Logon Type 9 (NewCredentials) on the source machine, and Logon Type 3 with NTLM authentication (not Kerberos) on the target. In a healthy domain, most authentication should be Kerberos. A burst of NTLM Type 3 logons between workstations is a red flag.
WMI remote execution
Attackers use WMI to run commands remotely because it's a built-in Windows feature that doesn't install anything on the target. Look for Event ID 4648 (explicit credential logon) where the target server name contains "RPCSS" or "HOST" on the source machine. On the target, you'll see Event ID 4624 Type 3 followed by wmiprvse.exe spawning unexpected child processes in the process creation logs.
RDP from unexpected sources
RDP is legitimate, which makes malicious RDP harder to spot. The key indicators: Event ID 4624 Type 10 from workstation-to-workstation (not from a jump server or admin machine), RDP from the loopback address 127.0.0.1 (indicates SSH tunneling), and RDP sessions outside business hours. Also watch Event ID 1149 in the TerminalServices-RemoteConnectionManager log for the source IP of every RDP connection.
The pattern across all of these: one machine reaching out to another in a way it normally doesn't. If WORKSTATION-05 suddenly authenticates to your file server, your DC, and three other workstations within ten minutes — and it's never done that before — that's lateral movement. Arden automates this detection with 13 lateral movement rules that flag exactly these patterns in real time.
SMB Security
The $29/month alternative to a six-figure SIEM
By Arden Security • April 2026 • 3 min read
With new attack vectors, zero-day exploits, and nation-state sponsored threat actors making headlines every week, the question every IT team faces isn't if they'll be targeted — it's whether they'll know when it happens. The cybersecurity adage "prevention is ideal, but detection is a must" has never been more relevant.
So you start looking at detection tools. Splunk Enterprise runs $1,800+ per year per GB of daily ingestion. IBM QRadar starts around $800/month for basic deployments. Microsoft Sentinel charges per GB of log data ingested into Azure. Elastic SIEM is open source but requires dedicated infrastructure to run. LogRhythm, Securonix, Exabeam — all assume enterprise budgets and dedicated security staff to configure and maintain them. You look at the pricing, look at your team of two, and close the tab.
But the need doesn't go away. You still need to be able to see what's happening on your network. You need detection — not next quarter when the budget allows it, but now, on the machines you're already managing. That's where Arden comes in: a simple, affordable, portable solution that gives you direct insight into Windows event logs without the infrastructure, the cloud dependency, or the six-figure price tag.
What you actually need vs. what they're selling you
Enterprise SIEMs do three things: collect logs, run detection rules, and show you a dashboard. For that, you're paying for log ingestion by the gigabyte, agents on every endpoint, a cloud subscription, and usually a professional services engagement to configure it. Most SMBs end up paying $500 to $5,000 per month and still have rules they never tuned and alerts they never check.
What if you could get the detection part — the part that actually finds attacks — without the infrastructure? That's the idea behind Arden. It's a single Windows executable that reads your event logs directly, runs 71 detection rules covering the full MITRE ATT&CK kill chain, and serves a real-time dashboard on localhost. No server. No database. No cloud. No agents (unless you want them for multi-host monitoring).
What $29/month gets you
The Standalone tier runs on a single machine and analyzes its local event logs. In 30 seconds, you go from "I have no idea what's happening on this machine" to a prioritized list of security findings sorted by severity, mapped to MITRE ATT&CK, with contextual explanations of what each alert means and what to do about it. You can import EVTX files from other machines, export findings as CSV or JSON for your records, and suppress false positives so they don't clutter future scans.
For $49/month, the Network tier adds the ability to deploy lightweight agents to every Windows machine on your network, scan your network for hosts, collect logs remotely via admin share or WinRM, and monitor everything from a single dashboard. It's the same detection engine — you're just running it across more machines.
Is it a replacement for CrowdStrike or Sentinel? No. Those tools do real-time endpoint protection, cloud telemetry, and managed threat hunting. But if your alternative is nothing — which is the reality for most SMBs — then 71 detection rules running on your actual logs is infinitely better than hoping your antivirus catches everything.
Arden is currently in development. Join the early access list to be notified
when it launches — and get a discount on your first year.
Windows 10/11 • Server 2016+ • x64 • No runtime required
Why the name?
Named after the Ardennes — the forested
region where Allied defenders held the line against a massive offensive in the
winter of 1944. Arden is built for the same mission: when attackers breach the
perimeter, you need to see what happened, how far they got, and where to cut them off.