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

# Automox

> Configure the Automox Endpoint Management integration with RAD Security to ingest device inventory and compliance findings, and trigger device remediation.

# Automox Endpoint Management Integration Setup

This guide walks you through integrating Automox with RAD Security to ingest managed-device inventory and device compliance findings, and to trigger remediation on a device from RAD.

Automox is a cloud-native endpoint management platform. RAD Security connects to the Automox API using an API token and pulls device inventory and compliance posture on a scheduled basis to correlate them with your runtime, cloud, and Kubernetes security data.

<Info>
  **Read-only ingestion, with one write action:** RAD only reads device inventory and compliance from Automox. The single exception is **device remediation** — RAD can trigger a remediation action on a device through Automox. That action is RBAC-gated (requires tenant write permission) and recorded as an OCSF Device Control Finding.
</Info>

## Prerequisites

Before you begin, ensure you have:

<Check>
  * An Automox account with API access
  * Permission to create an API key in Automox
  * Your Automox **Organization ID**
  * Access to a RAD Security workspace with integration permissions
</Check>

## Understanding Integration Components

<AccordionGroup>
  <Accordion title="API Token" icon="key">
    RAD Security authenticates to the Automox API using an **API token (API key)** generated in your Automox account. The token is stored as a secret and never returned by RAD.
  </Accordion>

  <Accordion title="Organization ID" icon="building">
    The **Organization ID** scopes the integration to a single Automox organization and is used in the Automox API requests. You can find it in your Automox account settings.
  </Accordion>

  <Accordion title="API URL (optional)" icon="globe">
    The **API URL** override is optional. Leave it blank to use the default Automox API endpoint; set it only if Automox directs you to a non-default API host.
  </Accordion>

  <Accordion title="Scheduled Polling" icon="clock">
    RAD Security ingests Automox device inventory and compliance via scheduled polling. Data arrives on RAD's polling cadence rather than being pushed by Automox.
  </Accordion>
</AccordionGroup>

***

## Step 1: Create an API Key in Automox

<Steps>
  <Step title="Sign in to the Automox Console">
    Log in to the Automox console with an account that has permission to manage API keys.
  </Step>

  <Step title="Create an API Key">
    Open your account/profile settings and navigate to the **API Keys** section. Create a new API key and copy its value.

    <Warning>
      Copy the **API Key** immediately. The full value is typically shown only once at creation time. Store it securely in a password manager or secrets vault.
    </Warning>
  </Step>

  <Step title="Locate Your Organization ID">
    Find your **Organization ID** in your Automox account or organization settings.
  </Step>
</Steps>

<Note>
  Exact console navigation and labels may vary across Automox versions. See the [Automox developer documentation](https://developer.automox.com) for the current steps to create an API key and locate your Organization ID.
</Note>

***

## Configure in RAD Security

Navigate to your RAD Security workspace and configure the Automox integration with the following parameters:

### Required Parameters

| Parameter           | Required | Description                                                                 |
| ------------------- | -------- | --------------------------------------------------------------------------- |
| **API Token**       | Yes      | Automox API key used to authenticate API requests                           |
| **Organization ID** | Yes      | Automox organization identifier that scopes the integration                 |
| **API URL**         | No       | Optional override for the Automox API base URL; leave blank for the default |

***

## Verify Integration

<Steps>
  <Step title="Check Connection Status">
    1. Navigate to **Data Sources > Integrations > Endpoint Management** in RAD Security
    2. Locate your Automox integration
    3. Verify the connection status shows as **Connected**
  </Step>
</Steps>

<Check>
  Your Automox integration is now configured! RAD Security will ingest device inventory and compliance findings from Automox on a scheduled basis.
</Check>

## What Data is Synced

<AccordionGroup>
  <Accordion title="Device Inventory" icon="laptop">
    Managed devices, mapped to **OCSF Device Inventory Info (5001)** — hostname, OS, hardware, serial, owner, managed/compliant flags, risk, and first/last-seen timestamps.
  </Accordion>

  <Accordion title="Compliance Findings" icon="shield-exclamation">
    Device compliance posture, mapped to **OCSF Compliance Finding (2003)** and stored as security findings. Feeds unified posture analysis and RADBot.
  </Accordion>

  <Accordion title="Device Remediation" icon="screwdriver-wrench">
    The one write action — RAD can trigger an Automox remediation on a device. RBAC-gated (tenant write) and recorded as an **OCSF Device Control Finding**.
  </Accordion>
</AccordionGroup>

## Use Cases

<CardGroup cols={2}>
  <Card title="Compliance Management" icon="shield-check">
    Track device compliance gaps from discovery through remediation across your Automox fleet.
  </Card>

  <Card title="Asset Visibility" icon="laptop">
    Use managed-device inventory to understand your endpoint estate and reduce attack surface.
  </Card>

  <Card title="Threat Response" icon="screwdriver-wrench">
    Trigger Automox remediation on a non-compliant or compromised device directly from RAD.
  </Card>

  <Card title="RADBot Prioritization" icon="robot">
    Leverage RADBot to prioritize Automox device findings by real-world impact.
  </Card>
</CardGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Authentication Failed" icon="triangle-exclamation">
    **Possible causes:**

    * Incorrect API token
    * The API key was revoked or disabled in Automox

    **Solution:**

    * Verify the API token is copied correctly (no extra spaces)
    * Confirm the API key is still active in Automox
    * Regenerate the key in Automox and update it in RAD Security if needed
  </Accordion>

  <Accordion title="Empty Results" icon="inbox">
    **Possible causes:**

    * Incorrect Organization ID
    * The organization has no devices or compliance data in scope

    **Solution:**

    * Verify the **Organization ID** matches your Automox organization
    * Confirm devices exist in the Automox console for the configured organization
  </Accordion>

  <Accordion title="Remediation Action Rejected" icon="ban">
    **Possible causes:**

    * The calling user lacks tenant write permission in RAD Security
    * The API key lacks permission to run remediation in Automox

    **Solution:**

    * Confirm your RAD role grants tenant write
    * Confirm the Automox API key has the required remediation permissions
  </Accordion>
</AccordionGroup>

## Security Best Practices

<CardGroup cols={2}>
  <Card title="Use a Service Account" icon="user-gear">
    Create a dedicated API key for the RAD integration rather than tying it to a personal account.
  </Card>

  <Card title="Least Privilege" icon="shield-halved">
    Grant only the permissions required to read inventory and compliance, plus remediation if used.
  </Card>

  <Card title="Rotate Credentials" icon="rotate">
    Rotate the API token periodically according to your security policy.
  </Card>

  <Card title="Secure Secret Storage" icon="vault">
    Store the API token in a secrets vault. Never commit it to version control.
  </Card>
</CardGroup>

## Additional Resources

<CardGroup cols={2}>
  <Card title="Automox Documentation" icon="book" href="https://developer.automox.com">
    Official Automox developer documentation, including API keys
  </Card>

  <Card title="Endpoint Management Overview" icon="laptop-mobile" href="/rad-security/integrations/endpoint-management/overview">
    Learn about RAD's endpoint management integrations
  </Card>
</CardGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="Endpoint Management Integrations" icon="laptop-mobile" href="/rad-security/integrations/endpoint-management/overview">
    Explore other endpoint management integration options
  </Card>

  <Card title="Data Sources" icon="database" href="/rad-security/integrations/data-sources">
    Connect additional security data sources
  </Card>

  <Card title="RADBot" icon="robot" href="/rad-security/getting-started/radbot">
    Learn how RADBot helps prioritize findings
  </Card>
</CardGroup>