Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
1,666 detections
Filters
Last updated
All Time
Detection languages
1,077
189
170
102
53
Contributors
520
361
306
67
52
Categories
20,401
11,795
5,864
5,145
4,864
1,666
Platforms
1,091
590
440
252
122
Products / Services
1,130
476
189
125
118
MITRE Techniques
944
842
437
416
412
CVEs
12
12
9
6
5
IDS Classtypes
1
1
Detects a single user account authenticating from an unusually high number of distinct IP addresses within a short timeframe (1 hour), which may indicate the use of rotating proxy services or account sharing, commonly associated with unauthorized access or reseller activity.
Detects successful sign-ins using the device code authentication flow that are infrequent for a specific user and location. This flow is often targeted by attackers attempting to bypass MFA or perform device phishing, as it requires the user to manually authorize the device on a separate platform.
This rule detects potential credential stuffing or brute force attacks against a SonicWall VPN device. It identifies scenarios where a single source IP experiences multiple failed authentication attempts within a 15-minute window, followed by at least one successful authentication on the same destination host.
This rule detects scenarios where a new user account is created (Event ID 4720) and is subsequently logged into (Event ID 4624) within a 30-minute window. This behavior can indicate an adversary creating a backdoor or service account for persistence or lateral movement, followed by immediate usage of that account.
Detects high-frequency state changes in authentication events for a single account within a short time window. This type of 'flapping' behavior, where an account repeatedly toggles between different authentication statuses (e.g., success and failure) on one or more hosts, can be an indicator of brute force attempts, credential stuffing, or misconfigured automated authentication services.
Detects sign-in events using 'deviceCode' authentication or single-factor authentication via mobile/desktop clients where the device identifier has not been seen in the previous 30 days. This pattern can indicate an adversary using a new device to access an account, potentially utilizing stolen sessions or bypassing MFA.
This rule detects scenarios where a new user account is created (Event ID 4720) and is subsequently logged into (Event ID 4624) within a 30-minute window. This behavior can indicate an adversary creating a backdoor or service account for persistence or lateral movement, followed by immediate usage of that account.
Detects potential password spraying activity characterized by a high number of distinct IP addresses failing authentication for a specific user, followed shortly by a successful authentication for that same user from a geographic location outside the United Kingdom.
This rule identifies anomalous SonicWall VPN login attempts by tracking successful logins over a rolling 30-day baseline. It alerts when a user successfully authenticates from an IP address not previously seen in their baseline activity, specifically during off-hours (00:00 to 05:00).
This rule identifies Service Principals in Microsoft Entra ID that have successfully authenticated after a long period of dormancy (defined as 90 days or more). Reactivation of dormant service principals may indicate that an adversary is attempting to revive a persistent access method or abuse credentials that were previously set aside.
Detects a new-device Okta sign-in followed by three or more failed Admin Console authentication attempts originating from a different device/IP context, consistent with privilege escalation using a stolen AiTM session token.
Detects successful sign-ins using the device code authentication flow that are infrequent for a specific user and location. This flow is often targeted by attackers attempting to bypass MFA or perform device phishing, as it requires the user to manually authorize the device on a separate platform.
This rule monitors for potentially malicious activities involving Azure AD Connect synchronization accounts. It flags anomalous sign-in events (e.g., interactive sign-ins or sign-ins originating from unauthorized IP addresses) and tracks when these sync accounts are granted privileged roles within the environment.
This rule monitors for potentially malicious activities involving Azure AD Connect synchronization accounts. It flags anomalous sign-in events (e.g., interactive sign-ins or sign-ins originating from unauthorized IP addresses) and tracks when these sync accounts are granted privileged roles within the environment.
Detects non-interactive sign-ins (refresh-token usage) for Microsoft Purview Communication Compliance reviewer accounts (Administrator, Analyst, or Investigator roles) that originate from IP addresses not observed for the user in the previous 21 days. This behavior is indicative of potential token theft or session hijacking attempting to bypass multi-factor authentication.
This rule detects 'impossible travel' activity performed by users assigned to sensitive Microsoft 365 Communication Compliance roles. It monitors Azure Sign-in logs for successful authentication events occurring within a short timeframe (1 hour) from multiple distinct geographic locations (countries) or different autonomous system numbers (ASNs). This behavior is characteristic of an adversary utilizing stolen session tokens or compromised credentials to access protected administrative functions.
Detects non-interactive sign-ins (refresh-token usage) for Microsoft Purview Communication Compliance reviewer accounts (Administrator, Analyst, or Investigator roles) that originate from IP addresses not observed for the user in the previous 21 days. This behavior is indicative of potential token theft or session hijacking attempting to bypass multi-factor authentication.
Detects non-interactive sign-in events using specific Microsoft application IDs (Intune for Education, Intune portal) to access Microsoft Graph that do not have a corresponding successful or failed Conditional Access policy record. This suggests potential circumvention of Conditional Access policies or service-level activity bypassing standard authentication auditing.
Detects non-interactive sign-in events using specific Microsoft application IDs (Intune for Education, Intune portal) to access Microsoft Graph that do not have a corresponding successful or failed Conditional Access policy record. This suggests potential circumvention of Conditional Access policies or service-level activity bypassing standard authentication auditing.
Detects sign-in events using 'deviceCode' authentication or single-factor authentication via mobile/desktop clients where the device identifier has not been seen in the previous 30 days. This pattern can indicate an adversary using a new device to access an account, potentially utilizing stolen sessions or bypassing MFA.
This rule identifies potential post-Adversary-in-the-Middle (AiTM) session hijacking by correlating suspicious initial authentication events (e.g., AiTM indicators, unusual behavioral flags) with subsequent successful sign-ins originating from known residential proxies or anonymization VPN providers within a 24-hour window.
Page 48 of 80