Detect an RDP brute force attack¶
Here you will wage a small RDP brute force attack against your Windows Agent instance.
You will see how Wazuh detects and alerts on each login failure, and how a higher severity alert is produced when enough login failures are seen.
Lastly you will take a closer look at the decoders and rules involved in the detection of your “attack”.
Perform the attack¶
Using a Windows Remote Desktop client, attempt to log in as user “george” to your Windows Agent instance eight times in a fairly small time window.
See the resulting alerts in Kibana¶
- On Kibana, go to [Security events], search for “george” and then click on [Discover] on the top right corner.
Discover, you can personalize how to visualize the alerts. If you look at the menu on the left, click on the button next to
Available fields, introduce the field you are looking for in
Field nameand click on [add]. We will be using the 4 fields stated below.
- Inspect the events which will look similar to this:
- Notice how the lower level “Windows: Logon Failure” alert is triggered several times, followed by the higher level “Multiple Windows Logon Failures” alert. This process may repeat itself depending on the total number of logon failures seen.
Where could things proceed from here?¶
The generation of the “Multiple Windows Logon Failures” does not have to be the end of the story for this log event. Other things that could additionally or alternatively take place might be:
- An email, Slack, or PagerDuty message could be generated about this alert.
- A high severity local rule of your own making, child of rule 60204, could fire if the attacked account name specifically matches your secret Windows admin account name.
- An active response could be triggered causing windows-agent to null-route the attacking IP address.
This concludes the RDP brute force attack lab. We hope you enjoyed it!