Fixing ASM signature updates after a short break

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?

Check what the policy Enforcement Readiness Period is, you can update this to 30 days. Bear in mind, when the period ends, the items do not automatically start blocking, you need to Enforce them manually. For any signatures not triggered there will be an "Enforce Ready" option to enforce them all. Any that did trigger violations need to be investigated, if they are true positives then enforce them (i.e. uncheck Staging box from the signature properties). If they are false positives then you need to make a policy change.

By default, only new Signatures are put in staging, however, there is a box you can check to add any updating signatures into staging too. Check the attack signature updating area of the GUI.

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

There should be a readme file for each signature file, if i recall, this will outline all those signatures added/updated.

Hope this helps,

N

Any item that can be in staging, like a new parameter, is governed by the enforcement readiness period.