Device42

Asset Management

Overview

The Device42 Connector integrates with Device42, an IT asset management, IPAM, and data-center infrastructure management (DCIM) platform. It syncs inventory data from a Device42 appliance into Brinqa, covering physical and virtual devices, IP subnets, and customers (the business owners/tenants that devices and subnets are associated with). The connector reads paginated data over the Device42 REST API and maps it onto Brinqa's Unified Data Model (UDM) so devices, network ranges, and ownership context are available for downstream risk analysis.

Data retrieved from Device42

Connector Object	Required	Maps to Data Model
Device	Yes	Device
Subnet	Yes	Subnet
Customer	Yes	Customer

Model relationships

note

For detailed steps on how to view the data retrieved from Device42 in the Brinqa Platform, see How to view your data.

Setup

Connection settings

When setting up a data integration, select Device42 from the Connector dropdown and provide the following:

Setting	Required	Default	Description
Server URL	No	—	Device42 server URL
Username	No	—	Device42 api username
Password	No	—	Device42 api password
Page size	No	—	Maximum number of records to get per API request
Parallel requests	No	—	Maximum number of parallel API requests
SSL / TLS	No	—	Skip certificate verification

Authentication

Device42 uses HTTP Basic Authentication. The connector sends the configured username and password as a standard Authorization: Basic <base64(username:password)> header on every API request against the configured server URL. There is no separate token-exchange step; the credentials are presented directly on each call.

Connectivity Test Endpoint

The connector validates connectivity and credentials with a lightweight request:

Method	URL
GET	{url}/api/2.0/devices?limit=1

Request Headers

Header	Value
Authorization	Basic <base64(username:password)>
Accept	application/json

Sample Response

{
  "devices": [
    {
      "id": "64",
      "name": "wh-lab-sw-01 - Switch 1"
    }
  ],
  "total_count": "709",
  "limit": "1",
  "offset": "0"
}

Response Fields

Field	Description
devices	Array of device records on the current page.
total_count	Total number of records available.
limit	Page size used for the request.
offset	Zero-based starting index of the current page.

A successful (2xx) response confirms that the URL and Basic Auth credentials are valid. The same credentials are reused (no token caching) on every subsequent sync request.

Sync Behavior

The connector supports incremental (delta) syncs. It maintains a sync token between runs and applies it as an incremental timestamp filter, so each run re-processes only the records that changed after the previous sync. The initial run retrieves the complete data set; later runs are incremental. The specific timestamp field applied to each object is documented under that object's Sync Duration Parameter.

How to obtain Device42 credentials

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:

1. Log in to your organization's Device42 portal as an administrator.

2. Navigate to Tools > Administrators and click Add Local Admin.

3. Create the username and password for the new user.

   Copy the new username and password into the Username and Password fields for Brinqa configuration.

4. Click Save.

5. Under Permissions, select Active to ensure the new user is active.

Tip: Disable Staff status. This ensures that the user can only access the API to return data, and not the Device42 web interface.

6. Click Save.

Note: If you do not have permissions to create a new user, contact your Device42 administrator. For additional information, see Device42 documentation.

Data & mappings

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes:

Device

Source Field Name	SDM Attribute
Device constant + DeviceResource.category, DeviceResource.type, DeviceResource.device_sub_type	CATEGORIES
DeviceResource.aliases	ALIASES
DeviceResource.asset_no	ASSET_NO
DeviceResource.corethread	CORE_THREAD
DeviceResource.cpucore	CPU_CORE
DeviceResource.cpucount	CPU_COUNT
DeviceResource.cpuspeed	CPU_SPEED
DeviceResource.custom_fields[]	*<custom field>
DeviceResource.customer	CUSTOMER
DeviceResource.device_id	DEVICE_ID
DeviceResource.hw_depth	HW_DEPTH
DeviceResource.hw_model	HW_MODEL
DeviceResource.hw_model_id	HW_MODEL_ID
DeviceResource.hw_size	HW_SIZE
DeviceResource.id	UID
DeviceResource.id	NAME
DeviceResource.in_service	IN_SERVICE
DeviceResource.ip_addresses[].ip	IP_ADDRESSES
DeviceResource.ip_addresses[].ip	PRIVATE_IP_ADDRESSES
DeviceResource.ip_addresses[].ip	PUBLIC_IP_ADDRESSES
DeviceResource.is_it_blade_host	IS_IT_BLADE_HOST
DeviceResource.is_it_switch	IS_IT_SWITCH
DeviceResource.is_it_virtual_host	IS_IT_VIRTUAL_HOST
DeviceResource.last_updated	SOURCE_LAST_MODIFIED
DeviceResource.mac_addresses[].mac	MAC_ADDRESSES
DeviceResource.manufacturer	MANUFACTURER
DeviceResource.nonauthoritativealiases	NON_AUTH_ALIASES
DeviceResource.notes	NOTES
DeviceResource.os	OPERATING_SYSTEM
DeviceResource.ram	RAM
DeviceResource.serial_no	SERIAL_NUMBER
DeviceResource.service_level	SERVICE_LEVEL
DeviceResource.tags	TAGS
DeviceResource.type	DEVICE_TYPE
DeviceResource.ucs_manager	UCS_MANAGER
DeviceResource.uuid	UUID
DeviceResource.virtual_host_name	HOSTNAMES
Sync timestamp	LAST_CAPTURED

Subnet

Source Field Name	SDM Attribute
Network constant + SubnetResource.category_name	CATEGORIES
SubnetResource.allocated	ALLOCATED
SubnetResource.allow_broadcast_address	ALLOW_BROADCAST_ADDRESS
SubnetResource.allow_network_address	ALLOW_NETWORK_ADDRESS
SubnetResource.assigned	ASSIGNED
SubnetResource.can_edit	CAN_EDIT
SubnetResource.category_id	CATEGORY_ID
SubnetResource.custom_fields[]	*<custom field>
SubnetResource.customer_id	CUSTOMER_ID
SubnetResource.description	DESCRIPTION
SubnetResource.gateway	GATEWAY
SubnetResource.mask_bits	MASK_BITS
SubnetResource.network	NETWORK
SubnetResource.notes	NOTES
SubnetResource.parent_subnet_id	PARENT_SUBNET_ID
SubnetResource.parent_vlan_id	PARENT_VLAN_ID
SubnetResource.parent_vlan_name	PARENT_VLAN_NAME
SubnetResource.parent_vlan_number	PARENT_VLAN_NUMBER
SubnetResource.range_begin	RANGE_BEGIN
SubnetResource.range_end	RANGE_END
SubnetResource.service_level	SERVICE_LEVEL
SubnetResource.subnet_id	UID
SubnetResource.subnet_id then SubnetResource.name	NAME
SubnetResource.tags	TAGS
SubnetResource.vrf_group_id	VRF_GROUP_ID
SubnetResource.vrf_group_name	VRF_GROUP_NAME

Customer

Source Field Name	SDM Attribute
CustomerResource.contact_info	CONTACT_INFO
CustomerResource.custom_fields[]	*<custom field>
CustomerResource.id	UID
CustomerResource.id then CustomerResource.name	NAME
CustomerResource.manager	MANAGER
CustomerResource.notes	NOTES
CustomerResource.tags	TAGS

Operations & API

Operations & API

Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).

Device

Operation options

This object does not support any operation options.

Delta sync

Supported.

API

• Type: REST endpoint · Endpoint: GET /api/1.0/devices/all

Subnet

Operation options

This object does not support any operation options.

Delta sync

Supported.

API

• Type: REST endpoint · Endpoint: GET /api/1.0/subnets

Customer

Operation options

This object does not support any operation options.

Delta sync

Supported.

API

• Type: REST endpoint · Endpoint: GET /api/1.0/customers

Changelog

Changelog

The Device42 connector has undergone the following changes:

Version	Description	Migration Steps
3.0.1	New Features - Devices now track when they were last seen during a sync and are automatically transitioned through their lifecycle when they have not been observed for 30 days, helping keep your inventory accurate by surfacing stale or decommissioned devices. Improvements Dependency Upgrades Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform.	N/A
3.0.0	Overview The Device42 connector integrates with Device42 to synchronize asset inventory data, including devices, the customers they belong to, and the network subnets they reside on. Category: Asset Management Models	N/A