ASM policy building with automatic versus manual suggestions

The recommendation is to only use those attack signatures that are relevant to your OS/DB/environment. So if you've got Linux/PHP/MySQL, there's no need to use OWA attack signatures. Having said that, it's not uncommon for admins to select all of the signatures because they don't know what they're trying to protect. ASM is remarkably efficient, but there is a penalty for forcing it track strings indicating that a signature has been hit. When you ran the Deployment Wizard, you arrived at the Attack Signature configuration screen about midway through. That's where you first assign attack signatures to your policy. The generic attack signature set (keeps away script kiddies and common SQL or cross-site scripting patterns) is applied to all policies by default.