The three layers of security incident management tools
| Layer | What it does | Typical products | Where it stops |
|---|---|---|---|
| Detection | Collects logs and signals, raises alerts | Microsoft Sentinel, Splunk, Elastic Security, CrowdStrike | Does not run the rota or the response channel |
| Automation | Runs scripted steps such as enrichment and blocking | Splunk SOAR, Palo Alto Cortex XSOAR, Tines | Needs stable playbooks, adds build and upkeep work |
| Coordination | Pages the responder, escalates, opens the channel, keeps the timeline, updates stakeholders | PagerDuty, IncidentBot, incident.io | Does not detect or block anything |
A SIEM can email or webhook an alert. That is a notification, not a rota. If the alert fires at 03:00 and the one analyst it was addressed to is asleep, nothing happens until morning. The coordination layer closes that gap with an on-call rotation and an escalation policy that moves to the next person when nobody acknowledges.
What the coordination layer costs for 10 responders
Monthly list prices at annual billing. PagerDuty Professional is 21 USD per user, checked on pagerduty.com in November 2026. IncidentBot prices are on the pricing page.
| Tool | Per responder a month | 10 responders | Notes |
|---|---|---|---|
| PagerDuty Professional | 21 USD | 210 USD | Paging, status page and workflow are priced separately |
| IncidentBot Starter | 24 USD | 240 USD | Rotation, escalation, Slack incident channel, timeline, 1 status page |
| IncidentBot Team | 49 USD | 490 USD | Adds roles, unlimited schedules, postmortem drafts, reports |
| IncidentBot Business | 99 USD | 990 USD | Adds service catalog, workflow automation, SSO/SAML, audit log |
Detection and SOAR are quoted separately, usually by data volume, endpoints or workflow runs, so ask each vendor for a number at your volume rather than trusting a list price.
A security alert at 03:00 with and without a coordination layer
A SIEM rule flags a service account logging in from two countries within ten minutes. Without a rota the alert lands in a shared mailbox. The first analyst sees it at 07:30. With a rota, the alert pages the primary security engineer, escalates to the secondary after the acknowledgement timeout and opens a Slack incident channel with the alert attached. The engineer names an incident commander, sets a severity, and the timeline records who disabled the account and when. A status update for affected customers is drafted from that timeline, and the postmortem skeleton has the timestamps.
The point is time to first human response. The detection tool found the event in both cases. Only one case had a person working on it within minutes.
What a security on-call rota needs
- A primary and a secondary with a documented escalation timeout, tested with a real test page each quarter.
- Severity levels that decide who is woken. See incident severity levels for a workable scale.
- A single response channel and a named incident commander, covered in the incident response playbook.
- A written record that holds up in review. NIST's Computer Security Incident Handling Guide, SP 800-61 describes the phases and what to document.
- A tested way to tell stakeholders, internal or customer-facing, through a status page.
When IncidentBot fits and when it does not
IncidentBot suits security and IT teams of 5 to 40 people that already have detection and need paging, a response channel, a status page and a timeline in one seat price. It does not detect threats, it does not block or contain anything, and it is not a SOAR. We do not route live inbound phone calls and there is no native app: the web app installs on the phone with push notifications. See incident response for the coordination workflow and the incident management tools page for how the layers compare on cost. You can try a sample incident in the simulator with no account.
What are security incident management tools?
Security incident management tools detect, triage, coordinate and document security events. They split into SIEM and detection tools that find the event, SOAR tools that automate steps, and incident coordination tools that page responders and run the response. Most teams need the first and the last.
Is a SIEM an incident management tool?
Partly. A SIEM collects logs and raises alerts, which is detection. It does not usually run the on-call rota, open the response channel, keep the timeline or publish updates. Teams pair a SIEM with a paging and coordination tool.
What does a security incident response tool cost?
Detection platforms are usually quoted by data volume or endpoints. The coordination layer is priced per responder. For 10 responders, PagerDuty Professional is 210 USD a month and IncidentBot Starter is 240 USD at annual billing, status page included.
Do small security teams need SOAR?
Often not at first. SOAR pays off once the same playbook runs dozens of times a week. A team handling a few incidents a month gets more from a clear rota, severity levels, a timeline and a rehearsed communication step.