Forum Discussion
Rajit_171155
Nimbostratus
NimbostratusBest practices for attack signature update/maintenance on ASM
We are looking for suggestions regarding best practices for attack signature update/maintenance on ASM in an university environment. We would like to have inputs for the following questions
How...
Thomas_Gobet_91
Cirrostratus
CirrostratusHi,
-
Attacks signatures should be updated as often as you can. You won't need to apply each version, it will depend on what you have to protect.
-
Again it depends on which security management you apply. To avoid some false positives, you have to change blocking signatures to staging mode. I usually do that, you'll avoid to be waked up at 3am for "nothing".
-
Yes you can do that. Each ASM policy is isolated from others. So on your QA policy, you can update a policy whereas on your prod one you don't apply the update.
Rajit_171155Nimbostratus
NimbostratusThank you for your response. I was wondering if there is any document that suggests the step by step process to push the attack signature updates per policy. We do not want to apply the attack signature updates gobally.
Thank you again!
