Detections

Explore public detection logic contributed by the community across SIEM and rule languages.

780 detections

Detects when an Okta user rejects more than 2 Push notifications in a 10 minute window. This behavior can indicate an attacker attempting to gain access to an account by repeatedly sending MFA push notifications, hoping the user will eventually accept one (MFA fatigue).
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
10114
This rule detects failed authentication attempts in Okta where the security result indicates a "FastPass declined phishing attempt." This specifically targets real-time Adversary-in-the-Middle (AiTM) phishing proxy attacks against users enrolled in Okta FastPass, which is designed to prevent such attacks by checking the origin of the authentication request.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0079
This rule detects successful logins to the AWS console where Multi-Factor Authentication (MFA) was not used. It specifically looks for 'ConsoleLogin' events from AWS CloudTrail with an 'ALLOW' action and where 'MFAUsed' is explicitly set to 'No'. The rule also increases the risk score if the login is performed by a 'Root' user.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
2070
Detects when a high number of failed authentication attempts occur for unknown users on AWS, indicating a potential brute-force or credential stuffing attack against the AWS console.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
3069
This rule detects a successful login to the AWS console after multiple failed login attempts for the same user within a 15-minute window. It specifically looks for at least three failed authentication attempts followed by one successful authentication. The rule also calculates a risk score based on potential country mismatches between failed and successful attempts, and successful logins from unauthorized geographies (Cuba, Iran, North Korea, Russia, Syria).
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0062
This rule detects an unusual number of failed authentication attempts from the same IP address targeting valid users within an AWS environment. It specifically looks for 'ConsoleLogin' events from AWS CloudTrail where the security result indicates a 'BLOCK' action due to 'Failed authentication'. The rule triggers if there are more than 5 distinct target users experiencing failed logins from the same IP within a 5-minute window. Additionally, it calculates a risk score based on whether the source IP's country of origin is associated with known high-risk geographies (Cuba, Iran, North Korea, Russia, Syria).
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0060
This rule detects suspected brute force attacks against Okta accounts. It triggers when Okta ThreatInsight identifies multiple login failures from the same IP address across one or more Okta organizations. The rule also increases the risk score if the IP address is marked as suspicious by Okta ThreatInsight or if the login attempts originate from specific high-risk countries (Cuba, Iran, North Korea, Russia, Syria).
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
6050
Detects multiple failed requests to access different applications within a short timeframe from the same network session. This could indicate an adversary attempting to bypass authentication mechanisms, potentially using stolen session cookies or brute-forcing access to various applications after an initial compromise. The rule also incorporates risk scoring based on behavioral anomalies (e.g., new geo-location, new device, new IP) and access attempts from high-risk countries.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0050
This rule detects when an Okta user fails a number challenge during a push notification for multi-factor authentication. This specific failure occurs when the user provides an invalid response to the number challenge, leading to the authentication attempt being blocked. This could indicate an attacker attempting to gain access to an account by repeatedly sending MFA push notifications, hoping the user will eventually accept or incorrectly respond to the challenge.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0047
This rule detects multiple login failures from the same IP address targeting unknown users, as identified by Okta's ThreatInsight. It specifically looks for Okta events categorized as 'USER_UNCATEGORIZED' and 'security.threat.detected' with a summary indicating 'Login failures with high unknown users count'. The rule also incorporates risk scoring based on whether the IP address is deemed suspicious by Okta ThreatInsight and if the login attempts originate from certain high-risk countries.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0041
This rule detects multiple failed login attempts from different users originating from the same IP address within a one-hour window in Okta. It specifically looks for events where the login attempt was blocked due to invalid credentials. The rule also incorporates risk scoring based on Okta ThreatInsight detections and behavioral patterns like new geo-location, device, or IP, as well as logins from unauthorized geographies (Cuba, Iran, North Korea, Russia, Syria). The detection is triggered if more than 5 distinct user IDs attempt to log in with invalid credentials from the same IP within the specified timeframe.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
3039
Detects when a single user successfully logs into Okta from multiple distinct cities within a 24-hour period. This behavior can indicate a compromised account being used by an attacker from a different geographical location than the legitimate user, or a user traveling rapidly between distant locations. The rule also incorporates risk scoring based on Okta ThreatInsight and logins from suspicious countries.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0035
This rule detects multiple failed login attempts from different users originating from the same IP address within a one-hour window in OneLogin. It specifically looks for 'USER_LOGIN' events with a 'BLOCK' security result and a product event type of '6' (user failed authentication). The rule also calculates a risk score, which is increased if the originating IP address is from certain unauthorized geographies (Cuba, Iran, North Korea, Russia, Syria). This behavior is indicative of potential brute-force attacks or credential stuffing attempts against multiple user accounts from a single source.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0035
This rule detects suspected password spraying attacks identified by Okta's ThreatInsight. It specifically looks for Okta security events categorized as 'Password Spray' and can additionally increase the risk score if the originating IP address is marked as suspicious by Okta ThreatInsight or if the login attempt originates from certain unauthorized geographies (Cuba, Iran, North Korea, Russia, Syria).
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
1034
This rule detects a successful OneLogin login event that is preceded by multiple failed One-Time Password (OTP) attempts within a 15-minute window for the same user. Specifically, it looks for at least four failed OTP challenges followed by a successful OTP verification and then a successful user login. This pattern is indicative of an OTP brute-force attack where an attacker is attempting to guess the correct OTP.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0030
This rule detects targeted brute-force attacks against an Okta organization. It specifically looks for events from Okta ThreatInsight where known malicious IPs are attempting to access a specific user account, indicated by multiple failed authentication attempts for the same user within a one-hour window. The rule leverages Okta's security.attack.start event type to identify these activities.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0028
This rule detects suspicious user login activity where a single user attempts to log in from multiple distinct countries within a 24-hour period. This behavior can indicate a compromised account being used by an attacker from a different geographic location than the legitimate user, or a user attempting to bypass security controls. The rule also assigns a higher risk score if the login originates from specific high-risk countries (Cuba, Iran, North Korea, Russia, Syria).
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0026
Okta provides a platform detection for when a user enrolled in FastPass fails to authenticate via a real-time AiTM phishing proxy.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
003
Detects multiple user logins with invalid credentials from a single IP.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
002
Detects a successful login after multiple failed OTP intents
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
002
Detects when a high number of failed authentication attempts happen for unknown users.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
001
Page 36 of 38