Forum Discussion
NimbostratusAllowed URL, Parameters and files in ASM
Allowed URL, Parameters and files
1- what is the point of allowed URL, parameters and files options in ASM, if application will not accept the parameters etc that is not built-in in application logic
2- After enabling the tightening on wildcard for URL, parameters and files, if I will not enable learning under violations (that is illegal file type, illegal URL and illegal parameters) then ASM will not give the learning suggestion? OR tightening would be enough for learning URL, parameters and file type?
1 Reply
Vitaliy_SavransNacreous
- The point of Allowed URL, Parameters and files is to block disallowed (unwanted) before getting them to the application.
- From Guide:
Understanding tightening
You can perform tightening on wildcard entities (file types, URLs, parameters, and cookies) to learn explicit entities. When you enable tightening for a wildcard entity, and the system receives a request that contains an entity that matches the wildcard entity, the system generates a learning suggestion for the found entity. You can then review the new entities, and decide which are legitimate entities for the web application.
Tightening gives you the option of developing a more specific policy, a policy that is more accurate and in alignment with the traffic. Such a policy can provide better security, but requires more tuning to make sure all the specific entities that you add are accurately configured.
