Where will your logs live?
A vendor's cloud and region, or your own servers and cloud account. Logs describe your users, systems and incidents.
A SIEM collects logs from across your organization, turns them into searchable events, watches them for attacks and helps your team investigate. Here is how it works, how it differs from SOAR and EDR, and what to weigh when you choose one.
NIST defines a SIEM as a program that provides centralized logging for a variety of log types. Modern SIEMs go further: they detect, and they help you investigate.
Pull or receive logs from firewalls, servers, endpoints, identity providers, cloud platforms and SaaS apps.
Parse each source into one schema, so a sign-in from Okta and one from Entra ID look alike.
Keep events searchable for as long as your policy or regulator requires.
Run detection rules on events as they arrive and on a schedule, and raise alerts.
Group related alerts into cases, pivot across sources and record what you found.
Hand off to response tooling, and keep the evidence trail for audits and incident reports.
Most environments use all four. The SIEM then parses each source into one schema; nano uses OCSF, an open schema for security events.
| Method | How it works | Typical sources |
|---|---|---|
| Agents and aggregators | A small agent on each host forwards Windows events, Linux logs and files to an aggregator on your network, which buffers and sends them on. | Windows Event Log, Sysmon, auditd, journald, files |
| Syslog | Network devices send syslog to an aggregator, which tags and forwards it. | Firewalls, switches, routers, appliances |
| Push over HTTP | Pipelines and apps send events over HTTP Event Collector (HEC), HTTP or OpenTelemetry (OTLP). | Cribl, Fluent Bit, OpenTelemetry Collector, your apps |
| Cloud and SaaS pull | The SIEM reads from cloud queues and vendor APIs with credentials you own. | AWS S3/SQS, GCP Pub/Sub, Azure Event Hubs, Kafka, Okta, Google Workspace |
With nano, every install starts with zero log sources: you choose which to onboard and pick a parser from the catalog for each. Ingest data in nano
SIEM finds and explains. SOAR acts. EDR and XDR protect the devices and products they cover. Joint 2025 guidance from CISA, ASD's ACSC and partner agencies covers implementing both.
| Works on | Main job | Why you'd want it | |
|---|---|---|---|
| SIEM security information and event management | Logs and events from everything | Central collection, search, detection and alerting; the evidence trail | Detect and investigate across the whole estate |
| SOAR security orchestration, automation and response | Alerts and cases, usually from the SIEM | Playbooks and automated actions against other tools' APIs | Respond faster and the same way every time |
| EDR / XDR endpoint / extended detection and response | Telemetry from the vendor's own agents and products | Detection and response on endpoints (EDR) or across one vendor's stack (XDR) | Stop threats on the devices it covers |
| Log management | Logs from anything | Collection, storage and search, without security detections or cases | Troubleshooting, operations, retention |
A vendor's cloud and region, or your own servers and cloud account. Logs describe your users, systems and incidents.
Volume, workload, endpoints or users, plus retention. Model a year of growth before you sign.
A cloud SIEM shifts operations to the vendor. A self-hosted one keeps control with you, and the work too.
Query language, data format and content portability decide what a future move costs.
SIEM stands for security information and event management. NIST's glossary defines it as a program that provides centralized logging capabilities for a variety of log types. In practice, a SIEM collects logs from across an organization, normalizes them, stores them searchably, runs detections over them and supports investigation of what it finds.
A SIEM is the system a security team uses to see across its whole environment. It gathers logs from firewalls, servers, endpoints, identity providers and cloud services into one place, runs detection rules to raise alerts, and gives analysts search and case tools to investigate. It is also where the evidence lives when an incident has to be reported or audited.
Four ways, usually combined: agents on hosts that forward Windows and Linux logs to an aggregator; syslog from network devices, received by that aggregator; push over HTTP, HEC or OpenTelemetry from pipelines and applications; and pull from cloud queues and SaaS APIs such as AWS S3 and SQS, Azure Event Hubs or Okta. The SIEM then parses each source into one schema.
A SIEM finds and explains: it collects and stores logs, detects suspicious activity and supports investigation. SOAR (security orchestration, automation and response) acts: it runs playbooks and automated actions, such as disabling an account or blocking an address, through other tools' APIs. SOAR usually takes its alerts and cases from the SIEM. Many products now combine the two.
No. Endpoint detection and response (EDR) watches the devices where its agent runs, and extended detection and response (XDR) extends that across one vendor's products. A SIEM takes in logs from every source, including EDR alerts and telemetry, and keeps them for search, correlation and evidence. Most teams run both.
Splunk's SIEM product is Splunk Enterprise Security, which Splunk describes as a unified threat detection, investigation and response platform including SIEM, SOAR and UEBA. Microsoft Sentinel is Microsoft's cloud SIEM, now used through the Microsoft Defender portal. nano is a SIEM you run yourself, on your own infrastructure.
Commercial SIEMs include nano, Splunk Enterprise Security, Microsoft Sentinel and Elastic. Free and open-source options include nano's AGPL-licensed engine, Wazuh and Security Onion. They differ in where they run (vendor cloud or your own infrastructure), how they are priced and how much operating work they need.
SIEMs are usually priced by data volume (GB ingested per day), by workload or compute, or by the number of endpoints or users, plus the cost of storage and the people to run it. nano is licensed per GB/day of ingest from US$149/month, and you provide the infrastructure. Microsoft Sentinel bills per GB ingested or by commitment tier; Splunk offers activity-based, ingest or workload pricing.
Yes. In May 2025, CISA, the Australian Signals Directorate's Australian Cyber Security Centre and partner agencies jointly published guidance for executives and practitioners on implementing SIEM and SOAR platforms, including which logs to ingest first. Central, protected, analyzed logs remain the base of detection, incident response and many regulatory requirements.
Yes. Some SIEMs are cloud services only, while others can be installed on your own servers or cloud account. nano is a self-hosted SIEM: logs are collected, stored and analyzed in your environment and never sent to us, and if your environment requires it, it can also run air-gapped, with no connection to nano at all.
Last reviewed 13 November 2026.
From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.