Fixing ASM signature updates after a short break
F5 ASM automatic signature updates are been failing from last 6 months and only been noticed now. Not bothered about why its failing. We are running version 12.1.0
1) As the signatures are not updated from last 4 months, we are very sceptical to update it now and all our policies are in blocking mode. We dont want the new signatures to block traffic after the successfull update. I read that it wont put the new signatures to blocking till the staging period ends. How do i make sure that this wont be enforced for next 30 days?
Will this enforce any change in existing signatures? Or it puts any changes to the existing signatures in staging as well?
How do i make sure we fix this issue without the new signatures causing trouble to our existing applications.
How do i get an import of the existing signature list from the problem device and compare it with the latest signature update which is available