Forum Discussion
3 Replies
Sort By
Options 1. Create copy of existing asm policy and customise per requirement. Now assign new asm policy to particular vip.
Options 2. Use iRule and bypass certain signature id but not sure the feasibility.
- Erik_NovakEmployee
You could create a Parent policy with attack signatures configured as optional. Use that parent policy as the basis for new policies. You can then disable the signature causing the FP, or leave it in staging, for that single policy only. The change will not affect the Parent policy or other policies based on the Parent.
- Chung_YuNimbostratus
Thanks guys, I have started to use a Parent policy as the base policy and build out the ASM on a per VIP basis.
Great input and thanks for validating some ops procedures for me.
REgards
Chung