Kaspersky Security Center 13.1

Inheritance of policies and policy profiles

This section provides information about the hierarchy and inheritance of policies and policy profiles.

In this section

Hierarchy of policies

Policy profiles in a hierarchy of policies

How settings are implemented on a managed device

Page top
[Topic 165771]

Hierarchy of policies

If different devices need different settings, you can organize devices into administration groups.

You can specify a policy for a single administration group. Policy settings can be inherited. Inheritance means receiving policy settings values in subgroups (child groups) from a policy of a higher-level (parent) administration group.

Hereinafter, a policy for a parent group is also referred to as a parent policy. A policy for a subgroup (child group) is also referred to as a child policy.

By default, at least one managed devices group exists on Administration Server. If you want to create custom groups, they are created as subgroups (child groups) within the managed devices group.

Policies of the same application act on each other, according to a hierarchy of administration groups. Locked settings from a policy of a higher-level (parent) administration group will reassign policy settings values of a subgroup (see the figure below).

Unlocked parent policy settings can be reassigned and locked in the child policy. A user cannot change the parent and child policy settings, only the unlocked settings are available for reassignment.

Hierarchy of policies

Page top
[Topic 165770]

Policy profiles in a hierarchy of policies

Policy profiles have the following priority assignment conditions:

  • A profile's position in a policy profile list indicates its priority. You can change a policy profile priority. The highest position in a list indicates the highest priority (see the figure below).

    The Policy profile 1 has the highest priority, the Policy profile 100 has the lowest priority.

    Priority definition of a policy profile

  • Activation conditions of policy profiles do not depend on each other. Several policy profiles can be activated simultaneously. If several policy profiles affect the same setting, the device takes the setting value from the policy profile with the highest priority (see the figure below).

    Target device configuration fulfills the activation conditions of several policy profiles.

    Managed device configuration fulfills activation conditions of several policy profiles

Policy profiles in a hierarchy of inheritance

Policy profiles from different hierarchy level policies comply with the following conditions:

  • A lower-level policy inherits policy profiles from a higher-level policy. A policy profile inherited from a higher-level policy obtains higher priority than the original policy profile's level.
  • You cannot change a priority of an inherited policy profile (see the figure below).

    A child policy inherits the profiles of the parent policy. The inherited parent policy profiles obtain higher priority than the child policy profiles.

    Inheritance of policy profiles

Policy profiles with the same name

If there are two policies with the same names in different hierarchy levels, these policies function according to the following rules:

  • Locked settings and the profile activation condition of a higher-level policy profile changes the settings and profile activation condition of a lower-level policy profile (see the figure below).

    Profiles of the parent and child policies have the same name. Locked settings and the profile activation condition of the parent policy profile changes the settings and profile activation condition of the child policy profile.

    Child profile inherits settings values from a parent policy profile

  • Unlocked settings and the profile activation condition of a higher-level policy profile do not change the settings and profile activation condition of a lower-level policy profile.

See also:

Policy setup and propagation: Device-centric approach

Page top
[Topic 175793]

How settings are implemented on a managed device

Implementation of effective settings on a managed device can be described as follows:

  • The values of all settings that have not been locked are taken from the policy.
  • Then they are overwritten with the values of managed application settings.
  • And then the locked settings values from the effective policy are applied. Locked settings values change the values of unlocked effective settings.

See also:

About policies and policy profiles

About lock and locked settings

Hierarchy of policies

Policy profiles in a hierarchy of policies

Page top
[Topic 209754]