Set Up Credential Phishing Prevention

After you have decided which of the Methods to Check for Corporate Credential Submissions you want to use, take the following steps to enable the firewall to detect when users submit corporate credentials to web pages and either alert on this action, block the credential submission, or require users to acknowledge the dangers of phishing before continuing with credential submission.
  1. If you have not done so already, Enable User-ID.
    Each of the Methods to Check for Corporate Credential Submissions requires a different User-ID configuration to check for corporate credential submissions:
  2. If you have not done so already, configure a best practice URL Filtering profile to ensure protection against URLs that have been observed hosting malware or exploitive content.
    1. Select ObjectsSecurity ProfilesURL Filtering and Add or modify a URL Filtering profile.
    2. Block access to all known dangerous URL categories: malware, phishing, dynamic DNS, unknown, questionable, extremism, copyright-infringement, proxy-avoidance-and-anonymizers, and parked.
  3. Configure the URL Filtering profile to detect corporate credential submissions to websites that are in allowed URL categories.
    The firewall automatically skips checking credential submissions for App-IDs associated with sites that have never been observed hosting malware or phishing content to ensure the best performance even if you enable checks in the corresponding category. The list of sites on which the firewall will skip credential checking is automatically updated via Application and Threat content updates.
    1. Select User Credential Detection.
    2. Select one of the Methods to Check for Corporate Credential Submissions to web pages from the User Credential Detection drop-down:
      • Use IP User Mapping—Checks for valid corporate username submissions and verifies that the login username maps to the source IP address of the session. To do this, the firewall matches the submitted username and source IP address of the session against its IP-address-to-username mapping table. To use this method you can use any of the user mapping methods described in Map IP Addresses to Users.
      • Use Domain Credential Filter—Checks for valid corporate usernames and password submissions verifies that the username maps to the IP address of the logged in user. See Configure Credential Detection with the Windows-based User-ID Agent for instructions on how to set up User-ID to enable this method.
      • Use Group Mapping—Checks for valid username submissions based on the user-to-group mapping table populated when you configure the firewall to Map Users to Groups.
        With group mapping, you can apply credential detection to any part of the directory, or specific group, such as groups like IT that have access to your most sensitive applications.
      This method is prone to false positives in environments that do not have uniquely structured usernames. Because of this, you should only use this method to protect your high-value user accounts.
    3. Set the Valid Username Detected Log Severity the firewall uses to log detection of corporate credential submissions. By default, the firewall logs these events as medium severity.
  4. Block (or alert) on credential submissions to allowed sites.
    1. Select Categories.
    2. For each Category to which Site Access is allowed, select how you want to treat User Credential Submissions:
      • alert—Allow users to submit credentials to the website, but generate a URL Filtering log each time a user submits credentials to sites in this URL category.
      • allow—(default) Allow users to submit credentials to the website.
      • block—Block users from submitting credentials to the website. When a user tries to submit credentials, the firewall displays the Anti Phishing Block Page, preventing the credential submission.
      • continue—Present the Anti Phishing Continue Page response page to users when they attempt to submit credentials. Users must select Continue on the response page to continue with the submission.
    3. Select OK to save the URL Filtering profile.
  5. Apply the URL Filtering profile with the credential detection settings to your Security policy rules.
    1. Select PoliciesSecurity and Add or modify a Security policy rule.
    2. On the Actions tab, set the Profile Type to Profiles.
    3. Select the new or updated URL Filtering profile to attach it to the Security policy rule.
    4. Select OK to save the Security policy rule.
  6. Commit the configuration.
  7. Monitor credential submissions the firewall detects.
    Select ACCHosts Visiting Malicious URLs to see the number of users who have visited malware and phishing sites.
    Select MonitorLogsURL Filtering.
    The new Credential Detected column indicates events where the firewall detected a HTTP post request that included a valid credential:
    credential-phishing-log-column.png
    (To display this column, hover over any column header and click the arrow to select the columns you’d like to display).
    Log entry details also indicate credential submissions:
    credential-phishing-log-detail.png
  8. Validate and troubleshoot credential submission detection.
    • Use the following CLI command to view credential detection statistics:
    > show user credential-filter statistics
    The output for this command varies depending on the method configured for the firewall to detect credential submissions. For example, if the Domain Credential Filter method is configured in any URL Filtering profile, a list of User-ID agents that have forwarded a bloom filter to the firewall is displayed, along with the number of credentials contained in the bloom filter.
    • (Group Mappingmethod only) Use the following CLI command to view group mapping information, including the number of URL Filtering profiles with Group Mapping credential detection enabled and the usernames of group members that have attempted to submit credentials to a restricted site.
      >show user group-mapping statistics
    • (Domain Credential Filtermethod only) Use the following CLI command to see all Windows-based User-ID agents that are sending mappings to the firewall:
      > show user user-id-agent state
      The command output now displays bloom filter counts that include the number of bloom filter updates the firewall has received from each agent, if any bloom filter updates failed to process, and how many seconds have passed since the last bloom filter update.
    • (Domain Credential Filtermethod only) The Windows-based User-ID agent displays log messages that reference BF (bloom filter) pushes to the firewall. In the User-ID agent interface, select MonitoringLogs.

Related Documentation