-
Identifies when an Okta user account is locked out 3 times within a 3 hour window. An adversary may attempt a brute force or password spraying attack to obtain unauthorized access to user accounts. The default Okta authentication policy ensures that a user account is locked out after 10 failed authentication attempts.
Read More -
AWS Management Console Brute Force of Root User Identity
Sep 19, 2026 · Domain: Cloud Data Source: AWS Data Source: Amazon Web Services Data Source: AWS Sign-In Use Case: Identity and Access Audit Tactic: Credential Access Resources: Investigation Guide Noise: Low Performance: Normal Profile: Recommended Threat: Brute Force Rule Type: Threshold Platform: AWS Data Source: AWS CloudTrail ·Identifies a high number of failed authentication attempts to the AWS management console for the Root user identity. An adversary may attempt to brute force the password for the Root user identity, as it has complete access to all services and resources for the AWS account.
Read More -
AWS S3 Bucket Enumeration or Brute Force
Sep 19, 2026 · Domain: Cloud Data Source: AWS Data Source: Amazon Web Services Data Source: AWS S3 Resources: Investigation Guide Use Case: Log Auditing Tactic: Impact Tactic: Discovery Tactic: Collection Noise: High Performance: Normal Profile: Aggressive Threat: Brute Force Rule Type: Threshold Platform: AWS Data Source: AWS CloudTrail Service: AWS S3 ·Identifies a high number of failed S3 operations against a single bucket from a single source address within a short timeframe. This activity can indicate attempts to collect bucket objects or cause an increase in billing to an account via internal "AccessDenied" errors.
Read More -
Entra ID MFA TOTP Brute Force Attempted
Sep 19, 2026 · Domain: Cloud Domain: Identity Data Source: Azure Data Source: Entra ID Data Source: Entra ID Sign-In Logs Use Case: Identity and Access Audit Use Case: Threat Detection Tactic: Credential Access Resources: Investigation Guide Noise: Low Performance: Normal Profile: Recommended Threat: Brute Force Rule Type: ES|QL Platform: Entra ID ·Identifies brute force attempts against Azure Entra multi-factor authentication (MFA) Time-based One-Time Password (TOTP) verification codes. This rule detects high frequency failed TOTP code attempts for a single user in a short time-span with a high number of distinct session IDs. Adversaries may programmatically attemopt to brute-force TOTP codes by generating several sessions and attempt to guess the correct code.
Read More -
Entra ID Sign-in Brute Force Attempted (Microsoft 365)
Sep 19, 2026 · Domain: Cloud Domain: SaaS Domain: Identity Data Source: Azure Data Source: Entra ID Data Source: Entra ID Sign-In Logs Use Case: Identity and Access Audit Use Case: Threat Detection Tactic: Credential Access Resources: Investigation Guide Noise: High Performance: Normal Profile: Aggressive Threat: Brute Force Rule Type: ES|QL Platform: Entra ID ·Identifies potential brute-force attacks targeting Microsoft 365 user accounts by analyzing failed sign-in patterns in Microsoft Entra ID Sign-In Logs. This detection focuses on a high volume of failed interactive or non-interactive authentication attempts within a short time window, often indicative of password spraying, credential stuffing, or password guessing. Adversaries may use these techniques to gain unauthorized access to Microsoft 365 services such as Exchange Online, SharePoint, or Teams.
Read More -
Entra ID User Sign-in Brute Force Attempted
Sep 19, 2026 · Domain: Cloud Domain: Identity Data Source: Azure Data Source: Entra ID Data Source: Entra ID Sign-In Logs Use Case: Identity and Access Audit Use Case: Threat Detection Tactic: Credential Access Resources: Investigation Guide Noise: Medium Performance: Normal Profile: Recommended Threat: Brute Force Rule Type: ES|QL Platform: Entra ID ·Identifies potential brute-force attacks targeting user accounts by analyzing failed sign-in patterns in Microsoft Entra ID Sign-In Logs. This detection focuses on a high volume of failed interactive or non-interactive authentication attempts within a short time window, often indicative of password spraying, credential stuffing, or password guessing. Adversaries may use these techniques to gain unauthorized access to applications integrated with Entra ID or to compromise valid user accounts.
Read More -
M365 Identity User Brute Force Attempted
Sep 19, 2026 · Domain: Cloud Domain: SaaS Data Source: Microsoft 365 Data Source: Microsoft 365 Audit Logs Use Case: Identity and Access Audit Use Case: Threat Detection Tactic: Credential Access Resources: Investigation Guide Noise: High Performance: Normal Profile: Aggressive Threat: Brute Force Rule Type: ES|QL Platform: Microsoft 365 ·Identifies brute-force authentication activity targeting Microsoft 365 user accounts using failed sign-in patterns that match password spraying, credential stuffing, or password guessing behavior. Adversaries may attempt brute-force authentication with credentials obtained from previous breaches, leaks, marketplaces or guessable passwords.
Read More -
Multiple Logon Failure Followed by Logon Success
Sep 19, 2026 · Domain: Endpoint OS: Windows Use Case: Threat Detection Tactic: Credential Access Resources: Investigation Guide Data Source: Windows Security Event Logs Noise: High Performance: Normal Profile: Aggressive Threat: Brute Force Rule Type: Event Correlation (EQL) Platform: Windows Resources: Osquery ·Identifies multiple logon failures followed by a successful one from the same source address. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to accounts.
Read More -
Multiple Logon Failure from the same Source Address
Identifies multiple consecutive logon failures from the same source address and within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to accounts.
Read More -
Identifies multiple external consecutive login failures targeting a user account from the same source address within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to these accounts.
Read More -
Identifies multiple internal consecutive login failures targeting a user account from the same source address within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to these accounts.
Read More -
Identifies multiple consecutive login attempts executed by one process targeting a local linux user account within a short time interval. Adversaries might brute force login attempts across different users with a default wordlist or a set of customly crafted passwords in an attempt to gain access to these accounts.
Read More -
Identifies a high number of inbound SSH login attempts on a macOS host within a short time window. On macOS, each inbound SSH authentication attempt spawns the sshd-keygen-wrapper process once, whether the login succeeds or fails. Adversaries may perform password brute force or password spraying against exposed SSH services to obtain unauthorized access.
Read More -
Potential Malware-Driven SSH Brute Force Attempt
This detection identifies a Linux host that has potentially been infected with malware and is being used to conduct brute-force attacks against external systems over SSH (port 22 and common alternative SSH ports). The detection looks for a high volume of outbound connection attempts to non-private IP addresses from a single process. A compromised host may be part of a botnet or controlled by an attacker, attempting to gain unauthorized access to remote systems. This behavior is commonly observed in SSH brute-force campaigns where malware hijacks vulnerable machines to expand its attack surface. ESQL rules have limited fields available in its alert documents. Make sure to review the original documents to aid in the investigation of this alert.
Read More -
Detects potential brute force attacks against a single Okta user account where excessive unique device token hashes are generated, indicating automated tooling that fails to persist browser cookies between attempts.
Read More -
Potential Okta Brute Force (Multi-Source)
Sep 19, 2026 · Domain: Identity Use Case: Identity and Access Audit Use Case: Threat Detection Data Source: Okta Data Source: Okta System Logs Tactic: Credential Access Resources: Investigation Guide Noise: Low Performance: Fast Profile: Recommended Threat: Brute Force Rule Type: ES|QL Platform: Okta ·Detects potential brute force attacks against a single Okta user account from multiple source IPs, indicating attackers rotating through proxy infrastructure to evade IP-based detection.
Read More -
Detects potential credential stuffing attacks where a single source IP attempts authentication against many Okta user accounts with minimal attempts per user, indicating the use of breached credential lists.
Read More -
Potential Okta Password Spray (Multi-Source)
Sep 19, 2026 · Domain: Identity Use Case: Identity and Access Audit Use Case: Threat Detection Data Source: Okta Data Source: Okta System Logs Tactic: Credential Access Resources: Investigation Guide Noise: High Performance: Fast Profile: Aggressive Threat: Brute Force Rule Type: ES|QL Platform: Okta ·Detects potential password spray attacks where multiple source IPs target multiple Okta user accounts within a time window, indicating coordinated attacks using IP rotation to evade single-source detection.
Read More -
Detects potential password spray attacks where a single source IP attempts authentication against multiple Okta user accounts with repeated attempts per user, indicating common password guessing paced to avoid lockouts.
Read More -
This rule detects potential password spraying attacks via SSH by identifying multiple failed login attempts from a single source IP address targeting various user accounts within a short time frame. Password spraying is a technique where an attacker attempts to gain unauthorized access by trying a few commonly used passwords against many different accounts, rather than targeting a single account with multiple password attempts.
Read More -
Identifies repeated SIP REGISTER authentication rejection responses for one or more extensions from a client to a VoIP server within five minutes. The rule distinguishes repeated failures from the single 401 or 407 challenge expected in a normal digest-authentication flow. Attackers brute-force extension credentials to register rogue endpoints for toll fraud, call interception, or registration hijacking.
Read More -
Identifies multiple SSH login failures followed by a successful one from the same source address. Adversaries can attempt to login into multiple users with a common or known password to gain access to accounts.
Read More -
Privileged Accounts Brute Force
Identifies multiple consecutive logon failures targeting more than one Admin account from the same source address and within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to accounts.
Read More