Forum Discussion
How could I exclude Vulnerability scanners from Session Tracking?
- Jan 10, 2017
Is it bad form to answer my own question?
Anyhow, using logging I discovered that the violation name wasn't matching correctly. Here is a rule that I've now deployed and tested.
when ASM_REQUEST_DONE { if {([ASM::violation names] contains "SESSION_AWARENESS" && [ASM::violation count] < 2 && [IP::addr [IP::client_addr] equals n.n.n.n/m])} { ASM::unblock } }
So to do what I am looking for there would need to be a new function that could both set the certificate and the private key in parallel.. So far I can only make it work by creating the profile by letting it inherit the default and then changing the default pool on the new profile to be the one that holds my private key and pass-phrase settings already with a certificate that has been created with that same key as a placeholder. (this works because I am using the same private key and pass-phrase for most profiles) Then I can change the certificate with no headache as the key is already set.
Hope that makes some sense. Picture a customer environment where I have many profiles and certificates for different domains.......
As per my exp, It is by design the VLAN name cannot rename once it is created, all other parameters and options of the VLAN can be changed. The name is used as a fixed reference point for the VLAN allowing it to be referenced, thus changing the name would lose the reference to this specific VLAN. Only option to modify vlan name in config file & reload it. Or as you mentioned, we have to delete and config again .
i am not tried or done that in device.
The recommended way is to delete the VLAN and re-create it again.
But You could go into the configuration files and change the name and reload the configuration from the files. But then you need to edit the name on all places where it is used. You can try if needed. but always best and better way is deleting the VLAN and re-create it again.