From first signal to resolved incident.

LogPulse watches the logs you already collect for signs of an attack. We supply and maintain the detection rules, the agent checks your servers and laptops for software with known vulnerabilities and every alert arrives with a risk score, a first investigation and a plan for handling it. That way your team spends its time on the few alerts that matter.

detection rules we maintain and test before they go live
690+
detection rules we maintain and test before they go live
known vulnerabilities (CVEs) we track
19,000+
known vulnerabilities (CVEs) we track
checks the agent uses to find vulnerable software on your devices
230+
checks the agent uses to find vulnerable software on your devices
fixed places for your data, one per type
16
fixed places for your data, one per type

Spot, connect, resolve.

From loose log lines to one case with a plan, all on the same data.

Raw Logs

12,000 events

Index per type

firewall · iam · dns

Detection Hub

48 detections

Risk Scoring

Per entity, 0–100

Notable

1 critical

Case

Response plan

Reduce noise

From thousands to a handful

Detect faster

Rules we maintain

Correlate smarter

Per device and user

Respond calmly

A case with a plan

Less noise. More to go on.

From the first alert to the check after an update: everything is in the same product, so the context is ready when your team starts.

Fewer alerts

The five that matter, not the ten thousand that don't.

An alert for every rule that fires soon becomes a pile nobody reads. LogPulse adds up all signals from one device or user into a score from 0 to 100. You only get an alert above the threshold, so you keep a short list where nothing important gets lost.

Notablesrisk engine
checkout-svcrisk 92 · critical
10,000 alerts5 notables
Investigated by AI

Every alert arrives with a first investigation.

The AI Investigator gathers the context, weighs whether it is a real threat or a false alarm and writes down why. If you switch it on, it closes alerts that are certainly harmless by itself. You review the rest and the decision stays with you.

AI verdict
checkout-svc· risk 92True positive · 91%
  • Brute force → success from a new ASN
  • Outbound 2.1 GB to an unknown host
Handling incidents

Everyone knows the next step.

Alerts that belong together come together in one case, with an owner and an agreed response time per severity. For phishing, malware, a taken-over account or a data breach, LogPulse proposes a step-by-step plan, from containing the incident to recovery, including whether you need to report it. That way handling doesn't depend on who happens to be on call that night.

Case · Account takeoverresponse plan
highTier 13 notablesSLA resolve 24h
  • Sign the account out everywhereContain
  • Check the sign-in methodsContain
  • Look at the recent sign-insInvestigate
  • Undo forwarding rulesClean up
From vulnerability to finished task

Detection is where the work starts.

For every vulnerability that matters, the Detection Hub delivers a tested rule, a mitigation and ready-made actions: a ticket with a deadline for your IT team, a block in your firewall, a disabled account or a device taken off the network. LogPulse then checks whether the vulnerability is really fixed. Disruptive steps always wait for an owner.

CVE-2026-xxxxxdetection hub
  1. 1Tested rule per vulnerability
  2. 2Mitigation with deadline
  3. 3Ticket in TOPdesk
  4. 4Block IP, after approval
  5. 5Verified as mitigated
How detection and response work
Vulnerable software

Know which device is vulnerable and whether the update worked.

The LogPulse agent sees which software is on your devices and checks it for known vulnerabilities. In the Detection Hub you see which vulnerabilities affect you, on which devices and what to update first: what is actively exploited comes first. After the update you let the agent check again and the ticket in TOPdesk, Jira or ServiceNow gets a note that it is fixed. You don't need a separate scanner for this.

Detection Hub · Overviewpatch order
CVE-2025-04117-Zip 24.07exploited14 hosts
CVE-2024-21762FortiOS 7.2.4exploited2 hosts
CVE-2024-6387OpenSSH 9.6p19 hosts
Check again7-Zip fixed on 14 hosts
Live queries

Ask all your devices at once and get the answer in seconds.

Which computers still run an old version of a program? Is a port open somewhere that should be closed, or did a firewall rule change? With Live queries you ask all your devices that question at once and see the answer per device. Pick one of 20 ready-made questions or write your own. When you schedule a question, LogPulse keeps track of what changes and you can put an alert on it.

Live query · Open ports128 agents
web-01443/tcpnginx
web-0122/tcpsshd
db-prod-35432/tcppostgres
fs-023389/tcpsvchost
Answered by 128 of 128 agents in 4 s
Behavior analytics

Watch risk build before it becomes a breach.

LogPulse learns what is normal for every user and every device. When behavior drifts away from that more and more often, the risk score goes up and you see it while there is still time to step in.

Risk timeline · db-prod-3
02:14unusual login
02:31privilege escalation
02:58data exportrisk 92
Built-in AI

An assistant that can do what your team does.

LogPulse AI searches your logs, looks at alerts and cases and makes proposals: a new detection rule, less noise from an existing rule or an action. It works with the same tools Claude or ChatGPT get through the LogPulse MCP server and can only do what you are allowed to do. Every proposal is tested on your own data first. Whether it then waits for approval is up to you.

LogPulse AI · Workspacemcp tools

Why did db-prod-3 get risk 92 last night?

list_notablesget_blast_radiussearch_logspropose_detection_tuning
Tuning proposed, tested on 7 days of dataawaiting approval

Your data in order, by kind.

Every source lands in its own index, a fixed place per type of data, such as firewall, iam or dns. Detection rules only search the indexes they need. That keeps searches fast, even with a lot of data, and you see at a glance what is coming in.

  • index=windowsEvent Log, Sysmon, PowerShell
  • index=linuxjournald, auditd, sshd, sudo
  • index=firewallFortiGate, Palo Alto, Check Point, Sophos
  • index=networkCisco IOS, F5, VPN, wifi
  • index=dnsDNS queries
  • index=webnginx, Apache, IIS
  • index=emailExchange Online, FortiMail, Defender for Office 365
  • index=iamEntra ID, Okta, Cloudflare Access
  • index=endpointDefender XDR, CrowdStrike, SentinelOne
  • index=auditCloudTrail, Microsoft 365, GitHub
  • index=kubernetespod logs, audit logs
  • index=vulnerabilitiesagent inventory, sensors, scanners

New sources get the right index automatically. You can change it per source. Anything that fits nowhere else goes into the main index.

What you expect from a SIEM, and what comes with it.

Everything you expect from a full SIEM is in there. On top of that, LogPulse does things you would buy elsewhere as a separate product or extra license, on the same data and in the same subscription.

What you expect from a SIEM

  • Risk-based alerting. One risk score per device and user instead of an alert per rule.
  • Alerts and cases. Queues, owners, response times and a step-by-step plan per type of incident.
  • Threat intelligence. Lists of known malicious addresses, such as abuse.ch and Spamhaus, add context to every alert.
  • Behavior analytics. Sign-ins from impossible places, things happening for the first time and sudden spikes.
  • SOAR. Automatic actions with approval, tickets and containing an attack.
  • MITRE ATT&CK coverage. An overview of which attack techniques you cover and which you don't yet.

What LogPulse adds as standard

  • Detection rules we maintain. The Detection Hub publishes new rules, checks and actions. Your environment picks them up every 15 minutes, switched off, so you decide what is turned on.
  • Checks for vulnerable software. An overview of your software, checks for known vulnerabilities, the order to update in and a new check after the update.
  • Its own agent. For Linux and Windows. It collects logs, checks software and answers Live queries.
  • AI that makes proposals. In the app and for your own AI assistants. Every proposal is tested on your data first.
  • Hosted in the EU. At Scaleway in Amsterdam, built in the Netherlands.

Everything to spot attacks and handle them

It all runs on the same storage and search engine as your logs, so there is no separate security database to fill or pay for.

One risk score per device and user

Every server, laptop and user gets a score from 0 to 100. An attack that takes several steps counts for more than noise that keeps repeating. You only get an alert once the score passes a threshold.

Alerts that are already investigated

Before anyone opens an alert, the AI Investigator has gathered the context and given a verdict, with its reasoning. You open the alert as a workspace with notes, evidence and an overview of what else may be affected.

Cases and step-by-step plans

Alerts that belong together in one case, with an owner and a response time per severity. Five step-by-step plans guide you per type of incident, from containing to reporting.

Detection rules we maintain

Over 690 rules from the Detection Hub, mapped to MITRE ATT&CK, the well-known overview of attack techniques. Every rule is tested on a real attack and on normal traffic. You can also write your own rules or import Sigma rules.

Known vulnerabilities and suspicious addresses

The Detection Hub compares the software the agent finds on your devices with lists of vulnerabilities that are actively exploited and delivers a tested rule for each one. Lists of known malicious IP addresses, such as those from abuse.ch and Spamhaus, add context to every alert.

Find vulnerable software

You see which vulnerabilities affect you, on which devices and what to update first. After the update the agent checks again and your service desk gets a ticket for it.

Unusual behavior (UEBA)

Signing in from two countries within an hour, something happening for the first time or a sudden spike in activity. Small signals like these add up to a finding you won't miss.

Automatic response (SOAR)

A ticket in TOPdesk, Jira or ServiceNow, blocking an IP address in Cloudflare or your firewall, disabling an account in Entra ID or taking a laptop off the network through Defender, CrowdStrike or SentinelOne. Disruptive actions always wait for an owner's approval.

The sources you already have

Windows and Linux through the agent, firewalls through syslog and Entra ID, Microsoft 365, Defender, CrowdStrike, SentinelOne, AWS and more through an integration. Everything arrives in the same format, so rules and searches work everywhere.

SIEM questions

What does the LogPulse SIEM do?
It searches the logs you already send to LogPulse for signs of an attack, using detection rules, behavior analysis and lists of known threats. All signals add up to one risk score from 0 to 100 per device or user. Above a threshold you get an alert, which the AI Investigator has already looked into. Alerts that belong together are handled in one case with a step-by-step plan.
Is the SIEM included in the free plan?
Yes. Security monitoring, cases, lists of known threats, the check for vulnerable software, Live queries and actions are in every plan, including Free (1 GB of logs per day, kept for 7 days). Scheduled queries, the Detection Lab and the coverage report for NIS2 and ISO 27001 are in Pro and Business.
Where do the detection rules come from?
From the LogPulse Detection Hub. We maintain over 690 rules there, mapped to MITRE ATT&CK, with a rule for every vulnerability that is actively exploited. A rule only goes live after a person has reviewed it and it passes a test on an attack and on normal traffic. New rules arrive switched off, so you decide what is turned on. You can also write your own rules or import Sigma rules.
Do I need a separate vulnerability scanner?
Not necessarily. The LogPulse agent sees which software is installed and more than 230 checks look for known vulnerabilities in it. If you already use Nessus, Qualys, Defender or another scanner, you can bring those results in too. Everything comes together in the Detection Hub.
How do I handle an incident in LogPulse?
In a case. Alerts that belong together are merged and the case gets an owner, a queue and a response time. LogPulse proposes a step-by-step plan, from containing and investigating the incident to cleaning up, recovering and whether you need to report it under NIS2 or the GDPR.
How does LogPulse respond to an incident?
With actions you link to an alert or a vulnerability: a message, a ticket in TOPdesk, Jira Service Management or ServiceNow, blocking an IP address in Cloudflare or your firewall, disabling an account in Microsoft Entra ID or taking a device off the network through your endpoint security. Disruptive actions need an owner's approval. The SOAR page explains how it works.
Can AI change my detection rules or start actions?
AI can make proposals, but changes nothing unseen. LogPulse AI in the app and your own AI assistants through the LogPulse MCP server use the same tools and can never do more than the user. A proposal is tested on your own data first and by default then waits for a person's approval. You set this in the AI settings.
Which sources can I connect?
Windows and Linux through the LogPulse agent and firewalls and network equipment through syslog. You connect cloud sources with an integration, including Entra ID, Microsoft 365, Defender XDR, CrowdStrike, SentinelOne, Okta, AWS CloudTrail, GitHub and Cloudflare. Every source goes into its own index, such as firewall, iam or endpoint.
Can LogPulse replace my current SIEM?
For most organizations, yes. Risk scores, cases, threat intelligence, behavior analysis and automatic actions are all included. You can first run alongside your current SIEM for a while by sending the same logs to LogPulse as well and comparing the alerts. The comparison pages explain per product what works differently.
Where is my data stored?
In the EU, at Scaleway in Amsterdam. The Detection Hub only receives anonymous counts, such as how many customers use a product, never your logs or the name of your organization.

Start security monitoring on your own logs

The SIEM is in every plan, including Free. You start with 1 GB of logs per day, no credit card needed.

Get started
Hosted in the EU · Rules we maintain · No separate storage needed