Incident Response Commander: AI Incident Lead
On Sale
$67.99
$67.99
Your AI incident lead, running the response in your team chat
It declares the incident, loads the right playbook, keeps the timeline, scopes with Wazuh and writes the post-incident report. Containment and IRIS escalation wait for your Approve click.
In an incident, the record is the first thing to fall apart
Today: the response lives in chat
- Findings and decisions scattered across threads
- Tasks and owners tracked from memory
- The report rebuilt by hand after it is over
With the Commander: one record
- Timeline, tasks, IOCs, hosts and phase, logged as you talk
- The right playbook loaded as tasks with due times
- The post-incident report built from the record
An incident commander that never loses the thread
- Declares the incident: Sets type and severity and loads one of 8 playbooks as a task list with due times
- Keeps the record: Timestamped timeline, tasks with owners, IOCs, affected hosts and accounts, and the phase. Stored in n8n Data Tables, not chat memory
- Scopes with Wazuh: "Where else did this IP, hash or user show up?" Alert counts, first and last seen, every agent involved and hosts not yet in the incident
- Threat intel: IPs, domains and hashes checked with VirusTotal, AlienVault OTX and AbuseIPDB
- Contains, with approval: Blocks an IP, disables a user or isolates a host through Wazuh Active Response, only after someone clicks Approve
- Stakeholder updates: Plain-language drafts on cadence: critical every hour, high every 4 hours, medium every 24 hours
- DFIR-IRIS escalation: Creates the case after approval, then pushes only what is new: IOCs, assets, timeline, tasks and status
- Post-incident report: A branded HTML report with the timeline, tasks, IOCs and time to contain, delivered in your chat
- Reminders: A schedule with no AI pages the team about overdue tasks, quiet incidents and updates that are due
One command, about ten minutes
- Install: Run one command on Linux, macOS or Windows. It deploys n8n too if you need it
- Connect: Add your AI model key, Wazuh and your chat app. Threat intel keys and DFIR-IRIS are optional
- Respond: Tell it what happened. It declares the incident and gives you the first tasks
Built to act only when you say so
- Facts come from tools: The model orchestrates and writes prose. Incident facts and reports come straight from the record
- Approve before anything runs: Containment and IRIS escalation both wait for an Approve click in chat
- Dry run by default: Containment ships with dry run on, so nothing is blocked until you switch it off
- Never contains on a guess: It proposes containment only with evidence and refuses internal IPs, protected IPs and protected accounts
- No raw queries: Chat text never reaches Wazuh as a raw query. Every filter is a typed clause
- Private IPs stay private: Internal addresses are never sent to threat-intel services or to IRIS
What you need
- n8n: n8n 2.34 or newer with Agents and Data Tables, or let the installer deploy it
- Wazuh: Wazuh 4.x indexer and manager API with read access. Active Response only if you enable containment
- Chat app: Telegram, Slack, Discord or Linear. A Telegram bot takes a minute with @BotFather
- AI model: An API key from any provider in the n8n Agent model picker
- Optional: DFIR-IRIS 2.4+ and free VirusTotal, OTX and AbuseIPDB keys
What you get
- 10 tool workflows plus the reminder schedule
- The agent with 12 skills: 8 playbooks, severity matrix, containment decision, stakeholder updates and the post-incident report
- One-command installer for Linux, macOS and Windows
- Setup guide and example conversations
- Single-organization commercial license
- 7-day money-back guarantee
Full details and a demo: neetrox.com/ai-agents/incident-response-commander