Hi Jaired!
Yes, it must be a literal parameter, not a regular expresion or length type.
Imagine someone stold a bunch o credict cards number an you want to fire an alarm when those numbers are used in a web request parameter; so, you want an alert when the exact stolen credict card number is used, not when the parameter match a "credict card" characteristic (like lenght or regular expression). And, of course, you want the Custom Policy to be as simple as possible (simple = beauty :D), so the credict cards numbers to be audited must be in a separate data set and not embebed in the policy itself.
I guess i should use "
Lookup Data Set Search" as Michael suggested, it could be handdy.
I will try it.
Thx!
------------------------------
Ricardo Gilberto
Analista Seguridad
Ciudad de Buenos Aires
------------------------------
Original Message:
Sent: 02-17-2022 12:27
From: Jaired Anderson
Subject: Custom Web Application Policy using pre defined Lookup Data
Hi Ricardo,
Must it be a strict, predefined list of literal parameters values?
Web Profiles were designed to me this need, however, there are not quite as stringent as you are requesting.
For example, you can define the following as acceptable values for a specific parameter:
-- Number of characters (minimum and maximum)
-- Types of characters allowed (alphanumeric, numeric, special characters)
Would this approach meet your needs?
For more information, please see: https://docs.imperva.com/bundle/v14.4-web-application-firewall-user-guide/page/1953.htm