Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
345 detections
Filters
Last updated
All Time
Detection languages
193
87
18
17
15
Contributors
54
46
42
41
30
Categories
143
142
77
60
47
Platforms
238
82
37
36
22
Products / Services
66
51
49
43
27
MITRE Techniques
18,123
15,639
12,581
8,394
6,215
CVEs
5
2
2
2
1
IDS Classtypes
3
IDS Protocols
3
Detects a single GitLab token/account holding Owner-level access across an unusually large number of projects (50+), the standing-privilege condition that turned one leaked token into a 55-project supply-chain exposure.
Detects anomalous, high-frequency access to sensitive Microsoft Graph API endpoints by a single service principal or user identity. The rule flags identities that interact with five or more distinct categories of sensitive resources (e.g., users, groups, applications, sites) within a 30-minute window, suggesting automated reconnaissance or environment discovery.
Detects a single GitLab token/account holding Owner-level access across an unusually large number of projects (50+), the standing-privilege condition that turned one leaked token into a 55-project supply-chain exposure.
Detects the execution of common system administration tools (cmd, powershell, net, nltest, etc.) used to perform environment discovery or credential enumeration, specifically when targeting Domain Controllers, Active Directory objects, database credentials, or sensitive configuration files.
This rule detects rapid enumeration of Azure AD identity and configuration components by identifying a burst of specific, high-level administrative API calls (Get user flows, Get API connectors, Get identity providers, Get user attributes) within a short window. This pattern is indicative of reconnaissance activities aimed at mapping out the identity provider configuration.
This rule detects rapid enumeration of Azure AD identity and configuration components by identifying a burst of specific, high-level administrative API calls (Get user flows, Get API connectors, Get identity providers, Get user attributes) within a short window. This pattern is indicative of reconnaissance activities aimed at mapping out the identity provider configuration.
Detects a single GitLab token/account holding Owner-level access across an unusually large number of projects (50+), the standing-privilege condition that turned one leaked token into a 55-project supply-chain exposure.
Detects the execution of common system administration tools (cmd, powershell, net, nltest, etc.) used to perform environment discovery or credential enumeration, specifically when targeting Domain Controllers, Active Directory objects, database credentials, or sensitive configuration files.
This rule detects rapid enumeration of Azure AD identity and configuration components by identifying a burst of specific, high-level administrative API calls (Get user flows, Get API connectors, Get identity providers, Get user attributes) within a short window. This pattern is indicative of reconnaissance activities aimed at mapping out the identity provider configuration.
Detects a single GitLab token/account holding Owner-level access across an unusually large number of projects (50+), the standing-privilege condition that turned one leaked token into a 55-project supply-chain exposure.
This rule detects rapid enumeration of Azure AD identity and configuration components by identifying a burst of specific, high-level administrative API calls (Get user flows, Get API connectors, Get identity providers, Get user attributes) within a short window. This pattern is indicative of reconnaissance activities aimed at mapping out the identity provider configuration.
Detects the execution of common system administration tools (cmd, powershell, net, nltest, etc.) used to perform environment discovery or credential enumeration, specifically when targeting Domain Controllers, Active Directory objects, database credentials, or sensitive configuration files.
Detects the execution of common system administration tools (cmd, powershell, net, nltest, etc.) used to perform environment discovery or credential enumeration, specifically when targeting Domain Controllers, Active Directory objects, database credentials, or sensitive configuration files.
Detects the execution of SOAPHound, a .NET tool for collecting Active Directory data, using specific command-line arguments that may indicate an attempt to extract sensitive AD information.
This rule detects rapid enumeration of Azure AD identity and configuration components by identifying a burst of specific, high-level administrative API calls (Get user flows, Get API connectors, Get identity providers, Get user attributes) within a short window. This pattern is indicative of reconnaissance activities aimed at mapping out the identity provider configuration.
Detects a set of suspicious network related commands often used in recon stages
Detects a sequence of common discovery commands (ipconfig, whoami, nltest, net group, wmic) executed within a short timeframe (60 seconds) by the same process. This activity is indicative of an adversary performing internal reconnaissance to understand the environment, network, and user privileges.
Suspicious Discovery Command Execution
Cortex XDR
Detects the execution of common command-line utilities frequently used by adversaries for system, network, and account discovery after gaining initial access to a host.
Detects anomalous activity where a user account experiences access denials across a high number of distinct applications (>= 5) within a 15-minute window via Zscaler Private Access. This pattern often indicates unauthorized exploration, directory probing, or automated credential testing against enterprise resources.
Detects instances where AI coding assistants (e.g., Cursor, Claude, Copilot) are observed interacting with specific configuration or sensitive files and subsequently initiating suspicious shell commands. The rule correlates file read activity (containing keywords like 'skill', 'preflight', '.ssh', or '.aws') followed closely by execution of potentially malicious commands like 'whoami /priv', credential decoding, or registry exploration, indicating potential abuse of the assistant's context.
Detects Shai-Hulud / ChainDrop activity by correlating known malicious hashes, npm/Node/Bun execution, payload artifacts, IDE persistence, credential discovery, cloud metadata access, GitHub exfiltration, C2 domains, Ethereum RPC activity, staging files, persistence artifacts, and known IOC IP connections.
Page 5 of 17