Through BIG-IQ® Web Application Security, you can view and manage signature files and signature file updates centrally for multiple BIG-IP® devices. For each signature file, the system displays the file name, the file version, the version of BIG-IP with which it is compatible, and its source.
By managing signature files from the BIG-IQ platform, the administrator can spend less time on signature updates and can view the signatures update information in a single central location.
The BIG-IP system includes an attack signature pool and a bot signature pool. These pools include the system-supplied attack signatures and bot signatures, which are shipped with the BIG-IP Application Security Manager, and any user-defined signatures.
BIG-IQ Web Application Security fetches all new and relevant signature files automatically from an external server proxy configured from the system interface. It can then push the signature files to the relevant BIG-IP device or to multiple BIG-IP devices. It displays the signature version for each device.
Signature file properties are read-only and displayed for informational purposes only.
|Name||Name of the signature file. Example: ASM-SignatureFile_20150917_152714.im123456789|
|Version||Version of the signature file. Example: 1445276000000|
|Compatibility||Version running on the BIG-IP® device with which the signature file is compatible. Example: BIG-IP 11.5.3|
|Source||F5 Networks. Example: F5|
If a signature file is pushed to a clustered system, the configuration of the nodes is synchronized. The ASM™ configuration is deployed to the active device and then synchronized with the standby device.