Configure synchronization

Set the desired global synchronization interval for the in-scope sensor. Configuration is defined on the parent sensor; synchronization starts at child sensors and flows upstream.

Each and every sync takes place following a notification message sent by the child sensor, stating that the child sensor is ready to synchronize data to its parent. The notification messages act as global synchronization settings, working together with the following settings as well.

Note: In a multi-level deployment (e.g., one with root CMC, local CMC, and Guardian), the setting must be applied at each parent level (e.g., at the root CMC as well as at the local CMC).

Set the desired interval between DB synchronizations for the in-scope sensor. Configuration is done on the parent sensor; synchronization starts at child sensors and flows upstream. The setting applies to each DB element subject to synchronization (e.g., Alerts, Assets, Audit logs, and Health logs). As the interval expires, the DB entries are synchronized at the next notification message.

Note: In a multi-level deployment (e.g., one with root CMC, local CMC, and Guardian), if the setting is applicable, it must be applied at each parent level (e.g., at the root CMC as well as at the local CMC).

• interval_seconds: the number of seconds between DB synchronizations (default: 60). This parameter only makes sense when set higher than the global synchronization interval.

Set the desired interval between filesystem synchronizations for the sensor in scope, from its child sensors. The setting applies to each filesystem element subject to synchronization (e.g., nodes, links, and variables). As the interval expires, the filesystem entries are synchronized at the next notification message. In case the CMC is All-In-One, this interval will be used as default value for the Set the configurations merge interval.

Note: In a multi-level deployment (e.g., one with root CMC, local CMC, and Guardian), if the setting is applicable, it must be applied at each parent level (e.g., at the root CMC as well as at the local CMC).

• interval_seconds: the number of seconds between filesystem synchronizations (default: 10800 [3 hours] if the CMC is multi-context, 720 (12 minutes) if the CMC is All-In-One). This parameter only makes sense when set higher than the global synchronization interval.

Set the desired interval between binary files synchronizations for the sensor in scope, from its child sensors. The setting applies to each binary file element subject to synchronization (e.g., PDF reports). As the interval expires, the binary file entries are synchronized at the next notification message.

Note: In a multi-level deployment (e.g., one with root CMC, local CMC, and Guardian), if the setting is applicable, it must be applied at each parent level (e.g., at the root CMC as well as at the local CMC).

Set whether to synchronize all alerts from the child sensors to the in-scope parent sensor (false), or to synchronize only visible alerts (as defined in the Security Profile) (true). Default: false.

Note: In a multi-level deployment (e.g., one with root CMC, local CMC, and Guardian), if the setting is applicable, it must be applied at each parent level (e.g., at the root CMC as well as at the local CMC).

Set the desired execution policy for the alert rules.

Note: In a multi-level deployment (e.g., one with root CMC, local CMC, and Guardian), if the setting is applicable, it must be applied at each parent level (e.g., at the root CMC as well as at the local CMC).

Periodically, CMC All-In-One merge all the filesystem elements received by the connected Guardians. This operation strictly depends on the filesystem synchronization. It is possible to define a custom interval, however it is suggested to specify a similar value as the one set for the filesystem synchronization.

Note: In a multi-level deployment (e.g., one with root CMC, local CMC, and Guardian), if the setting is applicable, it must be applied at each parent level (e.g., at the root CMC as well as at the local CMC).

Enable this feature to avoid potential database deadlocks on assets. This option shall be applied on mid-level CMC if the bulk asset synchronization is not enabled.

Note: This option applies only on the CMC it is configured on. It is enabled by default.