Configure Sensitive Data

To improve the protection of sensitive data, configure sensitive parameter matchers that determine whether or not a request contains sensitive data and should be checked for related vulnerabilities.

These matchers are defined by the parameter names and types, the patterns of names, values or URLs in which they are passed.

  1. In the main menu, click (Projects) and open a project that you want to configure.
  2. Click Sensitive Data.
    A list of currently defined sensitive parameter matchers is displayed.
  3. You can filter the list by the matcher type and literal parameter name, value, and URL. Filtering works only as exact match of the literals with the defined patterns.
    Tip: Seeker supplies several predefined common parameter/header name and value pattern matchers such as authentication token, credit card, password, and more. You can enable or disable any of these matchers as required.
  4. To add a new matcher, click +Add sensitive parameter matcher. To edit an existing matcher, click the Edit button in its row.
  5. Enter the following properties:
    PropertyDescription
    Name Name of the matcher.
    Type Select the type of sensitive parameter matching:
    • Match to any supported user-input type (default)
    • Restrict to HTTP body or query parameters
    • Restrict to HTTP headers
    Parameter name pattern Enter a regex pattern for parameter names, for example,(.*password.*)|(.*passphrase.*)|(.*passwd.*)|(.*username.*). A regex matching any string is .*).
    Parameter value pattern Enter a regex pattern for parameter values, for example, (\b[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,6}\b).
    URL pattern Enter a regex pattern for URLs.
    Mask parameter value Select this option to protect sensitive data, such as passwords. If selected, the sensitive parameter values in a matching vulnerability detection will not be displayed in the UI.
  6. Save your changes.