Problem:Idira EPM offers multiple endpoint protection features and more often than not, least privilege is the first and primary focus for many organizations. This is the correct strategy since removing all local administrator accounts should be the first phase to complete in the EPM adoption journey.Threat actors and vulnerable software can contribute to increasing the chances of compromising endpoints, whether the access is via a privileged account or not. One method that has gained in popularity in recent years is credential theft in web browsers. Your browser credential store may contain different cached credentials to various applications and systems. Some of these credentials could be privileged accounts that will allow hackers to move laterally onto systems containing sensitive data. With sophisticated ransomware or malicious browser extensions, it can be easy for these hackers to install and execute scripts to access and download the credential store in your browsers.Read on to learn how EPM can protect against credential store theft using the Privileged Threat Protection (PTP) feature. PTP can be easily enabled and is not susceptible to zero-day attacks since EPM monitors the credential store and alerts when the database is accessed regardless of the payload.
Steps
Solution:1. To enable the browser stored credential protection in EPM, turn on the Protect Against Credential Theft and Lateral Movement default policy and choose Detect mode.
2. IMPORTANT NOTE: Click on Edit policy settings to tune the credential theft policy. This is an important step since you will only want to enable the specific Browsers Stored Credential Theft policy. Clicking on the blue Yes button below will instead enable detection for every protection available with PTP. This results in turning on events management for all possible events. Best practice is to enable one credential theft policy at a time so events can be tuned more effectively since events are more manageable.
3. Under Browsers Stored Credential Theft, enable detection for each browser that is supported in your organization (Chrome, Firefox, and/or MS Edge). As mentioned previously, these credential theft policies should be enabled and targeted to a pilot group first to validate the types of events generated in Events Management. The number of events could vary based on the environment but targeting a pilot group would provide a good indicator as to how many events need to be reviewed. Continue to expand the pilot group and review Events Management again. Eventually, the policy can be enabled to cover all endpoints and switched from Detect to Block mode.
When this policy is enabled, EPM is monitoring the file that contains the stored credentials and checks to see who or what is accessing it. When accessed, EPM generates an event containing information about the suspect process and other pertinent file info.
It is important to remember that this credential theft protection policy detects and/or blocks access made by all applications, even legitimate ones. Legitimate applications would need to be documented/identified in Events Management and added to the exclusions list of the credential theft policy or allowed separately via another EPM policy.In Events Management, the specific event type that is associated with browser credential theft is event type
Attack Attempt, which can be filtered using the
Table view.
Now you are protected from browser credential theft! These steps can be repeated to enable more threat protection policies such as IT application credential theft and remote access application credentials. Make sure these policies are enabled gradually and piloted first before rolling out to the organization.