Skip to main content

Connect incident.io to Crush

Give Crush governed access to incident.io’s 154 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add incident.io to Crush in four steps

Admins approve the server once. Everyone in Crush then gets it through the same governed connection.

  1. 1

    Approve incident.io in Runlayer

    Add incident.io from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Crush to Runlayer

    Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches incident.io’s 154 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Crush setup guide
  3. 3

    Sign in to incident.io

    Sign in the way incident.io requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use incident.io from Crush

    incident.io’s approved tools appear in Crush. Every call is checked against policy and recorded.

Tools

154 incident.io tools in Crush

Runlayer policy decides which of these Crush users can call. 26 read data only and 9 can change or delete data.

  • Action convert

    Convert an incident action into a follow-up.

  • Create action

    Create an action on an incident.

  • Delete action

    Delete an incident action.

  • List action

    List incident actions with optional filters and pagination.

  • Update action

    Update an existing incident action.

  • Alert attach

    Attach an existing alert to an incident, marking it as related.

  • Alert create incident

    Declare a new incident for one or more alerts, attaching them to it as related.

  • Alert detach

    Detach an alert from an incident, marking it as unrelated.

See all 154 incident.io tools

Control

What Runlayer can see and stop in Crush

Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.

  • Gateway policy (available)

    Every incident.io call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination