Set Up Credential Phishing Prevention
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.
After you have decided which of the methods to detect 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 the submission.
Before enabling credential phishing prevention, verify that the Primary Username that you configure on the firewall uses the sAMAccountName attribute. Credential phishing prevention does not support alternate attributes.
- 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:
- If you plan to use the group mapping method, which detects whether a user is submitting a valid corporate username, map users to groups.
- If you plan to use the IP user mapping method, which detects whether a user is submitting a valid corporate username and that username is the same as the login username, map IP addresses to users.
- If you plan to use the domain credential filter method, which detects whether a user is submitting a valid username and password and that those credentials belong to the logged-in user, configure credential detection with the Windows-based User-ID agent and map IP addresses to users.
- 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.
- SelectandObjectsSecurity ProfilesURL FilteringAddor modify a URL Filtering profile.
- 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.
- Add a Decryption policy rule to decrypt the traffic you want to monitor for user credential submissions.
- Configure the URL Filtering profile to detect corporate credential submissions to websites that are in allowed URL categories.The firewall does not check credential submissions for trusted sites, even if you enable the checks for the URL categories for these sites, to provide best performance. 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. For a list of App-IDs that are exempt from credential detection, see Trusted App-IDs That Skip Credential Submission Detection on live.paloaltonetworks.com.
- SelectUser Credential Detection.
- Select one of the user credential detection methods to web pages from theUser Credential Detectiondrop-down:Confirm that the format for the primary username is the same as the username format that the User-ID source provides.
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.
- 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 and 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 for specific groups that have access to your most sensitive applications, such as IT.
- Set theValid Username Detected Log Severitythe firewall uses to log detection of corporate credential submissions. By default, the firewall logs these events as medium severity.
- Block (or alert) on credential submissions to allowed sites.
- For each Category to whichSite Accessis allowed, select how you want to treatUser 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.
- SelectOKto save the URL Filtering profile.
- Apply the URL Filtering profile with the credential detection settings to your Security policy rules.
- SelectandPoliciesSecurityAddor modify a Security policy rule.
- On theActionstab, set theProfile TypetoProfiles.
- Select the new or updatedURL Filteringprofile to attach it to the Security policy rule.
- SelectOKto save the Security policy rule.
- Committhe configuration.
- Monitor credential submissions the firewall detects.Selectto see the number of users who have visited malware and phishing sites.ACCHosts Visiting Malicious URLsSelect.MonitorLogsURL FilteringThe newCredential Detectedcolumn 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:
- Validate and troubleshoot credential submission detection.
>show user credential-filter statisticsThe 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.
- Use the following CLI command to view credential detection statistics:
- (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 allThe 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
Recommended For You
Recommended videos not found.