Understanding ControlUp Compliance Update Latency and Best Practices for Timely Patching
When organizations use ControlUp for Compliance to monitor and manage application updates, a common question arises regarding how quickly updates, such as security patches for applications like Google Chrome, become available through the platform’s compliance module. This is particularly important when timely patching is critical to address vulnerabilities identified by CVEs.
The update availability process in ControlUp for Compliance involves several stages. First, a new application version must be included in the patch catalog, which is derived from a third-party patch feed. The speed at which a new version appears in this feed varies by application vendor and release and is outside ControlUp’s direct control. For major browsers like Chrome, this step is typically quick but not guaranteed within a specific timeline.
Once the patch feed updates, ControlUp scans it every three hours to update the catalog. The tenant then checks for a catalog update approximately every hour, resulting in roughly a four-hour delay on ControlUp’s side before the tenant receives the latest version information. After that, devices report their compliance status based on their scanning schedule, meaning the frequency with which devices scan for updates directly impacts how soon they reflect new versions. The installation or remediation of updates follows according to template settings, including remediation windows and any manual triggers from administrators.
For sensitive environments requiring rapid response, such as those impacted by CVEs, recommendations include increasing scan frequency to daily or more, configuring remediation windows to allow timely installations, and leveraging the ControlUp Content Delivery Network (CDN) with the “Allow CDN bypass for self-updating applications” option (available starting with agent version 1.6). This setting enables applications like Chrome to update directly from the vendor, speeding up patch delivery. Additionally, maintaining the application’s native auto-update functionality provides a primary defense layer, with ControlUp Compliance providing oversight to catch devices where auto-update failed.
In practice, new Chrome updates have been observed to appear in Compliance the day after a vendor’s release, although this example should not be considered a guaranteed SLA due to variations in vendor feeds and catalog processing times. Windows patching follows a similar cadence, typically aligned with Microsoft’s Patch Tuesday schedule, and similarly may take up to three days to reflect in the catalog after release.
Further details on scheduling scans and managing templates in ControlUp for Compliance are available in the official documentation here: https://support.controlup.com/docs/controlup-for-compliance Read the entire article here...


