Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
2,982 detections
Filters
Last updated
All Time
Detection languages
1,486
513
403
239
167
Contributors
986
658
304
198
109
Categories
916
822
673
590
452
Platforms
39,952
7,270
6,537
3,867
3,651
2,982
Products / Services
1,229
703
443
309
200
MITRE Techniques
1,053
824
459
384
348
CVEs
17
16
16
10
10
IDS Classtypes
24
7
7
4
3
IDS Protocols
49
1
This rule detects the creation of a new GitHub repository from a compromised endpoint, specifically looking for indicators of stolen credential exfiltration. The rule identifies GitHub application events where a repository is created and the raw event data contains keywords associated with credential dumping or specific campaign names like "Miasma" or "Spreading Blight". Automated exfiltration to GitHub is often fast and difficult to remediate, making prompt detection crucial. If triggered, it's recommended to revoke tokens used to create the repository and investigate the endpoint for compromise.
Identifies HTTP POST requests indicative of rogue administrator account creation patterns ('dev_xxxxxx' or 'developer_api1') used in the OptinMonster, TrustPulse, and PushEngage supply chain attack. This rule specifically looks for POST requests to WordPress user creation endpoints containing attacker-controlled account names in the URI query.
Detects bursts of Google Workspace device registrations for a single user in a short window, specifically when 3 or more devices are registered within a 1-minute interval for the same account.
This rule detects queries made within ServiceNow by accounts classified as 'Guest' or 'Unknown'. This could indicate unauthorized access or unusual activity from unprivileged or unidentifiable accounts attempting to query data within the ServiceNow environment.
This rule detects queries made within ServiceNow by accounts classified as 'Guest' or 'Unknown'. This could indicate unauthorized access or unusual activity from unprivileged or unidentifiable accounts attempting to query data within the ServiceNow environment.
Detects OAuth application registration or permission grant via Graph API
Detects bulk export of CRM customer data for collection and theft
Detects new app installations, expansions of OAuth scopes, or the addition of collaborators to Slack applications. These activities can indicate an adversary attempting to establish persistent access, escalate privileges, or exfiltrate data from Slack by leveraging malicious or compromised applications.
Okta Impossible Travel Detection
Cortex XDR
Detects when a single user successfully authenticates to Okta from two different countries within a two-hour window, indicating potential impossible travel which could be a sign of a compromised account.
Detects bulk export of Confluence wiki content
This rule looks for exposed pairs of credentials used for GitHub cloud identity federation in logs or artifacts. Leaked pairs let attackers mint tokens as your pipeline. Rotate federation settings and audit recent workflow runs.
This rule detects when a GitHub workflow branch is deleted shortly after build artifacts were downloaded. This behavior can indicate an attacker attempting to hide their tracks after exfiltrating secrets or sensitive information from build artifacts. It is crucial to preserve logs and investigate who deleted the branch. Further investigation should include questioning the user about recent software installations or clicked links, and involving the security team if the answers are unclear.
This rule detects anomalous access to cloud services, specifically Salesforce, Drift, Salesloft, HubSpot, and Marketo, that may indicate OAuth token abuse. It identifies scenarios where a high volume of actions (8 or more) occur within a short timeframe (3 hours or less) from a single IP address but with multiple unique user agents (2 or more). The detection is further refined by looking for actions related to 'Add delegated permission grant' or 'Create service principal', which are indicative of an attacker attempting to establish persistence or escalate privileges after gaining access through a compromised OAuth token.
Detects when an actor searches Slack audit logs, which could indicate an attacker attempting to understand logging capabilities or evade detection. Also detects bulk session resets initiated by an administrator, which may be a response to an account takeover or an attacker attempting to evict legitimate users from their sessions.
This rule detects the creation of Okta API tokens with broad administrative scopes (okta.users.manage, okta.factors.manage, or okta.apps.manage) by the same user multiple times within a one-hour window. This behavior can indicate an attempt to establish persistent access or bypass multi-factor authentication.
Detects use of forged web credentials for unauthorized application access
Okta MFA Push Bombing / Fatigue
Cortex XDR
Detects repeated push denials for the same user within a short timeframe, indicating an active MFA fatigue attack where an adversary is attempting to overwhelm a user with MFA requests in hopes they will eventually approve one.
Slack Canvas External Access & Tampering
Cortex XDR
Detects external users accessing internal Slack canvases and suspicious canvas deletion or access level changes. Canvases can contain sensitive runbooks, credentials, and organizational data, making these actions critical to monitor for potential data exfiltration or unauthorized access.
This rule detects suspicious GitHub workflow modifications or pushes originating from multiple distinct IP addresses within a short time frame (1 hour). It specifically looks for 'WorkflowCreated', 'WorkflowUpdated', or 'Push' actions on GitHub, and triggers if more than one such event and more than one distinct IP address are observed for a given account within an hour. This could indicate compromised credentials or unauthorized access to a GitHub account being used to manipulate CI/CD pipelines.
This rule detects potential GitHub token theft or abuse activity by identifying GitHub tokens that are used from an unusually high number of distinct IP addresses or for an unusually high number of uses within a one-hour window. Specifically, it looks for tokens with more than 5 uses and more than 2 distinct IP addresses in an hour. This behavior could indicate that a compromised token is being used by an attacker from multiple locations or in an automated fashion.
Detects successful device code flow sign-ins to the Microsoft Authentication Broker application targeting the Microsoft Graph resource, specifically when the sign-in does not originate from a trusted named location. This activity can indicate a device code phishing attempt where an attacker tricks a user into authenticating a malicious application.
Page 116 of 142