Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
2,832 detections
Filters
Last updated
All Time
Detection languages
1,375
495
363
281
175
Contributors
848
453
393
252
188
Categories
20,456
11,839
5,876
5,155
4,865
2,832
Platforms
1,449
916
693
670
264
Products / Services
994
701
613
469
216
MITRE Techniques
1,240
912
484
482
388
CVEs
6
5
2
1
1
IDS Classtypes
15
10
6
5
3
IDS Protocols
39
Detects high-frequency, multi-action data access events through the Microsoft Graph API, indicative of automated exfiltration of Exchange, SharePoint/OneDrive, and Teams data. This behavior is consistent with an adversary using stolen OAuth access tokens to perform bulk enumeration and extraction of sensitive cloud-hosted data.
Detects when a user registers or adds a new device to Microsoft Entra ID (Azure AD) that has not been previously seen used by that user within the last 7 days. This behavior can indicate an adversary attempting to enroll an unauthorized device to bypass MFA or maintain persistent access.
Detects high-frequency S3 object upload activity (PutObject/CompleteMultipartUpload) originating from the Rclone tool, a common indicator of potential data exfiltration to cloud storage.
This rule detects potentially malicious outbound email activity sent through Microsoft Graph or Exchange APIs using unknown or infrequently seen client applications. It identifies scenarios where these applications send emails containing financial keywords (e.g., 'invoice', 'wire transfer'), which is a common indicator of Business Email Compromise (BEC) and 'EvilTokens' style mail-vault activity where attackers intercept or inject themselves into existing financial threads.
Detects anomalous privilege reconnaissance activity where an account queries Microsoft Graph API endpoints (such as directory roles or member/transitive member lists) multiple times in a short window, which may indicate a compromised account attempting to enumerate Global or Exchange Administrator role memberships.
Detects high-frequency, multi-action data access events through the Microsoft Graph API, indicative of automated exfiltration of Exchange, SharePoint/OneDrive, and Teams data. This behavior is consistent with an adversary using stolen OAuth access tokens to perform bulk enumeration and extraction of sensitive cloud-hosted data.
This rule monitors Office 365 SharePoint file operations and search queries for patterns indicative of automated discovery and exfiltration of sensitive content. It specifically identifies high-frequency search queries involving wildcard parameters used in SharePoint content indexing, which may suggest an adversary is systematically crawling or enumerating organizational documents.
Detects high-volume or multi-mailbox activity in Exchange Online, indicative of automated mailbox collection or unauthorized bulk data access via Graph or REST APIs. The rule monitors for a threshold of operations across multiple mailboxes or high event counts originating from specific API clients.
This rule detects potentially malicious, automated enumeration of Microsoft Graph API endpoints. It monitors for high volumes of requests (>= 8 within a 15-minute window) that utilize multiple OData pagination, filtering, and search parameters such as $top, $skip, $skiptoken, $count, /delta, and /search. Such activity is often indicative of automated reconnaissance, data scraping, or unauthorized bulk enumeration of cloud directory resources.
Detects individual access events to sensitive Microsoft Graph control-plane endpoints, including directory roles, role management, authentication methods, applications, service principals, and OAuth permissions. This rule is designed to be paired with a broader correlation rule to identify potential reconnaissance or persistence activities involving high-privilege configuration changes.
This rule detects successful sign-in attempts to Azure AD (Entra ID) using the Device Code authentication protocol. Device Code flow allows users to sign in to input-constrained devices by using a browser on another device. While legitimate for smart TVs, IoT devices, or CLI tools, this flow is frequently abused by attackers to perform phishing or bypass MFA by tricking users into authorizing an application.
This rule detects suspicious cloud user activity by identifying a single user account engaging in diverse, multi-stage actions (Authentication, MFA updates, Reconnaissance, and Exfiltration) originating from a high number of distinct source IP addresses. This behavioral pattern is indicative of a compromised account where an adversary is rotating IPs while performing a coordinated, multi-stage attack sequence.
Detects the use of the OAuth device code authentication flow in Azure AD/Entra ID sign-in events. This flow is frequently abused by attackers who use vishing or SMS phishing pretexts to trick users into authorizing a device login, enabling the attacker to obtain a valid session token without direct credential harvesting or cookie theft.
Detects sign-in activity to the 'Office Home' portal from an unmanaged, non-compliant device, followed by authentication to sensitive cloud services like SharePoint Online, OneDrive, or Microsoft Graph. This pattern often indicates a potential session hijacking or post-compromise activity where an attacker uses an unmanaged device to access enterprise data via cloud application discovery.
Detects a multi-stage cloud attack sequence involving a sign-in anomaly, modification of user authentication methods (e.g., registering an attacker-controlled device), reconnaissance using Microsoft Graph API, and subsequent abnormal data access/download, typically observed in Storm-3121 and Storm-3032 activities.
Detects unauthorized attempts to manipulate cgroup files (e.g., cgroup.procs) within Kubernetes pods using kubectl exec/attach sessions. This technique is often associated with SPIRE attestation spoofing or container escape attempts where an attacker attempts to influence process management or isolation constraints from within the container via the Kubernetes API.
Detects anomalous, high-frequency access to multiple distinct Microsoft Graph API endpoints (e.g., users, groups, applications) by a single user within a short timeframe, which is indicative of tenant-wide reconnaissance following identity compromise.
Detects anomalous, systematic enumeration of multiple Microsoft Graph API resource categories (e.g., users, groups, applications, sites) by a single identity, IP, or application within a short time window. This activity often indicates an adversary performing discovery or reconnaissance against the M365 tenant environment.
Detects anomalous sign-in behavior following a successful device code authentication. The rule identifies instances where a successful device code login is immediately followed by a sign-in session using a different IP address or device name for the same account, indicating potential session theft or adversary-in-the-middle phishing activity.
Detects process creation events containing command-line arguments indicative of an OAuth 2.0 device code flow, commonly used in consent phishing or device code phishing attacks to hijack account access via a malicious OAuth application registration.
Detects a suspicious sequence of events where a user initiates a device code authorization flow, immediately followed by a Microsoft Authentication Broker sign-in using the 'sso_reload=true' parameter. This pattern is indicative of an attacker hijacking the device code authorization process to gain unauthorized access to a user's session.
Page 53 of 135