Device42
Device42 is an asset management tool that provides insights into your organization's hardware and software infrastructure. You can bring customer, device, and subnet data from Device42 into Brinqa to streamline risks associated with your data and strengthen your cybersecurity posture.
This document details the information you must provide for the connector to authenticate with Device42 and how to obtain that information from Device42. See create a data integration for step-by-step instructions on setting up the integration.
Required connection settings
When setting up a data integration, select Device42 from the Connector drop-down. If you cannot find the connector in the drop-down, make sure that you have installed it first. You must provide the following information to authenticate Device42 with Brinqa:
-
Server URL: The Device42 Server URL. The URL format is
https://<server_url>. -
Username and Password: The username and password associated with the Device42 account, which must have permissions to log in to the API server and return data.
Create a Device42 user
The Device42 user must have permissions to access the API server and return data. To create this user, follow these steps:
-
Log in to your organization's Device42 portal as an administrator.
-
Navigate to Tools > Administrators and click Add Local Admin.
-
Create the username and password for the new user.
Copy the new username and password into the Username and Password fields for Brinqa configuration.
-
Click Save.
-
Under Permissions, select Active to ensure the new user is active.
tipDisable Staff status. This ensures that the user can only access the API to return data, and not the Device42 web interface.
-
Click Save.
If you do not have permissions to create a new user, contact your Device42 administrator. For additional information, see Device42 documentation.
Additional settings
The Device42 connector contains additional options for configuration:
-
Page size: The maximum number of records to get per API request. The default setting is 100. It is not recommended to go over 100.
-
Parallel requests: The maximum number of parallel API requests. The default setting is 4.
-
Skip certificate verification: Select this option to allow for untrusted certificates.
Types of data to retrieve
The Device42 connector can retrieve the following types of data from the Device42 API:
Table 1: Data retrieved from Device42
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Customer | No | Not mapped |
| Device | Yes | Device |
| Subnet | Yes | Subnet |
The Device42 connector does not support operation options for the types of data it retrieves.
For detailed steps on how to view the data retrieved from Device42 in the Brinqa Platform, see How to view your data.
Attribute mappings
Click the tabs below to view the mappings between the source and the Brinqa data model attributes.
- Device
- Subnet
Table 2: Device attribute mappings
| Source Field Name | Maps to Attribute |
|---|---|
| aliases | Local variable |
| asset_no | Local variable |
| category | categories |
| core_thread | Local variable |
| cpu_count | Local variable |
| cpu_core | Local variable |
| cpu_speed | Local variable |
| customer | Local variable |
| device_sub_type | categories |
| device_type | categories, Local variable |
| hw_depth | Local variable |
| hw_model | Local variable |
| hw_model_id | Local variable |
| hw_size | Local variable |
| in_service | Local variable |
| ip_addresses | ipAddresses, publicIpAddresses, privateIpAddresses |
| is_it_blade_host | Local variable |
| is_it_switch | Local variable |
| is_it_virtual_host | Local variable |
| last_updated | sourceLastModified |
| mac_addresses | macAddresses |
| manufacturer | manufacturer |
| name | name |
| non_auth_aliases | Local variable |
| notes | Local variable |
| os | os |
| ram | Local variable |
| serial_no | serialNumber |
| service_level | Local variable |
| SYS_ID | uid |
| tags | tags |
| ucs_manager | Local variable |
| uuid | Local variable |
| virtual_host_name | hostNames |
Table 3: Subnet attribute mappings
| Source Field Name | Maps to Attribute |
|---|---|
| allocated | Local variable |
| allow_broadcast_address | Local variable |
| allow_network_address | Local variable |
| assigned | Local variable |
| can_edit | Local variable |
| category_id | Local variable |
| category_name | categories |
| customer_id | Local variable |
| description | description |
| gateway | Local variable |
| mask_bits | Local variable |
| name | name |
| network | Local variable |
| notes | Local variable |
| parent_subnet_id | Local variable |
| parent_vlan_id | Local variable |
| parent_vlan_name | Local variable |
| parent_vlan_number | Local variable |
| range_begin | Local variable |
| range_end | Local variable |
| service_level | Local variable |
| SYS_ID | uid |
| tags | tags |
| vrf_group_id | Local variable |
| vrf_group_name | Local variable |
Local variable indicates that the field is processed within a specific context, such as a particular workflow or calculation. Unlike other attributes, local variables aren't mapped to the unified data models. They only exist on the source data model.
APIs
The Device42 connector uses the Device42 REST API v1. Specifically, it uses the following endpoints:
Table 4: Device42 REST API Endpoints
| Connector Object | API Endpoint |
|---|---|
| Customer | GET /api/1.0/customers |
| Device | GET /api/1.0/devices/all |
| Subnet | GET /api/1.0/subnets |
Changelog
The Device42 connector has undergone the following changes:
3.0.1
- Added support for Data lifecycle management to the Device object.
3.0.0
- Initial Integration+ release.