Forum Discussion

T-Pltn0001_3316's avatar
T-Pltn0001_3316
Icon for Nimbostratus rankNimbostratus
Oct 16, 2017

Enabling custom attack signature only on one security policy

Hello Everyone,

 

We have two dozens of security policies on our F5 ASM. Frequently we need to create application specific attack signature, however when we do it, new signature is set to Enabled on all remaining security policies. It takes between half an hour and hour to go into all remaining policies and disable this new signature. As you imagine this is very cumbersome and time wasting process.

 

Do you have any workaround to recommend?

 

By the way, we are running 11.6.1.

 

Thank you.

 

1 Reply

  • Simply don't assign the newly created user-defined signature to any systems/technology!

     

    Once you have the attack signature in its own own custom signature set you can easily assign/unassign your App1/App2 signature sets from individual policies