argussoc

observe · evidence · incidents

Security for servers, workstations and network equipment

ArgusSOC reads server logs and syslog from network equipment, gathers evidence into incidents and explains why each one is an incident. It changes nothing on your systems.

  • linux
  • freebsd
  • windows
  • macos
  • equipment via syslog

$ argus --how

How it works

Data flows one way: from your systems to the center.

  1. [agent]

    01 Agent

    A small program on a server or workstation. It reads login logs and the protection state: firewall, packages, listening ports, accounts.

  2. [hub]

    02 Hub

    Sits inside your network. Receives agent data and syslog from equipment, keeps a queue on disk when the link is down, and sends everything over a single channel.

  3. [center]

    03 Center

    Groups events into incidents with evidence, evaluates them with rules that have open thresholds, and sends notifications.

  4. [panel]

    04 Panel

    A web panel for your team: incidents, servers, equipment, vulnerabilities and backups. Works on a phone too.

$ argus --features

Features

Everything you need to know about the security of a node, in one place.

01incidents

An incident with evidence, not a stream of events

A burst of failed logins, a login after brute force, a new access key, a new listening port. Every incident carries a “why” line and evidence with time and source.

02equipment

Switches, routers, UPS units

The hub receives syslog and parses it by device type. A login from an unknown address, password guessing or a configuration change outside the maintenance window becomes a suspicion.

03posture

Weak spots before others find them

A firewall that allows everything, a database without a password on the network, Windows auditing switched off. A finding closes itself once the problem is fixed.

04vulnerabilities

Packages checked against databases daily

The center refreshes vulnerability databases once a day and checks every server's packages against them. Vulnerabilities already exploited in the wild are marked separately.

05load

CPU, memory, disks, network

Charts from one hour to one year with incident markers on the same timeline. You can see what the server was doing at the moment of the event.

06backups

Encrypted copies under watch

On schedule the agent runs your script, encrypts the file and uploads it to storage. Backups made by other programs are visible too: whether they ran and how they ended.

07workstations

Employee computers

The agent runs on Windows and macOS. On Windows you see whether updates are installed, whether built-in protection is running and which USB drives were connected.

08alerts

A messenger for the on-call team

New incidents arrive in your team's messenger. You also learn when a source goes silent.

09ai analysis

Explained in plain language

A model reads the incident's evidence and explains what happened and what to check. Its verdict is not evidence: an incident is opened by a rule, not by the model.

10teams

Everyone sees only their own

Several organizations, branches or customers in one installation. Roles from viewer to owner, sign-in by invitation only, every action written to the audit log.

$ argus --panel

Panel

Organization overview: open incidents, server and hub status, coverage gaps.

argussoc://overviewdemo
ArgusSOC panel: organization overview with open incidents, server and hub status and coverage gaps

Panel screenshot with demo data.

$ argus --principles

Principles

A security service must not become a risk itself.

  • [ ok ]

    Observe only

    The agent and the hub change nothing on servers or equipment. They have no remote commands.

  • [ ok ]

    Everything is signed

    Updates and settings from the center are accepted only with a signature.

  • [ ok ]

    Honest about coverage

    If a source is silent or delivers incomplete data, the panel shows it. No events does not mean “clean”.

  • [ ok ]

    Rules, not a black box

    Every rule has an open threshold and false-positive statistics.

  • [ ok ]

    A human has the last word

    An operator confirms an incident or marks a false positive. That decision is logged and feeds back into rule quality.

  • [ ok ]

    Data stays in the organization

    The addresses of your servers and users are visible only to members of your organization.

$ argus request-access

Request access

There is no sign-up: access is by invitation. Leave a request and we will get back to you.

Form data goes only to the ArgusSOC team. The site stores a single cookie: your chosen language.