← All automations
IT & Security·6–16 weeks·6–10 weeks

Log Anomaly Detector

Rule-based SIEMs catch known attacks. This catches the unknown ones — deviations from per-user, per-system baselines. Ships findings into your existing SIEM / SOC workflow; does not replace it. Cuts mean-time-to-detect from days to hours.

Mean time to detect
Days → hours
Alert noise
−40%
Coverage of unknown threats
Added layer
The problem

What this fixes.

  • Sophisticated attackers don't trip rules

  • MTTD measured in days, not hours

  • SOC team buried in alert fatigue

How it works

Three jobs, on rails.

Baseline

Per entity

User + system + service behavioural baselines.

Detect

Anomalies

Statistical + ML deviations, severity-scored.

Triage

SOC-ready

Findings shipped into your existing SOC workflow.

From signed proposal to live

The path.

01

Pipe access, system and audit logs into the model for a baselining window.

02

Calibrate severity per entity type with the SOC team.

03

Surface findings inside the existing SIEM — never a second console.

04

Tune monthly on confirmed true-positives and false-positives.

A real moment

One scenario, one outcome.

The scenario

A trusted admin starts pulling 22 GB of database backups at 04:00 from an unusual IP.

The outcome

Behavioural baseline trips inside 90 seconds. Alert lands in the SIEM with the reasoning ('off-hour + unusual IP + volume p99'). SOC contains in 18 minutes vs the days it would have taken on rules alone.

Engagement

Scoped on a call.

Delivery

6–10 weeks

Engagement model

Pilot → retainer

Scope confirmed in a 30-minute call. Fixed scope, fixed timeline before you sign. We'll send a one-page proposal within 48 hours.

Book a call →
Want this in your workflow?

Talk to us about your version.

Start a project