Set Up Credential Phishing Prevention (PAN-OS & Panorama)

1. Enable User-ID.
   Each of the methods to check for corporate credential submissions requires a different User-ID configuration:

   • Group Mapping—detects whether a user is submitting a valid corporate username and requires you to map users to groups.
   • IP User Mapping—detects whether a user is submitting a valid corporate username and that the username matches the login username—requires you to map IP addresses to users.
   • Domain Credential Filter—detects whether a user is submitting a valid username and password and that those credentials belong to the logged-in user— requires you to configure credential detection with the Windows-based User-ID agent and map IP addresses to users.
2. 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, command-and-control, extremism, copyright-infringement, proxy-avoidance-and-anonymizers, newly-registered-domain, grayware, and parked.
3. Create a Decryption policy rule that decrypts the traffic you want to monitor for user credential submissions.
4. Detect corporate credential submissions to websites that are in allowed URL categories.
   To provide the best performance, the firewall does not check credential submissions for trusted sites, even if you enable the checks for the URL categories for these sites. The trusted sites represent sites where Palo Alto Networks has not observed any malicious or phishing attacks. Updates for this trusted sites list are delivered through Application and Threat content updates.
   1. Select a URL Filtering profile (ObjectsSecurity ProfilesURL Filtering) to modify.
   2. Select User Credential Detection and choose one of the user credential detection methods.
      Confirm that the format for the primary username is the same as the username format that the User-ID source provides.
      • 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, configure any of the user mapping methods listed in Map IP Addresses to Users.
      • Use Domain Credential Filter—Checks for valid corporate usernames and password submissions and verifies that the username maps to the IP address of the logged-in user. For instructions on how to set up this method, see Configure Credential Detection with the Windows-based User-ID Agent.
      • 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 for specific groups that have access to your most sensitive applications, such as IT.

      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.
5. 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 submission.
      • continue—Present the anti-phishing continue 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.
6. 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.
7. Commit the configuration.
8. 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:

   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:

9. 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 Mapping method 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 Filter method 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 all

     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 Filter method 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.