Update compliance is not refreshed when adding a nested group to a compliance policy

Problem

A compliance policy is defined for a static System group or Update group. Another group is later added to the static group defined in the compliance policy. Compliance status is not refreshed for the systems or updates in the new, nested group.

Explanation

A System group or Update group can be added to a static group of the same type, but nested groups will not inherit the compliance policy of any parent group they are included in.

For example, if a compliance policy is made up of a static Update group that contains updates and other Update groups, only the updates of the group in the policy will be validated for compliance to the systems in the same policy. Anything within the nested Update group will not be considered for validation of the compliance policy.

Resolution

Create a separate compliance policy for nested System groups and Update groups.