This topic outlines the terminology, concepts, and functional requirements for the EB release and update process.
Netskope Enterprise Browser Release Cycle
As part of the product lifecycle, the EB team builds and releases new versions of the browser, based on the following:
- Security vulnerabilities and bugs are fixed and need to be delivered to end users in a timely manner spotted by the team or from Chromium upstream. The vulnerability is assigned by severity, and the EB team works to fix it and deploy it according to SLAs. Critical vulnerabilities are addressed immediately until the issue is fixed and deployed. Contact your Netskope admin to review your current SLAs.
- New internal and Chromium-related features are continuously developed and made available. These regular updates occur monthly. This lifecycle and timing is aligned with the Chromium Release Cycle and with our rebase strategy.
Installing and Updating Netskope Enterprise Browser
The installation and update experience is similar to any other Chromium browsers (including Chrome). Once the Enterprise Browser is installed, the updates happen automatically after some configured time and after users are notified. By default, our configuration forces the update after a window of time.
Installation Options
- License Management via Netskope UI
- MDM
- API
Update Process
EB instances regularly make requests to Netskope services to verify the availability of new versions for the corresponding platforms (e.g. Windows and MacOS).
The process of checking for a new release, downloading, and installing it when available, takes place in the background, without the user’s intervention.
Once downloaded, the new release is installed next to the existing installation of the browser. If the browser is not running, the new release immediately replaces the existing installation. If the browser is running, the new release will not replace the existing installation until the browser is relaunched, either by the user or via a forced relaunch of the browser.
Update User Notification
The end user is notified when new releases are installed and ready to use. Typically, they will see the following:
Menu Only Relaunch Notification
Recommended Relaunch notification
Required Relaunch Notification
Update Configuration
By default, the Enterprise Browser requires the following update configuration:
- All the new versions require the user to relaunch the browser within an hour of its installation.
- The browser will automatically restart within the hour if the user doesn’t relaunch the browser.