Skip to main content

Device42

Visualize Device42 users and devices and monitor changes through queries and alerts.

Installation​

The Device42 integration supports two authentication schemes: Basic authentication with a Device42 username and password, and Token authentication with a Device42 API Client. In either case, Device42 enforces role-based security: the account's effective access comes from the role granted to its Admin Group, so grant only the read permissions the integration needs.

Configuration in Device42​

Before configuring the integration in JupiterOne, create the credential in Device42 and grant it read access to devices and end users.

Create a read-only Admin Group​

  1. In the Device42 Console, navigate to Tools > Admin Groups.
  2. Click Create and select only the read permissions the integration needs, including access to Devices and End Users.
  3. Click Save.

Create the account​

For Basic authentication, create a Device42 user:

  1. Navigate to Tools > Admins & Permissions > Administrators.
  2. Click Create to add a local user. Create a username and password, and save these for the integration configuration in JupiterOne.
  3. Under Permissions, assign the read-only Admin Group you created.
  4. Make sure the Superuser Status checkbox is unchecked before saving.
  5. Click Save.
note

To let the account use the API but not the Device42 UI, deselect Staff Status for the user.

For Token authentication, a Device42 administrator creates an API Client. The API Client's Client key and Client Secret key are used to request a Bearer token. The API Client proxies a Device42 user and inherits that user's role, so apply the same read-only Admin Group to the proxied user.

info

Refer to Device42's role-based access documentation for additional assistance assigning permissions, and Device42's documentation on adding an Active Directory administrator for adding AD users.

Configuration in JupiterOne​

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

Creating an instance requires the following:

  • The Account Name used to identify the Device42 account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • A Base URL, the hostname for your Device42 instance.

  • For Basic authentication, the Device42 Username and Password for the Device42 user used to integrate with JupiterOne.

  • For Token authentication, the Device42 Client Key and Device42 Client Secret Key for the API Client used to integrate with JupiterOne.

  • Optionally, Disable TLS Verification. When enabled, the integration does not verify the Device42 server's TLS certificate. This is not recommended; if possible, install a valid TLS certificate on the Device42 server instead.

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

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.