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

# Dark Web ID

> Connect ThreatAware to Dark Web ID to track security posture and device inventory

## Overview

The Dark Web ID integration enables ThreatAware to collect data from Dark Web ID, providing visibility into your security posture and cyber asset management.

<Info>
  **Connection Method**: API
  **Setup Time**: 15-30 minutes
  **Access Required**: Administrator account with API permissions
</Info>

## Use cases

<CardGroup cols={2}>
  <Card title="Device & Asset Tracking" icon="computer">
    Monitor devices and assets managed by Dark Web ID
  </Card>

  <Card title="Security Compliance" icon="shield-check">
    Track security posture and compliance status
  </Card>

  <Card title="User & Access Management" icon="users">
    Identify users, roles, and access patterns
  </Card>

  <Card title="Threat Detection" icon="triangle-exclamation">
    Detect threats and vulnerabilities in real-time
  </Card>
</CardGroup>

## Setup instructions

<Steps>
  <Step title="Log In to ThreatAware">
    * Access your ThreatAware dashboard.
    * Navigate to **Settings** > **Systems**.
  </Step>

  <Step title="Search for Dark Web ID">
    * Use the search bar to find "Dark Web ID."
  </Step>

  <Step title="Initiate Connection">
    * Click on **Connect**. A pop-up window will appear with further instructions.
  </Step>

  <Step title="Enable API Access">
    * To enable access to the Dark Web ID API, contact their support. Follow this [link to request API access support.](https://support.idagent.com/hc/en-us/articles/360013615278-How-can-I-enable-API-access-for-ID-Agent-)
  </Step>

  <Step title="Admin Account Requirement">
    * An **Admin Account** is necessary to access the API. It is advisable to create a new admin account specifically for this purpose.
  </Step>

  <Step title="Whitelisted IP Address">
    * You will need to provide an **IP Address** to be whitelisted. Contact ThreatAware to obtain the necessary IP address.
  </Step>

  <Step title="Contact Dark Web ID Support">
    * Log in to the Dark Web ID portal and navigate to **Support**.
    * Furnish support with the **Admin Account** credentials and **IP Address** you have.
  </Step>

  <Step title="Enable API Access">
    * Once the API access has been confirmed by support, you may continue to the following steps in ThreatAware.
  </Step>

  <Step title="Enter Credentials and Domain Information">
    * Input the Admin Username into ThreatAware.
    * Input the Admin Password into ThreatAware.
    * Enter the associated Domains into ThreatAware.
  </Step>

  <Step title="Authorize Connection">
    * Click the **Authorize** button to complete the connection process.
  </Step>
</Steps>

## Data collected

The Dark Web ID integration provides:

* Device and asset information
* Security compliance and posture data
* User and access information
* System performance metrics
* Configuration and policy information

## Required credentials

To set up the Dark Web ID integration, you will need:

* **API Key or Token**: Obtain from Dark Web ID admin console
* **API Secret or Client Secret**: Keep this secure
* **API Endpoint URL**: The Dark Web ID API base URL
* **Service Account**: Admin account or dedicated integration user
* **Service Account Password**: Associated credentials

<Tip>
  Create a dedicated service account specifically for ThreatAware integration and store all credentials securely in your organisation's password manager.
</Tip>

## Verification and testing

After setup, verify the integration is working correctly:

1. **Check Integration Status**
   * Navigate to **Settings → Integrations** in ThreatAware
   * Confirm the integration shows **Active** status
   * Check the last sync timestamp

2. **Verify Data Collection**
   * Wait up to 60 minutes for the initial data collection
   * Verify data appears in device details or dashboards

3. **Test Queries**
   * Create a test query to filter data from this integration
   * Verify results match your expectations

## Troubleshooting

<AccordionGroup>
  <Accordion title="Connection Failed" icon="triangle-exclamation">
    **Symptoms**: Integration fails to connect or shows error

    **Solutions**:

    * Verify all credentials are correct and copied without extra spaces
    * Ensure the API endpoint URL is accessible from ThreatAware
    * Check firewall rules allow outbound HTTPS (port 443) to the API endpoint
    * Confirm API credentials have not expired
    * Verify the service account has necessary permissions
  </Accordion>

  <Accordion title="Authentication Failed" icon="lock">
    **Symptoms**: Invalid credentials error

    **Solutions**:

    * Double-check the API key and secret are correct
    * Verify the API credentials have not been revoked
    * Ensure you are using the correct API version
    * Check if IP whitelisting is required
    * Review admin logs for authentication failures
  </Accordion>

  <Accordion title="No Data Appearing" icon="database">
    **Symptoms**: Integration active but no data visible

    **Solutions**:

    * Wait 60 minutes for initial synchronization
    * Verify API credentials have read permissions
    * Check the service account can access required data
    * Ensure data exists in the source system
    * Review ThreatAware integration logs
  </Accordion>

  <Accordion title="Incomplete or Partial Data" icon="hourglass">
    **Symptoms**: Only some data is being collected

    **Solutions**:

    * Verify the service account permissions for all resources
    * Check for API rate limit issues
    * Review source system for data availability
    * Contact ThreatAware support if the issue persists
  </Accordion>
</AccordionGroup>

## Best practices

<Tip>
  **Security Considerations**

  * Create a dedicated service account specifically for the ThreatAware integration
  * Use read-only API permissions (never grant write access)
  * Store credentials securely in your organisation's password manager
  * Rotate API credentials annually or per your security policy
  * Monitor authentication failures and API usage regularly
  * Review and audit integration activity periodically
  * Enable multi-factor authentication on the service account if available
  * Restrict the service account to only necessary resources and permissions
</Tip>