Bug ID 739900: All Policies are created with 3 new Signature Sets After Creation of a Policy using Application Ready Templates

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP ASM(all modules)

Fixed In:
14.1.0, 13.1.3

Opened: Aug 09, 2018

Severity: 3-Major

Symptoms

When a Security Policy is created using new versions of some Application Ready Templates, three new Signature Sets are created that are set to automatically be added to policies subsequently created.

Impact

Three new Signature Sets are created with the option 'Assign To Policy By Default' enabled. As a result, the system adds these Signature Sets to subsequently created policies. This may provide enforcement for unexpected or undesired Attack Signatures.

Conditions

A Security Policy is created using one of the following updated Application Ready Templates: * Drupal * Joomla * SAP Netweaver * Sharepoint * Wordpress

Workaround

To prevent the newly created signature being added to subsequently created policies, disable 'Assign To Policy By Default'. You can also remove the signatures from new policies after they have been created.

Fix Information

The Application Ready Templates now create the new signatures with the option 'Assign To Policy By Default' disabled, so they are no longer automatically added to subsequently created policies.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips