The access key is used to add devices to your Automox account.
The activity log tracks all automated and manual actions taken over a given period of time on the devices in your organization.
Advanced patch policies allow you to create custom patching configurations.
The API key is used to access the Automox API.
When you approve a patch, the software is applied on the policy's next scheduled update.
The Policy Status for a device will show as Compliant when all scheduled patches are installed and applicable reboots are complete.
Common Vulnerabilities and Exposures. Unique, common identifiers for publicly known information-security vulnerabilities in publicly released software packages.
Calculated based on the first time the package is available in the Automox customer base.
Devices that have been marked by the sysadmin user to not be shown on reports. A device will still be updated according to the policies assigned to the group that it is in.
failed update attempts
(formerly non-compliant) There are scheduled patches that have failed or have not yet been applied to a device.
A patch that has been marked by the sysadmin user to prevent a software package from being installed on a device/group of devices/global.
Device has successfully connected to Automox, but has not completed its first system scan
If a devices fails to patch for any reason, that device is identified as "needs attention". It might require a reboot to complete the patching process.
Action to turn off a device and reboot the OS.
When the Automox agent reviews the status of a device.
The interval indicates how often Automox re-inventories a device for hardware, software, system information, and available patches. The default is 24 hours.
A patch that will be installed automatically by a policy at the scheduled time.
(can be seen in Device > Export csv file)
The category label assigned to the level of threat to a vulnerability. Automox determines this based on several factors including CVSS values.
All available patches.
up to date
Devices that are fully compliant, do not need attention, and have no other pending status conditions.
Any change to a device that impacts its configuration and operation (install, uninstall, patch, apply worklet).
Use a worklet to perform any scriptable action on devices.