Integrations

Connect Stairwell to the tools you already run: EDR platforms that send it files, and the SIEM, SOAR, and case management systems that receive its findings.

Stairwell integrates in two directions, and it is worth knowing which one you are setting up before you start, because they solve different problems.

Inbound integrations send files to Stairwell. An EDR platform you already run has visibility into your endpoints, and Stairwell can take the files and detections it surfaces rather than requiring a second agent on every machine. This is how you get coverage without a new deployment.

Outbound integrations send Stairwell's findings somewhere else. A verdict, a rule match, or a report match becomes an event in your SIEM, a case in your case management system, or the trigger for a playbook in your automation platform. This is how Stairwell reaches the people and processes that already exist.

Most teams run at least one of each.

Which integrations are available?

IntegrationDirectionWhat it does
CrowdStrikeInboundIngests detections and suspicious file activity, and optionally retrieves the files themselves
SentinelOneInboundIngests threat detections and fetches the associated files
SplunkOutboundSends Stairwell events into Splunk as searchable data
Google SecOpsOutboundSends Stairwell events into Google SecOps, formerly Chronicle
ElasticOutboundSends Stairwell events into Elasticsearch
TheHiveOutboundCreates and updates cases from Stairwell findings
TinesOutboundDrives Tines stories from Stairwell events, and queries Stairwell from a story
Cortex XSOAR and XSIAMBothA full content pack: commands, playbooks, and an event feed
Generic SIEM or SOAROutboundA webhook, for anything without a purpose-built integration

Two more ways in and out are documented elsewhere, because they are not integrations with a named product. The REST APIs are what every integration above is built on and what you would use to write your own, and the MCP server exposes Stairwell to AI assistants that speak the Model Context Protocol.

Do I still need the forwarder?

Usually, yes, and this is the question worth settling early rather than discovering later.

An EDR integration gives you the files that platform noticed. The forwarder gives you the files that are there, whether anything noticed them or not, including everything already on disk before Stairwell existed in your environment. That difference is the whole premise of the product: the file nothing flagged is the one worth finding, and an integration that only forwards detections cannot hand you one.

There is also a throughput consideration. An EDR platform's data pipeline is built for its own purposes, and it may not sustain the rate needed for full file visibility, particularly on macOS and Linux. If extended coverage on those platforms matters to you, deploy the forwarder there and treat the integration as an addition.

The honest summary: use an integration to reach machines you cannot put a forwarder on, and use the forwarder where you can.

How do I set one up?

Inbound integrations are configured per environment, from the settings area:

  1. Select the settings icon.
  2. Open the Managed environments tab.
  3. Find the environment you are configuring, select (...) under Actions, and choose Manage integrations.
  4. Choose the integration to add.

Outbound integrations are configured on the receiving side, using a Stairwell auth token and, in most cases, an event notification that decides which findings are sent. Each page below covers its own specifics.

Every integration needs credentials from both sides, and several of them involve secrets that the other platform will show you exactly once. Read the whole page before you start clicking, and have somewhere to put a secret before you generate it.

What should I read next?


Did this page help you?