Skip to main content

Armis

The Armis integration adds comprehensive device visibility and threat detection capabilities. This integration enables JupiterOne users to better manage assets, assess risks, and respond to incidents more effectively by leveraging Armis's device insights.

Installation​

To install this integration, you will need to configure settings both within Armis and on JupiterOne. Before enabling in JupiterOne, ensure that you complete the setup within your Armis's account.

Configuration on Armis​

note

You will have to configure an API secret key in Armis so that the integration can make REST API calls to fetch data from Armis.

  1. Using a web browser, go to your Armis tenant (e.g. https://my-tenant.armis.com) and log in with your credentials.

  2. Click on Settings -> API Management

    Settings

  3. Click on the Create button

    Create Button

  4. You will get a message box with the newly created API Secret Key. Save the key in a safe place, you will need this to configure the integration in JupiterOne.

    Armis API Secret Key

Finalize in JupiterOne​

To install the Armis integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Armis. Click New Instance to begin configuring the integration.

Creating an integration instance requires the following:

  • Enter the Armis URL (e.g. https://<tenant>.armis.com)

  • Enter the Armis API Secret Key generated for use by JupiterOne.

  • Enter the account name by which you want to identify this Armis account in JupiterOne.

  • [Optional] Enter a description to help your team identify the integration.

  • [Optional] Select a polling interval that is sufficient for your monitoring requirements. You can leave this as DISABLED and manually execute the integration.

  • [Optional] Enter the Historical Days (any number greater than 0). The integration will ask Armis to return devices/alerts seen in the last few days. The Historical Days number will be used for this query. Higher number of days will result in more data ingested.

  • [Optional] Disable TLS Verification - Set this to true only if you have an on-prem Armis server that does not have a valid SSL certificate configured. For most cases this value should be false.

Click Create once all values are provided to finalize the integration.