Elastic Security Detection Rules

Spike in Failed Logon Events

Last updated 2 years ago on 2024-06-18
Created 5 years ago on 2021-06-10

About

A machine learning job found an unusually large spike in authentication failure events. This can be due to password spraying, user enumeration or brute force activity and may be a precursor to account takeover or credentialed access.
Tags
Use Case: Identity and Access AuditUse Case: Threat DetectionRule Type: MLRule Type: Machine LearningTactic: Credential Access
Severity
low
Risk Score
21
MITRE ATT&CK™

Credential Access (TA0006)(external, opens in a new tab or window)

↳ Brute Force (T1110)(external, opens in a new tab or window)

False Positive Examples
A misconfigured service account can trigger this alert. A password change on an account used by an email client can trigger this alert. Security test cycles that include brute force or password spraying activities may trigger this alert.
License
Elastic License v2(external, opens in a new tab or window)

Definition

Rule Type
Machine Learning
Integration Pack
Prebuilt Security Detection Rules
Related Integrations

auditd_manager(external, opens in a new tab or window)

endpoint(external, opens in a new tab or window)

system(external, opens in a new tab or window)

Query
text code block:

Install detection rules in Elastic Security

Detect Spike in Failed Logon Events in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(external, opens in a new tab or window).