Manual Chapter : Overview: Creating HTTP Request Signatures

Applies To:

Show Versions Show Versions
Manual Chapter

Overview: Creating HTTP Request Signatures

Due to the dynamic and rapidly changing nature of malware and other types of anti-fraud attacks, users may want to set their own criteria for detecting anti-fraud attacks in addition to the detection services provided by FPS. The Request Signatures user interface allows you to do this, by setting your own criteria for what is considered suspicious data in HTTP requests. If the BIG-IP system detects this data in HTTP requests, an alert is sent to the FPS alert dashboard. Specifically, you can define suspicious data in the following parts of the HTTP request: header field, payload, query string, Client IP address, and path.
HTTP request signatures are defined per URL in the anti-fraud profile.