Clarification on Checkpoint LivePatch Package Availability Timeline After Repository Publication

[luiz_br]

I would like to better understand the expected timeline between the publication of a new package in the official Check Point repositories and its availability to customers through Check Point LivePatch/AutoUpdater.

As an example, the package BUNDLE_URGENT_SECURITY_UPDATE_R81_20_AUTOUPDATE Take 28, which is referenced in the following SK article (https://support.checkpoint.com/results/sk/sk185114) has not yet appeared in the list of available updates for our gateways through the AutoUpdater mechanism.

We observed a similar situation when BUNDLE_URGENT_SECURITY_UPDATE_R81_20_AUTOUPDATE Take 26 was released. In that case, several days passed between the publication of the package by Check Point and its availability through the automatic update process.

Given that Check Point LivePatch is intended to deliver security fixes and vulnerability mitigations in a timely manner, it would be very helpful to understand:

• What is the typical delay between a package being published in the official Check Point repositories and becoming available through LivePatch/AutoUpdater for customer gateways?
• Is the deployment performed in phases by region/country, platform group ?
• Are there any factors that can affect or delay the visibility of newly released packages in the AutoUpdater package list?

Understanding this process would help us better assess the exposure window between a security update release and its availability for automated deployment.

[CheckPointerXL]

Same question here