CB Defense: How Does the Staggered Update Randomization Window Setting Affect Signature Updates?
search cancel

CB Defense: How Does the Staggered Update Randomization Window Setting Affect Signature Updates?

book

Article ID: 287053

calendar_today

Updated On:

Products

Carbon Black Cloud Endpoint Standard (formerly Cb Defense)

Issue/Introduction

How does the "Staggered Update Randomization Window" policy setting affect the Sensor's signature update schedule?

Environment

  • CB Defense PSC Console: All versions
  • CB Defense PSC Sensor: 2.x.x.x and higher
  • Microsoft Windows: All supported versions

Resolution

  • The randomization window comes into play after the Local Scanner policy is first enabled, when the local scanner policy is updated, and after a machine is powered off for more than 10 hours
  • When these events occur, the first Signature update will run at a random time between 5 minutes and the value selected from the "Staggered Update Randomization Window" drop-down 

Additional Information

The Sensor will continue to update based on the "Frequency" policy setting until the next time the policy is updated or the machine powers off for more than ten hours