Clarification on Automatic Client Updates and Rollback Capabilities for Endpoint Security E89.21

[zaryhu]

I was reviewing the E89.21 Windows Client release notes and noticed the introduction of the Automatic Client Updates feature:

"Introducing the Automatic Client Updates feature that ensures endpoints always stay up to date by automatically delivering the latest protections and improvements, eliminating the need for manual upgrade cycles and helping maintain continuous security."

I would appreciate some clarification on how this feature impacts change management and operational support for organizations using Check Point Endpoint Security.

Specifically:

• Does this mean that functionality changes to the Endpoint Security thick client can now be delivered automatically outside of the traditional upgrade process?
• If so, how are customers notified of changes that may affect user experience, security controls, or administrative workflows?
• Will release notes continue to be published for all client changes that are delivered through Automatic Client Updates, including minor feature modifications?
• Is there a mechanism available to delay, approve, or otherwise control deployment of these automatic updates prior to broad release?
• In the event that a newly introduced change causes operational issues or conflicts within our environment, what rollback options are available?
• Can organizations revert to a previous client version, or can individual automatic updates be withdrawn from endpoints?
• Are there any administrative controls available to disable or opt out of Automatic Client Updates if an organization requires formal testing and change approval processes before client modifications are introduced?

Our concern is ensuring that we maintain visibility into changes that affect endpoint functionality and that we have a documented rollback strategy should an update introduce unexpected issues in production.

Any guidance or documentation you can provide on these topics would be greatly appreciated.

Thank you,

Zac Hudson
Information Security Analyst