Automox
Configure the Automox Endpoint Management integration with RAD Security to ingest device inventory and compliance findings, and trigger device remediation.
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.
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.
Prerequisites
Before you begin, ensure you have:
- 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
Understanding Integration Components
Step 1: Create an API Key in Automox
Sign in to the Automox Console
Log in to the Automox console with an account that has permission to manage API keys.
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.
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.
Locate Your Organization ID
Find your Organization ID in your Automox account or organization settings.
Exact console navigation and labels may vary across Automox versions. See the Automox developer documentation for the current steps to create an API key and locate your Organization ID.
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
Check Connection Status
- Navigate to Data Sources > Integrations > Endpoint Management in RAD Security
- Locate your Automox integration
- Verify the connection status shows as Connected
Your Automox integration is now configured! RAD Security will ingest device inventory and compliance findings from Automox on a scheduled basis.
What Data is Synced
Use Cases
Compliance Management Track device compliance gaps from discovery through remediation across your Automox fleet.
Asset Visibility Use managed-device inventory to understand your endpoint estate and reduce attack surface.
Threat Response Trigger Automox remediation on a non-compliant or compromised device directly from RAD.
RADBot Prioritization Leverage RADBot to prioritize Automox device findings by real-world impact.
Troubleshooting
Security Best Practices
Use a Service Account Create a dedicated API key for the RAD integration rather than tying it to a personal account.
Least Privilege Grant only the permissions required to read inventory and compliance, plus remediation if used.
Rotate Credentials Rotate the API token periodically according to your security policy.
Secure Secret Storage Store the API token in a secrets vault. Never commit it to version control.
Additional Resources
Automox Documentation
Official Automox developer documentation, including API keys
Endpoint Management Overview
Learn about RAD's endpoint management integrations