In a brute force attack, an attacker gains access to your system simply by repeatedly logging in with a variety of passwords until they guess the correct one. The ExtraHop Active Directory bundle can help you discover when these attacks are happening and where they are coming from.
In this walkthrough, you will learn how to download, install, and configure the Active Directory bundle, and then identify potential Kerberos brute force attacks with the Active Directory dashboard.
- Familiarize yourself with the concepts in this walkthrough by reading the Bundles concepts topic.
- You must have access to an ExtraHop Discover appliance with a user account that has full write privileges.
- You must be familiar with modifying triggers. For more information, see the Triggers concepts topic.
Before you can upload the Active Directory Bundle to your appliance, you must download the bundle from the ExtraHop website.
- Go to the ExtraHop Solution Bundles Gallery.
- Click Browse All Bundles.
- In the search bar, type Active Directory.
In the table, click Active Directory.
Note: This walkthrough is based on the Active Directory v3 bundle.
- If you have not already logged into the ExtraHop website, click Login in the right pane and then specify a valid username and password.
- Click Download Now.
- Save the .json file to a location on your local machine.
After you have downloaded the Active Directory Bundle, you can upload and install the bundle on your appliance.
- Log into the Web UI of a Discover appliance.
- Click the System Settings icon in the upper right corner.
- Click Bundles.
- On the Bundles page, click Upload.
- In the Load Bundle dialog box, click the Choose File button, and then select the Active Directory Bundle file you downloaded from the ExtraHop Solution Bundle Gallery.
- Click Upload.
- Select the Apply 7 included assignments checkbox.
From the Existing objects drop-down menu, select
Selecting this option will overwrite any objects that have the same name as objects in the bundle.
- Click Apply.
- In the Bundle Import Status dialog box, click OK.
- In the View Bundle window, click OK.
Before you can begin monitoring Active Directory activity, you must configure the trigger to mirror lockout and privileged account settings in your Active Directory environment.
- Click the System Settings icon .
- Click Triggers.
- In the table, click Active Directory.
- Click the Editor tab.
- Set the failedLoginDisableInterval constant to the value of the Reset account lockout counter after setting in your Active Directory environment.
- Set the accountLockoutDuration constant to the value of the Account lockout duration setting in your Active Directory environment.
- Under priv_names, specify all privileged accounts in your Active Directory environment.
- Click the Configuration tab.
- Clear the Disable Trigger checkbox to enable the trigger.
- Click Save and Close.
The Active Directory Bundle includes alerts that you can configure to email you when high processing and response times are detected. You can also be alerted when a privileged account accesses resources for the first time, or if someone attempts to log into a privileged account too many times with an invalid password.
- Click the System Settings icon .
- Click Alerts.
Enable each alert and configure the alert to send notifications to your email
Repeat these steps for each of the five ransomware alerts.
- Click Active Directory <alert>.
- Deselect the Disable Alert checkbox.
- Click Notifications.
- In the Additional email addresses field, type your email address.
- Click OK.
This example shows how you can detect Kerberos brute force attacks with the Active Directory bundle.
The Active Directory dashboard shows you how many times a user has attempted to log into a Kerberos system with an invalid password. In the example below, the bundle detected 13,605 unsuccessful log in attempts.
The Top 10 Users with Invalid Passwords chart then shows you which user accounts people are attempting to log into. User names are listed next to the IP address of the machine they attempted to log in from. In the following example, a machine with an IP address of 126.96.36.199 attempted to log into the kenp account 13,602 times:
It is highly unlikely that the legitimate owner of the kenp account attempted to log in thirteen thousand times without contacting an administrator. High levels of invalid logins like this are usually the result of a brute-force attack. The attacker is trying every possible password in an attempt to discover the correct one. With an ExtraHop Explore appliance, we can gain even more insight into the attack. To do this, we type the IP address of the machine into the top search bar, and then click Search Records for 188.8.131.52.
The records table shows all transactions related to the specified IP address. Clicking Kerberos Response AD in the left pane limits the results to Kerberos transactions only. Sorting the table by AD Error shows us all invalid password requests, including which machines specified those invalid passwords. The table shows that although the invalid password attempts all came from 184.108.40.206, there are a number of successful requests coming from 10.100.100.1:
These results suggest that 10.100.100.1 belongs to the actual user, and 220.127.116.11 belongs to the attacker. We can now block logins from 18.104.22.168 and contact the owners of both machines to confirm.
Now that the Active Directory bundle is up and running, you can check out the other charts in the Active Directory dashboard to monitor potential access and authentication issues.