Saeros

Purpose

Saeros is neither a SIEM nor an EDR. Instead, it sits between the two, delivering the contextual insights that most platforms overlook. Its purpose is to detect common user behaviors that could indicate data exfiltration, infiltration, malware activity, or other malicious or suspicious actions.

Key takeaways

• High-performance processing: Ingests tens of thousands of Windows Event Logs per second with minimal CPU usage.
• Low bandwidth footprint: Executes detection logic locally on each host, sending only matched detections over gRPC.
• Automatic audit policy management: Dynamically configures audit policies based on the rules you enable.
• Extensive ruleset: Ships with thousands of curated Sigma rules from the official Sigma repository.
• Customizable rules: Modify any rule at runtime to fit your environment and requirements.
• Flexible detection exclusions: Exclude detections using one or multiple event properties.
• Powerful integrations: Forward detections directly to ElasticSearch.
• MITRE ATT&CK visibility: Explore detection coverage by tactic, technique, or sub-technique.
• Effortless AD deployment: Install agents on domain controllers with a single click.
• Air-gapped ready: Fully operational without internet access.
• Zero external dependencies: Requires no DBMS or third-party components.
• Fast, simple installation: Get started in just a few clicks.

Use cases

Saeros can detect thousands of suspicious activities, including:

• Repeated failed logon attempts (password-guessing attacks)
• Sudden spikes in network traffic from a single process (data exfiltration)
• Remote logins originating from public IP addresses (lateral movements)
• Users being created or added to sensitive user groups (privilege escalation)
• Event logs being cleared (defense evasion)

Installation

Saeros is quick and straightforward to install. Download Saeros-Setup.exe from the Releases page and follow the guided setup.

Deployment

Saeros can be deployed on a standalone Microsoft Windows endpoint and across Microsoft Active Directory domains. The setup installs two Windows services and a desktop application.

Saeros Collector (Agent) – A Windows service that starts automatically with the system. It configures audit policies, subscribes to ETW channels, performs Sigma rule matching, and forwards detections to the Bridge. For simplicity, this service is referred to as the Agent. It usually sits on a standalone Windows workstation or on domain controllers.

Saeros Collector (Bridge) – A Windows service that also starts automatically with the system. It communicates with the Agent, manages Sigma rule configuration, stores detections in a local SQLite database, and forwards them to configured SIEMs. The Bridge exposes an API consumed by the Console. It usually sits on the local installation (where the installer was run).

Saeros Console – A Windows desktop application used to manage Sigma rules and exclusions, browse detections, configure integrations, and deploy collectors to Active Directory domains. It usually sits on the local installation (where the installer was run).

---

Non Domain-Joined Environment

In a non domain-joined (standalone) environment, the installer deploys both services and the Console on the local machine. Saeros immediately begins collecting events, and detections become available in the Console. An Agent can still be deployed to a domain later to monitor domain controllers.

Requirements

This is the simplest setup: no network or firewall configuration is required, and all communication occurs locally. The Saeros Collector (Bridge) service exposes a local HTTP endpoint and uses local gRPC communication with both the Agent and the Console.

---

Domain-Joined Environment

In a domain-joined environment, the installer detects domain membership and can deploy an Agent to each domain controller during setup. Deployment occurs via a Group Policy Object (GPO). Each Agent forwards detections back to the primary domain controller through a gRPC named pipe, then to the local Saeros Collector (Bridge) service (where the installer was run).

Requirements

Deployment must be performed by a user in the Builtin Administrators group. The password is not stored and is used only to establish SMB/LDAP connections during deployment.

The following ports must be open, and firewall rules must allow connections from the Saeros Collector (Bridge) service to the primary domain controller:

• TCP/445
• TCP/389 (or TCP/636 for LDAPS)

Deployment creates a GPO with the following components:

• Protected folder (read-only access for Authenticated Users):
  C:\Windows\SYSVOL\domain\Policies\{3560FF19-45A3-4F9A-956B-937A04D2AABF}
• A scheduled task that installs the Saeros Collector (Agent) service on domain controllers
• The Collector.exe signed binary which is executed by all domain controllers as a Windows service under LocalSystem identity
• Audit.csv containing required audit policies based on configured rules
• Registry values enabling the required ETW channels
• ADMX templates that configure PowerShell policies, including:
  Include command line in process creation events,
  Configure Logon Script Delay,
  Turn on Module Logging,
  Turn on PowerShell Script Block Logging

[!NOTE] Only detections—not full event logs—are sent from the Agent to the Bridge, significantly reducing bandwidth requirements.