Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
3,750 detections
Filters
Last updated
All Time
Detection languages
2,544
328
307
253
149
Contributors
953
720
641
297
173
Categories
1,245
994
880
773
476
Platforms
2,850
1,449
1,229
356
73
Products / Services
10,683
9,759
6,695
4,421
3,750
MITRE Techniques
1,096
989
950
912
820
CVEs
17
6
2
1
1
IDS Classtypes
9
4
3
2
2
IDS Protocols
21
1
Detects high-frequency, diverse Microsoft Graph API requests initiated by an identity, indicative of automated reconnaissance or enumeration of the cloud environment. The rule tracks requests across multiple categories such as organization settings, user/group identities, privilege information, application configurations, and resource access within a 30-minute window.
This rule monitors email, SMS, and voice logs for potential phishing attempts targeting user credentials. It specifically looks for social engineering lures related to passkey, SSO, or MFA updates that express urgency or imply service expiration, often masquerading as IT support communications.
Detects anomalous access patterns to Microsoft 365 SaaS applications where a single user session interacts with three or more specific portal applications (such as 'OfficeHome', 'My Apps', 'My Profile') within a five-minute window. This behavior may indicate an adversary attempting to map the environment or interact with multiple integrated services shortly after gaining access.
Detects high-frequency access to multiple sensitive Microsoft Graph API paths (users, groups, applications, directoryRoles, servicePrincipals, etc.) from a single identity within a short timeframe. This pattern is indicative of automated reconnaissance or enumeration of the cloud environment's identity and application landscape.
Detects a sequence of events indicative of an Adversary-in-the-Middle (AiTM) attack, specifically 'NovaCookies'. The rule identifies a phishing email lure (DocuSign/SharePoint-themed) received by a user, followed within a 6-hour window by an anomalous Microsoft 365 sign-in from that same user. The anomalous sign-in is defined by either risk flags or conditional access failure, suggesting potential replay of a captured session cookie.
Detects a potential Adversary-in-the-Middle (AiTM) attack sequence by correlating OneDrive/SharePoint document sharing email lures with subsequent successful Microsoft 365 sign-ins from unusual locations or user agents within a short time window. This activity often indicates session cookie theft and MFA bypass.
Detects phishing emails purportedly from Docusign that contain malicious links which redirect users through legitimate identity provider domains (e.g., login.microsoftonline.com, accounts.google.com) before landing on non-trusted infrastructure. This redirect-chain pattern is indicative of NovaCookies Adversary-in-the-Middle (AiTM) delivery, used to facilitate credential or session cookie theft.
Detects phishing attempts leveraging SendGrid infrastructure to send emails that impersonate well-known financial brands. The detection looks for emails with authentication checks passing (SPF/DKIM/DMARC) where the sender domain is suspicious (e.g., .asia or .com not matching the brand) and the volume of such messages suggests an automated campaign.
This rule detects potentially malicious messages sent via Microsoft Teams that contain keywords related to passkey enrollment or SSO updates, which are common social engineering tactics used in phishing campaigns to trick users into compromising their account credentials or security settings.
Detects high-volume, multi-endpoint enumeration activity against the Microsoft Graph API, involving a high frequency of requests across sensitive tenant resources (users, groups, applications, roles, mailboxes, etc.). This behavior is consistent with post-compromise reconnaissance by an adversary attempting to map the environment.
Detects a sequence of events starting with a user signing in via the OAuth device code flow, followed immediately by mailbox item enumeration and sending of email. This pattern is characteristic of attackers who use device code phishing to steal tokens, subsequently using those tokens to access mailboxes and send malicious emails from the compromised account.
This rule detects phishing emails attempting to impersonate Apple or Find My services by monitoring for specific sender display names and subject lines. It specifically flags messages originating from personal email providers like Gmail and iCloud that do not belong to the legitimate apple.com domain, which is a tactic often associated with device-recovery lures used in phishing campaigns.
This rule detects anomalous backend activity associated with phishing kits, specifically monitoring for the dispatch of SMS or WhatsApp messages containing lure links. It identifies logs indicative of automated message dispatch (via send_sms_apix.log or WhatsApp Business API calls), filters for successful delivery indicators while excluding known error states, and verifies the presence of specific message components like recipient details and malicious templates.
Detects Workday self-service banking detail changes occurring shortly after suspicious mailbox reconnaissance activities, such as searching for payroll-related terms or accessing sensitive documents. This behavior is indicative of a payroll diversion fraud scheme following an Adversary-in-the-Middle (AiTM) session hijacking attack.
Detects phishing emails associated with the Mirage2FA campaign, which utilize HTML smuggling via .htm, .xhtml, or .svg attachments, often disguised as voicemail or contract-related documents. The rule also accounts for social engineering lures involving QR codes.
Detects anomalous access to email items containing financial keywords (e.g., payroll, invoice, banking) via 'MailItemsAccessed' events, characteristic of potential data collection following an AiTM (Adversary-in-the-Middle) account takeover. The rule identifies accounts accessing multiple financial emails without performing traditional BEC indicators such as creating inbox rules, modifying mailbox forwarding, or sending outbound phishing emails, which helps isolate silent exfiltration attempts.
Detects Microsoft 365 / Entra ID sign-in events where the reported client application is Microsoft Outlook but the User-Agent string is inconsistent with Outlook's standard Edge-based WebView. This behavioral discrepancy often indicates the use of automated HTTP clients to replay stolen session tokens in Adversary-in-the-Middle (AiTM) phishing campaigns, allowing attackers to maintain authenticated access for reconnaissance and data collection.
Detects the creation or modification of O365 inbox rules designed to move incoming emails to the 'Deleted Items' folder, delete messages, or mark them as read. This behavior is a common indicator of an adversary attempting to hide phishing lures, security alerts, or C2 communications within a compromised mailbox.
This rule detects high-confidence phishing emails that were delivered to either the Inbox or Junk folder. It explicitly filters out messages that have been explicitly allowed by organization-level policies, user-level actions, or specific safe-sender bypass mechanisms, ensuring the alert focuses on malicious emails that bypassed standard security filters without an authorized exception.
This rule detects high-confidence phishing emails that were delivered to either the Inbox or Junk folder. It explicitly filters out messages that have been explicitly allowed by organization-level policies, user-level actions, or specific safe-sender bypass mechanisms, ensuring the alert focuses on malicious emails that bypassed standard security filters without an authorized exception.
Detects potentially malicious OAuth device code sign-ins by identifying sign-in events that exhibit anomalous characteristics, such as atypical geographic locations, rare client-application combinations, unmanaged/noncompliant device status, or elevated risk signals associated with the account. This detection helps identify account compromise or malicious OAuth consent activity often associated with 'EvilTokens' or device-code phishing attacks.
Page 56 of 179