nano SIEM
SOAR

Triggers

Supported in:Self-hosted

Start a flow from a new alert, a case event, a triage verdict, a schedule, or a person, and narrow alert and case triggers with an event match.

Choose a trigger to decide when a flow runs. Only live flows fire on their trigger. Any flow that isn't archived can also run manually.

Trigger types

In the flow editor, pick a trigger under Triggers in the block palette, or select the trigger and change Trigger type in the inspector.

Triggeron valueFires whenEvent data in the run
Alert committedalertA new alert is createdflow_input.alert
Case eventcaseA case is created, closed, or reopened, its status changes, or it is set to or cleared from pendingflow_input.case
Case triage verdictcase.triage_verdictAI triage records a verdict on a caseflow_input.case, verdict, confidence, alert_ids, top_entities
SchedulescheduleA cron schedule comes dueNone
ManualmanualSomeone runs it from the flow editor or the APIOnly the inputs they provide

Through the API you can also use case_created, which fires only when a case is created.

One run per event

An event starts at most one run of each matching flow. If ten flows match an alert, nano starts ten runs, one for each flow. The same alert never starts a second run of the same flow. Each case event and each triage verdict is its own event.

During an alert storm, nano starts one run for every matching alert for every matching flow. Runs queue and drain at the executor's concurrency limit. See How runs behave under load.

Narrow a trigger with an event match

Alert, case, and triage verdict triggers take an optional Event match. An empty match fires on every event of that type. The match is checked against the trigger's event data before nano starts a run.

Match grammar

A match is one or more clauses joined by &&. Each clause is one of these:

ClauseExampleMeaning
flow_input.<path> = "value" (or ==)flow_input.alert.rule_name = "Suspicious PowerShell"The whole value equals the literal, ignoring case and surrounding spaces
flow_input.<path> in ["a", "b"]flow_input.case.status in ["open", "in_progress"]The value equals one of the literals
flow_input.alert.severity <op> "<severity>"flow_input.alert.severity >= "high"Severity comparison with >, >=, <, or <=
flow_input.case.severity <op> "<severity>"flow_input.case.severity > "medium"The same, on the case
flow_input.confidence <op> <number>flow_input.confidence >= 0.9Triage confidence between 0 and 1, with >, >=, <, <=, or =

Severities are ordered informational < low < medium < high < critical.

Rules:

  • At most 8 clauses, and at most 8,192 bytes.
  • || (or) isn't supported. For alternatives on one field, use in [...]. For "high or above", use >= "high".
  • A clause can read only flow_input fields.
  • Fail closed: a missing or unknown severity never matches an ordering, a missing confidence never matches a threshold, and a match nano can't parse never matches.

Examples:

flow_input.alert.severity >= "high" && flow_input.alert.entities.host in ["dc01", "dc02"]
flow_input.verdict = "malicious" && flow_input.confidence >= 0.8
flow_input.case.event = "closed"

Filter by severity and rule

Through the API, an alert trigger also takes severity (a list of severities) and rule_ids (at most 64 detection rule IDs). A case_created trigger takes severity. These filters are checked as the alert or case is written: when no live flow wants an event, it never enters the trigger queue. An event match is checked later, when nano reads the queue, so an event that fails only its match still takes a place in the queue.

{"on": "alert", "severity": ["high", "critical"], "rule_ids": ["<rule id>"], "match": "flow_input.alert.entities.user in [\"svc_backup\"]"}

Trigger payloads

Steps and event matches read the trigger's data under flow_input.

Alert

FieldContents
flow_input.alert.idAlert ID
flow_input.alert.rule_id, rule_nameThe detection rule
flow_input.alert.titleThe rule name. Without a rule, the alert kind followed by "alert", for example "Detection alert"
flow_input.alert.tagsThe detection rule's tags
flow_input.alert.severityAlert severity
flow_input.alert.kindAlert kind
flow_input.alert.created_atWhen the alert was created
flow_input.alert.entities.<name>The first value found in the alert's matched events for host, user, src_ip, dest_ip, process, command_line, hash, or domain, or null

nano resolves entities from OCSF fields by event class, for example actor.user.name on endpoint events. It reads the first 50 matched events and skips values longer than 1,024 bytes.

Case event

flow_input.case holds id, case_number, severity, status, priority, and event. event is created, closed, reopened, status_changed, pending_set, or pending_cleared. For a change, previous_status holds the status before it. Case payloads carry no title or description.

Case triage verdict

FieldContents
flow_input.caseid, case_number, status, severity
flow_input.verdictmalicious, suspicious, benign, or inconclusive
flow_input.confidence0 to 1, or null
flow_input.alert_idsUp to 100 alert IDs on the case
flow_input.top_entitiesUp to 10 case entities, each with type and value

Schedules

A schedule uses a 7-field cron in UTC: sec min hour day month weekday year. In the inspector, set Every (minutes) or type the cron directly. The inspector shows the next run time.

0 0 */6 * * * *
  • Runs must be at least 5 minutes apart. nano checks the next 8 fire times and refuses a cron that runs more often.
  • A schedule doesn't catch up. If nano was down or SOAR was off when a run was due, the next run is the next occurrence from now.
  • A scheduled run carries no event data.
  • If a live schedule flow can no longer start a run, for example because it no longer compiles or its owner lost a permission, nano returns it to draft.

Who a triggered run acts for

A triggered run acts for the person who last saved the flow, and nano checks that person's permissions before every step. It also checks that this person can see the alert or case that fired the trigger. If they can't, nano skips the flow for that event.

What's next

On this page