Understanding Attack Signatures Pool in Application Security

Each security policy has a fixed set of attack signatures that cannot be changed.

User-defined attack signatures can be edited but not deleted from the Attack Signatures Pool.

System-supplied attack signatures are stored in a separate pool from user-defined attack signatures.

You cannot create your own custom attack signature sets.

All attack signature sets are suitable for all types of applications or attacks.

Information Leakage occurs when an attacker attempts to inject XPath queries into a susceptible web application.

User-defined attack signatures are created by the system and added to the attack signature pool.

Filter-based signature sets require manual selection of individual attack signatures to include.

A security policy can be assigned an individual signature.

The Generic Attack Signature Set is not applied to new security policies by default.