Skip to main content

​
Overview

The Device42 integration enables ThreatAware to collect asset discovery and inventory management data from your Device42 environment, providing visibility into your complete IT asset inventory and device configurations.
Connection Method: API with Credentials Setup Time: 15 minutes Access Required: Device42 Administrator or API user account

​
Data collected

The Device42 integration provides:
  • Complete asset inventory
  • Device hardware and software information
  • Network configuration data
  • Device relationships and dependencies
  • Compliance and licensing information

​
Use cases

Asset Discovery

Discover and track all IT assets from your Device42 inventory

Inventory Management

Maintain accurate inventory data across your infrastructure

Dependency Mapping

Understand device relationships and dependencies

Compliance Verification

Verify asset compliance and generate inventory reports

​
Setup instructions

1

Access ThreatAware Dashboard

Log in to your ThreatAware instance and navigate to Settings > Systems.
2

Search for Device42

Use the search bar to find “Device42” in the integrations list.
3

Click Connect

Click Connect to open the connection popup window.
4

Identify Device42 API User

In your Device42 environment, log in as an administrator and navigate to UI Tools > Admins & Permissions > Administrators. Identify or create an account for API access. The account must have read access to the API.
For detailed information, refer to Device42’s API Documentation
5

Configure API Access Permissions

For the account you identified or created:
  • Deselect Staff Status to grant API access without UI access (optional but recommended)
  • This restricts the account to API-only operations
  • Ensure the account retains read permissions to the API
  • Save the configuration changes
6

Gather Connection Details

Collect the following information for ThreatAware:
  • API Token: Generate or obtain the API token from Device42 (if supported)
  • Username: The username for the API user
  • Password: The password for the API user
  • IP Address: The IP address or hostname of your Device42 instance
  • Port: Typically 443 for HTTPS (default is 8030 for HTTP)
Store these credentials securely. They provide access to your complete asset inventory.
7

Input Details into ThreatAware

Return to the ThreatAware connection popup and enter:
  • API Token: Your API token (if applicable)
  • Username: The API user’s username
  • Password: The API user’s password
  • IP Address: Your Device42 server IP or hostname
  • Port: 443 (HTTPS) or 8030 (HTTP)
  • Click Connect to establish the integration
8

Verify Connection

After connecting:
  • Check that the Integration Status shows as Active
  • Verify that device and asset data begins appearing in ThreatAware within 5-10 minutes
  • Check the last sync timestamp

​
Required credentials

Field Name: Device42 API Token Type: Password (encrypted) Description: API token for Device42 API authentication (if your environment uses token-based authentication)Some Device42 installations may use token authentication instead of username/password.
Field Name: Device42 Username Type: String Description: Username of the Device42 API user accountThis account must have read access to the Device42 API.
Field Name: Device42 Password Type: Password (encrypted) Description: Password for the Device42 API user account
Store this credential securely in your organisation’s password manager
Field Name: Device42 Server IP/Hostname Type: String Description: The IP address or fully qualified domain name of your Device42 instanceFormat: IP address (e.g., 192.168.1.100) or hostname (e.g., device42.company.com)
Field Name: Device42 Server Port Type: Integer Description: The port number for Device42 API accessDefault Values: 443 (HTTPS) or 8030 (HTTP)

​
Verification and testing

After setup, verify the integration is working correctly:
  1. Check Integration Status
    • Navigate to Settings > Systems in ThreatAware
    • Confirm Device42 shows Active status
    • Check the last sync timestamp
  2. Verify Data Collection
    • Wait 5-10 minutes for the initial data poll
    • Check for device and asset data in ThreatAware
    • Verify the asset list matches your Device42 inventory
  3. Test Queries
    • Create a test query to filter devices from Device42
    • Verify the asset information matches your expectations

​
Troubleshooting

Symptoms: Integration status shows authentication failureSolutions:
  • Verify the Username and Password are correct
  • Ensure credentials were entered without extra spaces
  • Test credentials by logging directly into Device42 (if Web UI is accessible)
  • Confirm the account is not locked or expired
  • Check that API access is enabled for the account
  • Contact your Device42 administrator if needed
Symptoms: Connection succeeds but no device or asset data appearsSolutions:
  • Verify the API account has read access to the Device42 API
  • Navigate to UI Tools > Admins & Permissions in Device42 to check permissions
  • Ensure the account is not restricted to specific organisational units
  • Review Device42’s API Documentation for required permissions
  • Create a new API account with full read permissions if needed
Symptoms: Connection timeout or “host unreachable” errorSolutions:
  • Verify the IP Address or hostname is correct
  • Confirm the Port matches your Device42 configuration (443 or 8030)
  • Test connectivity: ping <ip-address> from your network
  • Check firewall rules allow outbound connections to the Device42 port
  • Verify the Device42 server is online and accessible
  • Contact your network administrator for firewall verification
Symptoms: Integration shows active but no device or asset data appearsSolutions:
  • Verify there is asset data in Device42 to collect
  • Check that the API account has visibility to all devices
  • Ensure Device42 is actively discovering assets
  • Confirm API access is enabled and not rate-limited
  • Wait up to 30 minutes for initial data sync to complete
  • Review ThreatAware integration logs for errors
Symptoms: Integration fails to connect or times outSolutions:
  • Verify your Device42 instance is online and accessible
  • Check firewall rules allow outbound connections to Device42
  • Test connectivity to the IP/hostname and port in a terminal
  • Verify your internet connection is stable
  • Try connecting again after waiting a few minutes
  • Contact your Device42 administrator if the service is down
Symptoms: Error message indicates API access is disabledSolutions:
  • Verify API access is enabled for the user account in Device42
  • Navigate to UI Tools > Admins & Permissions > Administrators
  • Select the API user and verify API access is allowed
  • Check that the account role has API permissions
  • Enable API access for the account if it’s currently disabled
  • Review Device42 API documentation for permission requirements

​
Additional resources

Device42 API Documentation

Official Device42 API documentation for detailed API information and usage

ThreatAware Support

Contact ThreatAware support for integration assistance

​
Best practices

Credential Management
  • Create a dedicated API account specifically for ThreatAware
  • Document the API account in your organisation’s credential manager
  • Rotate passwords annually or per your security policy
  • Consider deselecting “Staff Status” for API-only access (increased security)
  • Monitor for authentication failures in ThreatAware regularly
Security Considerations
  • Grant only read permissions to the API account
  • Limit account scope to necessary organisational units if supported
  • Review Device42 audit logs to monitor API usage
  • Follow your organisation’s principle of least privilege
  • Store API credentials in a secure password manager
  • Ensure the Device42 server is behind a firewall when accessed externally