Axonius

Use the Axonius integration in Torq to ingest Axonius events and manage assets as part of your automated security workflows.

Trigger workflows with Axonius events

To ingest Axonius events in Torq, you need to create an Axonius trigger integration and use the generated webhook URL (Torq endpoint) to configure a Webhook integration in Axonius.

Create an Axonius trigger integration

Perform these steps in Torq.

1. Go to Integrations > Triggers.
2. Locate Orca and click Add.
3. Type a meaningful name for the integration instance and click Add.
4. (Optional) Add an authentication header. Make sure you use the same authentication header names and values as they are in Axonius. Axonius supports the following headers:
   1. user name
   2. password

Create a send to Webhook action in Axonius

See the Axonus documentation for instructions on how to create this action.

Create a test workflow

You'll create the workflow in Torq. The purpose of the test workflow is to confirm that events from Axonius are being sent to the webhook URL successfully.

1. Go to Workflows and click Create Workflow.
2. Type a meaningful name for the workflow, such as Axonius Events Test.
3. Click the trigger icon and select Axonius.

Use Axonius steps in a workflow

To use Axonius steps in Torq workflows, you have to create an Axonius steps integration, which requires an Axonius API key and secret.

Create an Axonius API key and secret

See the Axonius documentation for instructions on how to create an API key and secret.

Create an Axonius steps integration in Torq

Perform these steps in Torq. You'll need the API key and secret you created previously.

1. Go to Integrations > Steps.
2. Locate Axonius and click Add.
3. Type a meaningful name for the integration instance.
4. Enter the API key and secret that you generated in your Axonius tenant.
5. Click Add.

Use steps in a workflow

Axonius steps have several required input parameters and more optional input parameters. To view the optional parameters, click the gear icon in the step configuration window.

• BASE URL: the URL for your Axonius tenant.
• FIELDS: the fields to include in returned assets. If no fields are supplied, only minimal information is returned for the assets.
• FILTERS: a filter that you build using Query Wizard that's used when counting assets.
• INTEGRATION: the steps integration to use to execute the step, for example, axonius-steps .

Premade steps

• Get devices
• Get users