HTTP Redirect based on protocol

I've found while developing our policies, that ASM does a fantastic job in identifying parameters - but collobaration between the developers and the network staff is needed to create the policy...

 

 

Is there any way of exporting the parameter list to a text file, which can then be shared with the developers while developing the policy? A high level of information containing parameter name, parm flow/object, parm level and parm type would be sufficient for my needs. Anyone else?

 

 

In our situation, learning results in a policy that is too narrow/granular. For example, many object level parms can often be replaced by global parms. But then what happens is that one parameter, whose initial use did not result in a violation, ends up giving a false violation in the production environment.

 

 

If we had the list of parameters, those that should be global and those that should be defined on the object-level (etc...) could be identified and defined appropriately.

 

 

Right now, it appears to be a catch-as-catch-can process.

 

 

thanx,

 

Don