SIEM vs SOAR is one of the most common questions in security operations, and one of the most misunderstood. Many teams treat the two as competing products. They are not. A SIEM finds the problem. A SOAR acts on it. Buy them in the wrong order, and you end up automating bad alerts at machine speed.
The market has also changed. Major SIEM platforms now ship with automation built in, and AI agents are starting to triage alerts on their own. This guide explains what each tool does, which one comes first, and when a separate SOAR is still worth paying for.
SIEM vs SOAR: The Short Answer
Think of a SOC as two questions. “Is something wrong?” and “What do we do about it?” The SIEM answers the first. The SOAR answers the second.
What a SIEM does
A SIEM (Security Information and Event Management) pulls logs from endpoints, identity systems, cloud services, firewalls and applications. It puts them in one format, runs detection rules, and raises alerts. It also stores the data, so analysts can search back months later during an investigation.
Its key asset is the detection rule. A SIEM with weak, untuned rules produces noise. A SIEM with well-tuned rules is the backbone of the SOC.
What a SOAR does
A SOAR (Security Orchestration, Automation and Response) takes alerts from the SIEM, EDR, email security and other tools. It runs playbooks: step-by-step workflows that enrich an alert, open a ticket, isolate a device or disable an account. Most SOAR tools also include case management, so evidence and analyst notes stay in one place.
Its key asset is the playbook. And a playbook is only as good as the alert that triggers it.
Side-by-side comparison
| Area | SIEM | SOAR |
|---|---|---|
| Main role | Detection | Response |
| Input | Raw logs and telemetry | Alerts from SIEM, EDR, email and identity tools |
| Key asset | Detection rules | Playbooks |
| Main cost driver | Volume of data ingested and stored | Licenses plus engineering time for playbooks |
| Typical failure | Alert fatigue | Automated action against harmless activity |
| Works on its own? | Yes, with manual response | Rarely, it needs detections to act on |
A SIEM without a SOAR is slow.
A SOAR without a good SIEM is dangerous.
Why the SIEM Comes First
Joint guidance from CISA, the Australian Signals Directorate and partner agencies is clear on the order. SOAR platforms usually do not suit immature environments. That means teams with no SIEM, a brand-new SIEM, or no experienced security staff. The guidance also warns that a badly configured platform can treat normal activity as an incident and disrupt the business.
A four-stage maturity path
- Collect: onboard the most important log sources first, such as identity, EDR, email and cloud, and confirm they parse correctly.
- Detect: tune each detection rule until you know how often it fires on real threats.
- Document: write a short runbook per rule. What does the alert mean, what should the analyst check, and when do they escalate?
- Automate: turn the runbooks analysts follow the same way every time into playbooks. Start with enrichment and ticketing. Add containment last.
Neither tool is “set and forget”
The same guidance tells executives to expect several skilled people working on a SIEM or SOAR rollout full time. Rules drift, log sources change and attackers adapt. Budget for people, not just licenses.
Automation only works on solid foundations. Read our CI/CD and DevSecOps security guide
Do You Still Need a Separate SOAR?
For many organizations, the honest answer is no. The line between the two categories has faded.
SIEM platforms now include automation
Microsoft Sentinel ships with automation rules and playbooks built on Azure Logic Apps. Google Security Operations includes SOAR in the same product family. If you already run one of them, you already own a SOAR engine. The real question is whether it covers your workflows.
Sentinel users have a deadline to plan around. After March 31, 2027, Sentinel will no longer be supported in the Azure portal and will run only in the Microsoft Defender portal. Build and test new automation there now, and check which playbook actions behave differently before the cutover.
Where XDR fits
XDR platforms detect and respond across one vendor’s endpoints, identities, email and apps. They act like a small SIEM and a small SOAR inside a single ecosystem. If you have third-party log sources, long retention needs or cross-vendor investigations, you still need a SIEM. The XDR becomes one of its best data feeds.
AI triage agents are the new layer
Vendors now offer AI agents that review alerts, such as user-reported phishing, and decide whether they are real. They close false positives and pass real threats to an analyst. Treat them like any automated decision-maker. Limit their permissions, review a sample of what they close, and keep a way to reverse their actions.
When a standalone SOAR is worth it
- You run more than one SIEM, for example after an acquisition, or you are an MSSP serving many clients.
- Your playbooks reach far beyond security tools, into ITSM, on-call paging and internal APIs.
- You already have a large library of working playbooks that would be costly to rebuild.
- You have dedicated automation engineers who will use the extra depth.
If none of these apply, native SIEM automation is usually enough. It also means one less platform to license, patch and keep in sync.
SIEM vs SOAR Costs and What to Ask Your Provider
Where the money goes
SIEM cost grows with data. Most vendors charge by the volume you ingest and keep. Your levers are which sources you collect, how much you filter at ingestion, and how long you keep hot versus archived data.
SOAR cost grows with integrations. Every playbook that calls an outside tool can break when that vendor changes its API. A playbook that touches six tools has six ways to fail. Give each playbook an owner and a yearly test, not a one-time build.
Questions for an MSSP or MDR provider
- Do the SIEM and playbooks run in our tenant or yours?
- Who owns the detection rules and playbooks if we end the contract?
- Which automated actions need our approval first?
- How are detections tested before they go live?
SECITHUB Take
For most SMB and mid-market teams, a separate SOAR is a budget item that can wait. The better investment is a well-tuned SIEM, clean identity and EDR logs, and runbooks people actually follow. Use the automation already built into your SIEM first. Buy a standalone SOAR only when you can name the playbooks it will run and the person who will maintain them.
Detect well first.
Then automate what you already do well.
Identity logs are your most valuable SIEM source. Read our Zero Trust access management guide
Running a SIEM, a SOAR or both? Share what works for your SOC.
Join the discussion at r/secithubcommunity

A SIEM collects and analyzes logs to detect threats and raise alerts. A SOAR takes those alerts and runs playbooks to enrich, route and respond to them. The SIEM decides what looks suspicious, and the SOAR decides what happens next.
Start with the SIEM. Joint guidance from CISA and partner agencies says SOAR platforms usually do not suit environments without a mature SIEM or an experienced security team. Automation is only as good as the alerts it receives.
Yes. Microsoft Sentinel includes automation rules and playbooks built on Azure Logic Apps. After March 31, 2027, Sentinel will be supported only in the Microsoft Defender portal, so new automation should be built and tested there.
A standalone SOAR makes sense if you run more than one SIEM, orchestrate many non-security systems, already have a large playbook library, or have dedicated automation engineers. Otherwise, native SIEM automation is usually enough.
Not for most organizations. XDR detects and responds within one vendor’s ecosystem. If you have third-party log sources, long retention needs or cross-vendor investigations, you still need a SIEM, and the XDR becomes one of its data sources.
SIEM costs grow with the volume of data you ingest and retain. SOAR costs grow with integrations, because every playbook that calls another tool needs maintenance when that tool changes.
Sources
Guidance for SIEM and SOAR Implementation – CISA
Implementing SIEM and SOAR platforms: Practitioner guidance – Australian Signals Directorate
What is Microsoft Sentinel? – Microsoft Learn
What’s new in Microsoft unified security operations – Microsoft Learn


