Skip to main content

Endpoint Software Configuration

The software configuration controls how endpoint sensors and browser extensions receive updates. Tune these settings to balance access to the latest capabilities with your organization’s change-management expectations.

Operating system sensor update policy​

Each platform—Windows, macOS, and Linux—has an independent update track. Use the dropdown for every OS to choose the policy that fits your rollout strategy:

  • Latest standard (default) keeps devices on the most recent generally available release. Cyberhaven applies the update automatically when a new build is qualified.
  • Previous standard holds devices on the prior standard release. Useful for short deferrals while validating the latest version.
  • Long Term Support (LTS) moves devices to the current LTS build and keeps them there until a new LTS release is ratified.
  • Version-specific entries (for example Version 25.09.01) pin devices to that build until you select a different option.
  • Off pauses automatic updates. Use sparingly—devices remain on their current build until you re-enable updates or assign a newer version.

The selected track is applied the next time each sensor checks in with the update service.

Browser extension updates​

Control the rollout cadence for browser extensions (Chrome, Edge, Firefox, Safari) from a single field.

  • Enter latest to keep extensions aligned with Cyberhaven’s most recent generally available build (default). Use this when your organization permits automatic updates or when you rely on Cyberhaven to distribute new releases.
  • Enter off to stop Cyberhaven-driven updates. Choose this if you host the extension internally or if change-management policies require you to stage updates through enterprise tooling such as Group Policy, Jamf, or Intune. With updates disabled, your deployment system must push new versions.
  • Enter an explicit semantic version number (major.minor.patch, for example 1.2.3) to pin the extension to that build. Pinning is only supported for self-hosted Chrome extensions. Edge, Firefox, and Safari respect only the latest or off setting, and they rely on your browser management policies if you need to control specific versions.

Update frequency​

Set how often devices check for new sensor builds and extension updates.

SettingDefaultRangeDescription
Auto updater interval60 minutes1 – 1,440 minutesDefines the polling cadence for update checks. Lower values accelerate rollouts; higher values reduce background traffic on constrained networks.

After changing the software configuration, publish it through a profile. Sensors apply the new policy on their next scheduled check-in, and you can track the update progress in Endpoint Management reporting.

See also: Cyberhaven Release Cadence and End-of-Support Policy