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

# Absolute

> Connect ThreatAware to Absolute to track and monitor managed devices and their security posture

## Overview

The Absolute integration enables ThreatAware to collect read-only data from your Absolute environment, providing visibility into managed devices and their security posture.

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

## Data collected

The Absolute integration provides:

* Managed device inventory
* Device security status
* Incident and threat detection data
* Compliance and recovery information

## Setup instructions

<Steps>
  <Step title="Log in to Absolute Console">
    Access your Absolute console with administrator credentials to generate API credentials.
  </Step>

  <Step title="Generate API Token and Secret Key">
    Create API credentials in the Absolute console:

    * Navigate to the API credentials section in your Absolute console
    * Follow the Absolute API documentation for symmetric encryption setup
    * Generate a new **API Token**
    * Generate a new **Secret Key**
    * If required, configure IP address restrictions for your ThreatAware server
    * Securely store both credentials

    <Warning>
      Keep your API Token and Secret Key secure. Treat them like passwords and never share in plain text.
    </Warning>
  </Step>

  <Step title="Determine Your Region">
    Identify your Absolute region based on your console URL:

    * If you access: `https://cc.absolute.com` -> Use region: `api`
    * If you access: `https://cc.us.absolute.com` -> Use region: `api.us`
    * If you access: `https://cc.eu2.absolute.com` -> Use region: `api.eu2`

    <Tip>
      Your region determines which API endpoint ThreatAware will connect to.
    </Tip>
  </Step>

  <Step title="Configure in ThreatAware">
    Complete the integration setup in ThreatAware:

    * Open ThreatAware and navigate to **Settings** > **Integrations**
    * Search for and select **Absolute**
    * Enter the required credentials:
      * **API Token**: The token generated in Absolute
      * **Secret Key**: The secret key generated in Absolute
      * **Region**: The region determined from your console URL
    * Click **Authorize** to establish the integration
  </Step>

  <Step title="Verify Connection">
    After connecting, verify the integration is working:

    * Check the **Integration Status** to confirm it shows **Active**
    * Wait for the initial data sync (typically within 1 hour)
    * Verify Absolute device data appears in ThreatAware
  </Step>
</Steps>

## Required credentials

<AccordionGroup>
  <Accordion title="API Token" icon="key">
    **Field Name**: Absolute API Token
    **Type**: String
    **Description**: The API token generated in your Absolute console
  </Accordion>

  <Accordion title="Secret Key" icon="lock">
    **Field Name**: Absolute Secret Key
    **Type**: Password (encrypted)
    **Description**: The secret key associated with your API token

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

  <Accordion title="Region" icon="globe">
    **Field Name**: Absolute Region
    **Type**: String
    **Description**: The API endpoint region for your Absolute instance

    **Valid Values**:

    * `api` (for [https://cc.absolute.com](https://cc.absolute.com))
    * `api.us` (for [https://cc.us.absolute.com](https://cc.us.absolute.com))
    * `api.eu2` (for [https://cc.eu2.absolute.com](https://cc.eu2.absolute.com))
  </Accordion>
</AccordionGroup>

## Verification and troubleshooting

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

    **Solutions**:

    * Verify the **API Token** and **Secret Key** are correct
    * Ensure credentials were copied without extra spaces
    * Confirm the credentials have not expired in Absolute
    * Check that API access is enabled for your account
  </Accordion>

  <Accordion title="Invalid Region" icon="ban">
    **Symptoms**: Integration shows auth error or region mismatch

    **Solutions**:

    * Verify the **Region** matches your Absolute console URL
    * Double-check the region code (api, api.us, or api.eu2)
    * Confirm your Absolute instance is in the specified region
    * Contact Absolute support to confirm your instance region
  </Accordion>

  <Accordion title="IP Address Restrictions" icon="shield-halved">
    **Symptoms**: Connection fails with permission denied error

    **Solutions**:

    * Verify that ThreatAware's IP address is whitelisted in Absolute API settings
    * If IP restrictions are configured, ensure ThreatAware's outbound IP is in the allowed list
    * Contact your network administrator to confirm ThreatAware's IP address
    * Review firewall rules allow outbound HTTPS (443) to Absolute API endpoints
  </Accordion>

  <Accordion title="No Data After 1 Hour" icon="database">
    **Symptoms**: Integration shows active but no device data appears

    **Solutions**:

    * Verify there is device data in your Absolute console to collect
    * Check that the API token has read permissions for devices
    * Wait for the next sync cycle (typically hourly)
    * Review ThreatAware integration logs for detailed error messages
  </Accordion>
</AccordionGroup>

## Best practices

<Tip>
  **Credential Management**

  * Generate dedicated API credentials specifically for ThreatAware
  * Document credentials securely in your organisation's password manager
  * Rotate API credentials annually or per your security policy
  * Monitor for authentication failures in ThreatAware regularly
  * Revoke credentials immediately if they are compromised
</Tip>

<Tip>
  **Security Considerations**

  * Enable IP address restrictions in Absolute for ThreatAware's IP range
  * Use symmetric encryption for API authentication
  * Review Absolute API access logs periodically
  * Follow your organisation's least privilege principles
  * Disable old API credentials after rotation
</Tip>