> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threataware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Device42

> Connect ThreatAware to Device42 for asset discovery and inventory management data

## 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.

<Info>
  **Connection Method**: API with Credentials
  **Setup Time**: 15 minutes
  **Access Required**: Device42 Administrator or API user account
</Info>

## 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

<CardGroup cols={2}>
  <Card title="Asset Discovery" icon="computer">
    Discover and track all IT assets from your Device42 inventory
  </Card>

  <Card title="Inventory Management" icon="boxes">
    Maintain accurate inventory data across your infrastructure
  </Card>

  <Card title="Dependency Mapping" icon="sitemap">
    Understand device relationships and dependencies
  </Card>

  <Card title="Compliance Verification" icon="clipboard-check">
    Verify asset compliance and generate inventory reports
  </Card>
</CardGroup>

## Setup instructions

<Steps>
  <Step title="Access ThreatAware Dashboard">
    Log in to your ThreatAware instance and navigate to **Settings** > **Systems**.
  </Step>

  <Step title="Search for Device42">
    Use the search bar to find "Device42" in the integrations list.
  </Step>

  <Step title="Click Connect">
    Click **Connect** to open the connection popup window.
  </Step>

  <Step title="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**.

    <Info>
      For detailed information, refer to [Device42's API Documentation](https://api.device42.com/)
    </Info>
  </Step>

  <Step title="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
  </Step>

  <Step title="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)

    <Warning>
      Store these credentials securely. They provide access to your complete asset inventory.
    </Warning>
  </Step>

  <Step title="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
  </Step>

  <Step title="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
  </Step>
</Steps>

## Required credentials

<AccordionGroup>
  <Accordion title="API Token" icon="key">
    **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.
  </Accordion>

  <Accordion title="Username" icon="user">
    **Field Name**: Device42 Username
    **Type**: String
    **Description**: Username of the Device42 API user account

    This account must have read access to the Device42 API.
  </Accordion>

  <Accordion title="Password" icon="lock">
    **Field Name**: Device42 Password
    **Type**: Password (encrypted)
    **Description**: Password for the Device42 API user account

    <Tip>
      Store this credential securely in your organisation's password manager
    </Tip>
  </Accordion>

  <Accordion title="IP Address" icon="globe">
    **Field Name**: Device42 Server IP/Hostname
    **Type**: String
    **Description**: The IP address or fully qualified domain name of your Device42 instance

    **Format**: IP address (e.g., `192.168.1.100`) or hostname (e.g., `device42.company.com`)
  </Accordion>

  <Accordion title="Port" icon="plug">
    **Field Name**: Device42 Server Port
    **Type**: Integer
    **Description**: The port number for Device42 API access

    **Default Values**: 443 (HTTPS) or 8030 (HTTP)
  </Accordion>
</AccordionGroup>

## 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

<AccordionGroup>
  <Accordion title="Invalid Credentials Error" icon="triangle-exclamation">
    **Symptoms**: Integration status shows authentication failure

    **Solutions**:

    * 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
  </Accordion>

  <Accordion title="Permission Issues" icon="ban">
    **Symptoms**: Connection succeeds but no device or asset data appears

    **Solutions**:

    * 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](https://api.device42.com/) for required permissions
    * Create a new API account with full read permissions if needed
  </Accordion>

  <Accordion title="Invalid IP Address or Port" icon="map-pin">
    **Symptoms**: Connection timeout or "host unreachable" error

    **Solutions**:

    * 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
  </Accordion>

  <Accordion title="No Asset Data After 10 Minutes" icon="database">
    **Symptoms**: Integration shows active but no device or asset data appears

    **Solutions**:

    * 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
  </Accordion>

  <Accordion title="Connection Timeout" icon="clock">
    **Symptoms**: Integration fails to connect or times out

    **Solutions**:

    * 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
  </Accordion>

  <Accordion title="API Access Denied" icon="lock-exclamation">
    **Symptoms**: Error message indicates API access is disabled

    **Solutions**:

    * 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
  </Accordion>
</AccordionGroup>

## Additional resources

<CardGroup cols={2}>
  <Card title="Device42 API Documentation" icon="book" href="https://api.device42.com/">
    Official Device42 API documentation for detailed API information and usage
  </Card>

  <Card title="ThreatAware Support" icon="life-ring" href="mailto:help@threataware.com">
    Contact ThreatAware support for integration assistance
  </Card>
</CardGroup>

## Best practices

<Tip>
  **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
</Tip>

<Tip>
  **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
</Tip>