Synchronization with Cloud: configuring the moving rule

Expand all | Collapse all

During the Configure cloud environment operation, the Synchronize with Cloud rule is created automatically. This rule allows you to automatically move devices detected in each poll from the Unassigned devices group to the Managed devices\Cloud group, to make these devices available for centralized management. By default, the rule is active after it is created. You can disable, modify, or enforce the rule at any time.

To edit the properties of the Synchronize with Cloud rule and/or enforce the rule:

1. In the main menu, go to Discovery & deployment → Deployment & assignment → Moving rules.

   This opens a list of moving rules.

2. In the list of moving rules, select Synchronize with cloud.

   This opens the rule properties window.

3. If necessary, specify the following settings in the Rule conditions tab, in the Cloud segments tab:
   • Device is in a cloud segment

     The rule only applies to devices that are in the selected cloud segment. Otherwise, the rule applies to all devices that have been discovered.

     By default, this option is selected.

   • Include child objects

     The rule applies to all devices in the selected segment and in all nested cloud subsections. Otherwise, the rule only applies to devices that are in the root segment.

     By default, this option is selected.

   • Move devices from nested objects to corresponding subgroups

     If this option is enabled, devices from nested objects are automatically moved to the subgroups that correspond to their structure.

     If this option is disabled, devices from nested objects are automatically moved to the root of the Cloud subgroup without any further branching.

     By default, this option is enabled.

   • Create subgroups corresponding to containers of newly detected devices

     If this option is enabled, when the structure of the Managed devices\Cloud group has no subgroups that will match the section containing the device, Kaspersky Security Center creates such subgroups. For example, if a new subnet is discovered during device discovery, a new group with the same name will be created under the Managed devices\Cloud group.

     If this option is disabled, Kaspersky Security Center does not create any new subgroups. For example, if a new subnet is discovered during network poll, a new group with the same name will not be created under the Managed devices\Cloud group, and the devices that are in that subnet will be moved into the Managed devices\Cloud group.

     By default, this option is enabled.

   • Delete subgroups for which no match is found in the cloud segments

     If this option is enabled, the application deletes from the Cloud group all the subgroups that do not match any existing cloud objects.

     If this option is disabled, subgroups that do not match any of the existing cloud objects are retained.

     By default, this option is enabled.

   If you enabled the Synchronize administration groups with cloud structure option when using the Configure cloud environment, the Synchronize with cloud rule is created with the Create subgroups corresponding to containers of newly detected devices and Delete subgroups for which no match is found in the cloud segments options enabled.

   If you did not enable the Synchronize administration groups with cloud structure option, the Synchronize with cloud rule is created with these options disabled (cleared). If your work with Kaspersky Security Center requires that the structure of subgroups in the Managed devices\Cloud subgroup matches the structure of cloud segments, enable the Create subgroups corresponding to containers of newly detected devices and Delete subgroups for which no match is found in the cloud segments options in the rule properties, and then enforce the rule.

4. In the Device discovered by using the API drop-down list, select one of the following values:
   • No. The device cannot be detected by using AWS, Azure, or Google API, that is, it is either outside the cloud environment, or it is in the cloud environment but it cannot be detected by using an API for some reason.
   • AWS. The device is discovered by using AWS API, that is, the device definitely is in the AWS cloud environment.
   • Azure. The device is discovered by using Azure API, that is, the device definitely is in the Azure cloud environment.
   • Google Cloud. The device is discovered by using Google API, that is, the device definitely is in the Google cloud environment.
   • No value. This criterion cannot be applied.
5. If necessary, set up other rule properties in the other sections.

The moving rule is configured.