Application Security Community

 View Only
Expand all | Collapse all

Custom Web Application Policy using pre defined Lookup Data

  • 1.  Custom Web Application Policy using pre defined Lookup Data

    Posted 02-16-2022 16:21
    Hi!

    It is possible to create a custom web application policy where the match criteria consist in:
    Any requet parameter (value) that matches with any value from a lookup data (already defined)

    it seems to be suach an easy task to perform, but i can not seet this option in the SecureSphere web interface neither documentation.
    it is a SecureSphere limitation?

    Thx!
    Ricardo Giliberto
    #On-PremisesWAF(formerlySecuresphere)

    ------------------------------
    -------------------------
    Ricardo Gilberto
    Analista Seguridad
    Ciudad de Buenos Aires
    -------------------------
    ------------------------------


  • 2.  RE: Custom Web Application Policy using pre defined Lookup Data
    Best Answer

    Posted 02-17-2022 08:02
    Hi Ricardo,

    Have you tried to use "Lookup Data Set Search" rule in web custom policy ?

    ------------------------------
    Michael Sorin
    Software Engineer
    Tel Aviv CA
    ------------------------------



  • 3.  RE: Custom Web Application Policy using pre defined Lookup Data

    Posted 02-17-2022 12:28
    Edited by Jaired ANDERSON 02-17-2022 12:50

    Hi Ricardo,

    Must it be a strict, predefined list of literal parameters values?

    Web Profiles were designed to me this need, however, they're 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 




  • 4.  RE: Custom Web Application Policy using pre defined Lookup Data

    Posted 02-17-2022 12:47
    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
    ------------------------------