nano SIEM
SOAR

SOAR

Supported in:Self-hosted

Automate response with flows that run actions on your security tools, search your data, notify your team, and wait for a person to approve anything disruptive.

Use SOAR to automate your response to alerts and cases. A flow runs a sequence of steps: actions on your security tools, nPL searches, notifications, AI Judge questions, and approval gates. Flows start from an alert, a case event, a schedule, or a person.

What SOAR does

You want toUse
Run the same response every time a matching alert firesA flow with an alert trigger
Look up, contain, or suspend something in another toolA pack action on a connection
Check your own data before actingAn nPL search step
Ask an AI model to classify the evidenceA Judge step
Make sure a person signs off before a disruptive changeAn approval gate
Tell your teamAn email or webhook notification step

Every run is recorded with each step's inputs, outputs, and outcome, and every change to SOAR is written to the audit log. See Audit and troubleshooting.

How SOAR relates to cases, playbooks, and pivt

  • Cases. A run can be linked to a case. When a linked run finishes, nano adds one entry to the case wall with the flow name, run ID, and step results. The Case automation pane on a case shows that case's runs, waiting approvals, and entity actions. From v2.0.34, case steps let a flow open, update, tag and assign cases directly, through Cases and with the flow owner's permissions.
  • Playbooks. A playbook stays the plan analysts follow. On a playbook run, Queue automation sends the steps that map to an installed pack action to SOAR as one run. Every mapped step needs approval from another analyst. Steps that don't map stay manual.
  • pivt. On Flows, click Draft with pivt to describe a flow in plain words. pivt drafts it against your installed packs and opens the draft in the flow editor. pivt never saves, activates, or runs a flow, and it marks every step that changes something as needing approval.

Find SOAR in nano

When SOAR is on, an Automation section appears in the left navigation:

PageUse it to
RunsFollow runs, see each step's result, and cancel a run.
FlowsCreate, test, and activate flows.
ApprovalsApprove or reject steps that are waiting for a person.
CapabilitiesInstall action packs, set up connections, and run a single action.

SOAR settings are at Settings → SOAR (/settings/soar).

Turn SOAR on

SOAR is off on a new deployment. A license makes it available, and an administrator turns it on.

Open SOAR settings

Go to Settings → SOAR.

Enter a reason

Type a reason. nano records it in the audit log with the change.

Turn SOAR on

Click Turn SOAR on. The Automation section appears in the left navigation, and the pack updates, email, webhook endpoint, and private-network allowlist settings appear on the page.

The same page holds the AI Judge daily token budget. See AI Judge.

Turn SOAR off

Click Turn SOAR off and confirm. Turning SOAR off is a hard stop that keeps all history:

  • Queued, running, and waiting runs end as canceled.
  • Pending approvals expire.
  • Requests that were in flight are closed. If a request may already have reached the vendor, its step is marked ambiguous, so nano never repeats it on its own after you turn SOAR back on.
  • Scheduled flows lose their next run time.
  • Alert and case events waiting to start runs are discarded.

Set up notifications

Flows send email through your own SMTP relay and post to your existing notification channels. A flow names a destination by its name, never by an address or URL. All of these settings are on Settings → SOAR and need settings:system; each change asks for a reason and is audited.

  • Mail transport. Enter the SMTP host, port, TLS mode (STARTTLS (required) or Implicit TLS), username, From address, and password. Storing the password also needs credentials:use; nano keeps it in the credentials store and never shows it again.
  • Email recipients. Add each recipient with a name and an email address. Flows use the name.
  • Webhook endpoints. Give an endpoint name and pick a notification channel (generic webhook, Slack, Microsoft Teams, or PagerDuty).

Use the test send next to a recipient or endpoint to check delivery. Notification bodies are plain text: nano removes connection credentials and the relay password from every message, masks common token shapes, and refuses a message that still looks like it contains a secret. Notifications never carry raw events.

Permissions

SOAR has four permissions. Assign them to roles in Access control.

PermissionLets you
soar:viewSee packs, connections, flows, runs, and approvals.
soar:manageInstall packs, manage connections, and create, edit, activate, archive, and test flows.
soar:runRun a single action, run a flow manually, and cancel a run.
soar:approveApprove or reject a waiting step. Never one you requested.

Some tasks need more than a SOAR permission:

TaskAlso needs
Store or change connection credentialssoar:manage and credentials:use
Save a flowsoar:manage and soar:run, plus search:execute for search steps, melod:summarize for Judge steps, and cases:view, cases:comment and each step's case permission for case steps
Draft a flow with pivtsoar:manage and melod:chat
Change SOAR settings, notifications, or the private-network allowlistsettings:system (interactive sign-in)
Store the SMTP relay passwordsettings:system and credentials:use
Attach a run to a casecases:comment, and access to that case
Cancel a run linked to a casesoar:run, cases:view, and cases:comment
Queue playbook automationsoar:run, playbooks:run, cases:edit, cases:view, and cases:comment

Default role grants:

RoleSOAR permissions
Admin, and any role that holds settings:systemAll four
Editorsoar:view and soar:run
ReadOnlyNone

API keys don't get SOAR permissions automatically. An administrator must add them to a key's scope. A run that an API key starts is treated as automated: every action in it waits for a person to approve it.

nano checks these permissions again before every step of a run, not only when the run starts. If the person a run acts for loses a permission, or loses access to the case or data the run uses, the run stops.

What's next

On this page