nano SIEM
SOAR

Actions and connections

Supported in:Self-hosted

Install signed action packs, connect them to your security tools with write-only credentials, run a single action, and control where SOAR may send requests.

Install an action pack and set up a connection to let flows act on your other security tools. A pack is a signed set of actions for one product, for example looking up a host or suspending a user. A connection holds the settings and credentials one pack uses to reach your account.

The action catalog

Go to Automation → Capabilities to see the signed catalog. Search by vendor, pack, or action, and filter by category or by whether a pack is installed. Open a pack to see each action's inputs, its Approval default, whether it is Safe to retry (idempotent), and its technical details: version, origin, license, validation, and Rate limit.

Every pack in the catalog is signed. nano verifies the signature, the content digest, and each pack's recorded test exchanges before it accepts a catalog. A tampered, foreign-signed, out-of-date, or rolled-back catalog is refused, and the catalog you already have stays in place.

How the catalog reaches your deployment

  • Connected installs receive the signed catalog through nano's content updates.
  • Air-gapped installs import a signed bundle. On Automation → Capabilities, click Import signed bundle and choose the file. See Air-gapped installs.

A bundle import accepts a catalog issued within the last 30 days by default. To change that window, set SOAR_OFFLINE_INDEX_MAX_AGE_DAYS (whole days, 1 to 90) on the API and jobs services. Any other value makes every import fail until you fix it. The catalog panel warns when your catalog was issued more than 7 days ago. Installed packs keep running, but withdrawals and pack updates published since then don't reach you until you import a newer bundle.

Install, upgrade, and remove packs

On a pack, click Install, Upgrade, or Remove pack. Each change is audited. Pending updates for installed packs are listed under Pack updates on Settings → SOAR.

  • When a pack release is withdrawn upstream, nano blocks new runs that use it.
  • When you upgrade a pack, runs that started on the earlier version fail with pack_version_changed when they reach that pack's step. Start them again.
  • When a pack is removed, flows that use it no longer compile, and their runs fail.

Action effects

Every action declares one effect. The effect decides whether a step needs approval and how it behaves in a test.

EffectExamplesApprovalIn a test with a real alert
readLook up a host, get a userNot needed, unless the step or pack requires itRuns against the vendor, if all its requests only read
writeAdd a tag, open a ticketNeeded by default. A flow step can allow automatic approval.Rendered, not sent
destructiveContain a host, suspend a userAlways needed. Can't be set to automatic.Rendered, not sent

See When a step needs approval.

Set up a connection

Open the connection form

On Automation → Capabilities, click Set up connection on an installed pack, or click New connection under Connections.

Fill in the settings

Pick the Pack, give the connection a Label, and fill in the pack's settings, such as its API host.

Enter the credentials

Fill in the fields under Credentials · write-only. nano encrypts them and never shows them again.

Save and test

Click Create connection, then Test connection. The test runs the pack's read-only test action against the vendor and stores the result. Authenticated and completed the read-only test action means the connection works.

How credentials are stored

  • Credentials are write-only. No page, API, or log returns them. When you edit a connection, a stored value shows Configured; type a new value to replace it.
  • nano encrypts each connection's credentials with AES-256-GCM, bound to that connection. A ciphertext copied to another connection can't be decrypted there.
  • nano refuses a label or setting that contains one of the connection's credentials.
  • Before a request goes out, nano refuses the step if its inputs contain a connection credential (secret_in_inputs). Credentials are removed from every recorded request and output.
  • Storing credentials needs credentials:use, the same permission nano requires everywhere it uses a secret on someone's behalf. Using a connection in a flow doesn't need it.

Which connection a step uses

A flow's action step names a connection, or uses Pack default. Pack default works only while the pack has exactly one connection. With two or more, runs that use the default are refused; pick a connection in the step instead.

When a run starts, nano pins the connection and the pack version it will use. If you edit the connection while the run is in progress, the run fails with connection_changed at that step. If you delete it, the run fails with connection_removed.

Delete a connection

Click Delete on a connection. nano checks that no queued or active run uses it, then destroys the stored credentials. Deleting works even while SOAR is off, so you can always dispose of credentials. Past runs keep their history.

Run a single action

Click Run action on a pack, or from a case's Case automation pane. Pick the connection and action, fill in the inputs, optionally attach the run to a case, and click Request run. Use Preview to see the request as a dry run first.

A single action follows the same approval rules as a flow step. A destructive action asks you to acknowledge it first and then waits for an approver. Accepted means queued, not succeeded.

Outbound safety

SOAR sends requests only to the hosts a pack declares, and only in ways you can predict:

  • Public addresses only. nano resolves each vendor host once for a run and checks every address. Private, loopback, link-local, metadata, and other reserved addresses are refused.
  • DNS pinning. nano connects only to the address it checked, so a DNS change during the run can't move the connection.
  • No redirects. Requests don't follow redirects and aren't retried by the transport. Retries are a flow decision.
  • Declared hosts only. Each pack lists the hosts its actions may reach, and nano also applies its own deny list.
  • Request budgets. Each pack declares requests per minute and per day, shown as Rate limit on the pack. Every request, including token requests, takes one unit. When the budget is used up, the step fails with rate_limited.
  • Concurrency. A process sends at most 16 vendor requests at once by default. See Limits and safety.

Reach a tool on your private network

Some packs are marked for self-managed tools that run on your own network. To let such a pack reach a private host, add it to the private-network allowlist. You need settings:system in an interactive sign-in.

Open the allowlist

Go to Settings → SOAR → Private-network allowlist.

Add the host

Enter the exact Host name the connection uses, the CIDRs it may resolve into, and the Port. CIDRs must be private ranges: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 100.64.0.0/10, or fc00::/7. If the tool uses a private certificate authority, paste it into Private CA (PEM, optional).

Save

Enter a reason and click Save allowlist.

Every address the host resolves to must sit inside one of the entry's CIDRs. Loopback, link-local, and metadata addresses stay refused. TLS still verifies the certificate for the host name. The allowlist holds at most 64 entries. Public vendor APIs need no entry, and packs not marked for self-managed tools can never use it.

Send vendor traffic through a proxy

To send SOAR vendor traffic through your forward proxy, set SOAR_EGRESS_PROXY_URL (http://[user:password@]host:port) on the API and jobs services. SOAR_EGRESS_PROXY_MODE chooses what nano asks the proxy to connect to:

ModeWhat the proxy seesWho checks the destination
pinned_ip (default)The IP address nano resolved and checkednano
hostnameThe host nameYour proxy. nano still applies the pack's host list and deny list, refuses literal IP destinations, and verifies TLS end to end.

An invalid proxy URL or mode stops all SOAR vendor traffic. nano never falls back to a direct connection. Packs for self-managed tools never use the proxy. See Self-run for the other proxy settings.

What's next

On this page