Tristan’s Cybersecurity Substack

Tristan’s Cybersecurity Substack

Share this post

Tristan’s Cybersecurity Substack
Tristan’s Cybersecurity Substack
SIEM 102 — Detect Windows bruteforce
Copy link
Facebook
Email
Notes
More
SIEM / SOC / MDR

SIEM 102 — Detect Windows bruteforce

Tristan Dostaler's avatar
Tristan Dostaler
Nov 13, 2024
∙ Paid

Share this post

Tristan’s Cybersecurity Substack
Tristan’s Cybersecurity Substack
SIEM 102 — Detect Windows bruteforce
Copy link
Facebook
Email
Notes
More
Share
Upgrade to paid to play voiceover

In this post I’ll explain how to detect a bruteforce on Windows. This is a simple case so it’s a good use case to start learning to create alerts.

Note: In this post I use Logz.io for my examples, but I recently switched to Humio. For more details: https://www.tristandostaler.com/why-i-switched-from-logz-io-to-humio/


For this post, I assume you’ve read my SIEM 100 series where I explain the basics of Logz.io. I’ll be using the stack I created in this series to demonstrate what to do.


Why we need to detect Windows bruteforce

When we have a lot of Windows machine in our environment, it can be useful to be able to detect a bruteforce on a machine, be it over RDP or not. For example, with this Use Case, we could detect an attacker trying to login on a sensitive computer or trying to pivot between machine.

This Use Case is really simple so it’s rather easy to develop and test. But it’s also prone to false positive, so it’s a good Use Case to learn to reduce the false positives.

How

Keep reading with a 7-day free trial

Subscribe to Tristan’s Cybersecurity Substack to keep reading this post and get 7 days of free access to the full post archives.

Already a paid subscriber? Sign in
© 2025 Tristan Dostaler
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture

Share

Copy link
Facebook
Email
Notes
More