12-Feb-2021 22:18
what is the best practice for ASM policy?
If I have unchecked "illegal parameter" from policy, is this risky? or we can mitigate this by doing sth.
19-Feb-2021 11:40
It depends on what you are trying to achieve... Could you provide a little bit more information about what issue you trying to solve by disabling this violation?
20-Feb-2021 09:49
I have dynamic parameters, so each time asm block the parameter. That's why I'm asking if i have unchecked this violation is it risky ?
note that all parameter value with meta characters will be blocked.
so how illegal parameters affect website security?
22-Feb-2021 21:34
There is no 100% correct answer is it risky or not - it depends on application.
If you know all parameters, which are allowed in your app, then defining such list and forbid all other parameter will be a good protection.
The more strict configuration you define, the better protection you will get.
As I see, there are several ways how you can avoid block by "Illegal parameter" violation without disabling it:
Thanks, Ivan
24-Feb-2021 22:22
If I have this parameters:
and so on,
I have create one parameter Terms[*].Groups , but the new parameter ex Terms[4].Groups does't match the wildcard why?
24-Feb-2021 22:41
Hello,
This happens because you have special characters in name of wildcard parameter.
To make it work like special character you need to create wildcard parameter with name Terms\[*\].Groups
Thanks, Ivan
25-Feb-2021 01:58
thank you , i will try that.