How to Rename an ASM Policy

A few comments in regards to modifying ASM policy names in the /config/bigip.conf file, as mentioned by cjunior.

This would be the fastest option, but you must be aware that this procedure involves an impact. As you load the modified bigip.conf file, your ASM policy with a new name will be de-attached from the Virtual Server and will be moved to Inactive Policies list. If you take this approach, you must be quick to manually re-activate your modified Policy and attach it to a relevant Virtual Server. There will be a small window of impact where your application is not protected by ASM. In any case, the prodecure is viable when working with non-production policies.

If you want to modify the name of an ASM policy without any impact to production traffic, you can use the procedure as descrived by blwavg. An equally good option would be defining your current Policy as Template, and then using it to create a new Policy with the desired name.