Symptoms

Template editors are allowed to pick a template for each individual template virtual server within the Security section of the template editing page.

Impact

You might discover that protection mode for the application is not what you expect. For example, it may show as not protected, even if the policy has 'Blocking' enabled for the hostnames of the app. Navigate to "Application Services" > "Security" in the application view, the following message is displayed: "Note: The following virtual-servers doesn't have a security policy attached to them: <name-of-virtual>"

Conditions

Navigate to a custom template with 1 or more virtual servers and click the Security menu. Select an ASM Policy for one of the virtuals and leave "None" for the other(s).

Workaround

Select the same ASM Policy for all virtual servers in the template.

Fix Information

None

Behavior Change