Will auto policy builder handle wildcards parameters like PAR1, PAR2, PAR3 -> PAR?
Hello, I am currently building up a policy in manual mode. Due to the size of this application, it requires a fair bit of work to add all parameters to the policy. A lot of these parameters are in the following form; PAR1 PAR2 iPAR1 iPAR2 PAR3 PAR4 ... PAR11 ... Does the automatic policy builder correctly build wildcard parameters with the numbers as a wildcard? Thanks. Regards
ASM url extensions "learning" new extensions
Hi, I have a problem with ASM trying to suggest extensions that don't exist like .55 .66 .78 etc. We have a web apps that put a lot of data into urls and and sometimes there are 2-3 random characters after a dot at the end, for example .xsa .12 .45 etc. ASM acts like it is a new file extension and suggests adding .55 extension.. Is there any way of fixing this other then by adding a "*" to allowed extensions and blacklist all unwanted ones?
Auto learning backed server by ASM?
Hello folks, I have got a requirement from the customer, and they have hosted an internal web server. The issue is, as and when they apply any changes to the web server, for eg. adding a new page, or modifying the existing page etc. ASM throws alert messages and doesn't allow to communicate further. Earlier I'd added parameter based exception, however it is becoming a challenge of daily life, as they are keep updating random pages to the web server. I can absolutely understand the ASM behavior, as it didn't learn the newly added resources, it will deny any communication to that resource. And that is how the behavior should be. However is there anyway where we can make this learning automatic or put it under staging (not the whole server, specific URI from where they are updating)? Thanks for your time, Cheers! Darshan