Objective
To explain how Automox Vulnerability Sync matches imported vulnerability scan data (from CSV files or third-party integrations) to existing devices managed within the Automox platform.
Overview
When importing external vulnerability scan reports into Automox via Vulnerability Sync, the system correlates vulnerability findings with managed endpoints to present actionable remediation data. This mapping relies on matching device identity attributes between the source report and the Automox console.
Device Matching Mechanism
Hostname Correlation: Automox evaluates the list of imported device records in the CSV or API payload by Hostname. It compares each entry against the system hostnames of active devices registered in your Automox organization.
Exact Match Requirement: A device must exist in both the imported vulnerability report and your active Automox device inventory.
Unmatched Devices: If an imported device hostname cannot be matched to an active Automox endpoint, the vulnerability findings for that device will be skipped during import and will not display in the Vulnerability Sync dashboard.
Troubleshooting Device Match Failures
If expected CVEs or devices do not appear after completing a Vulnerability Sync import, verify the following:
1.Verify Hostname Naming Conventions:
Ensure the device names in your vulnerability scanner export match the system hostnames reported in the Automox console (e.g., check for fully qualified domain names host.domain.com versus short hostnames host).
2.Confirm Automox Agent Status:
Verify that the target endpoint has the Automox Agent installed and is actively checking in to the console.
3.Re-upload or Sync Import File:
If hostnames were corrected in your source scanner or Automox console, re-import the CSV file or trigger a fresh Vulnerability Sync integration run.