Forum Discussion
Updating attack signatures (best practice)
Umm... The last incident was observed on 11.6.1 HF6. The signature got detected was "src http: (Parameter) (2)". However the old signature exist was "src http: (Parameter)" without (2).
The updated signature i.e. "src http: (Parameter) (2)" automatically took place and followed the ASM Policies' action i.e. Blocking.
So I think this needs to get verified.
Hello Folks,
So this is confirmed. When you update ASM Signatures, newly updated signatures will never placed into Staging, even you click on the checkbox of "Place updated signatures in staging", it won't place the signature into staging.
This has been validated with F5 btw! The fix should be released in version 12.X as per the last update from F5.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com