Select a policy in the list of policies and double-click the policy to open the Properties: <Policy name> window.
In the policy properties window, in the File Threat Protection section, select the additional protection profiles subsection.
A list of additional protection profiles will appear in the right part of the window. If you have not yet created additional protection profiles in this policy, the list of protection profiles is empty.
In the list of additional protection profiles, you can do the following:
Change the name of an additional protection profile by clicking the Rename button.
Edit the settings of the additional protection profile by clicking the Change button. The settings are edited in the Protection settings window. The additional protection profile settings are identical to the main protection profile settings. The new protection profile settings are applied after data is synchronized between Kaspersky Security Center and the SVMs.
Export the settings of an additional protection profile to a file by clicking the Export button. To save the settings of an additional protection profile, you need to specify the path to a file in JSON format. You can use previously saved settings when creating a new additional protection profile.
Delete the additional protection profile by clicking the Delete button. If the protection profile was assigned to virtual machines, the application will protect these virtual machines using the settings of the protection profile that was assigned to their parent object in the virtual infrastructure. If the parent object has been excluded from protection, the application does not protect such virtual machines.
If file protection settings are defined using NSX Vendor Templates / NSX Profile Configurations, protection profile removal will result in cancellation of mapping between the deleted protection profile and the NSX Vendor Template / NSX Profile Configuration. If you have not disabled the default protection profile, the NSX Vendor Template / NSX Profile Configuration will be automatically assigned the default protection profile. If you do not use the default protection profile, the virtual machines managed by NSX policies that use these NSX Vendor Templates / NSX Profile Configurations will be excluded from protection.