Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
2,831 detections
Filters
Last updated
All Time
Detection languages
1,374
495
363
281
175
Contributors
848
453
393
252
188
Categories
20,440
11,814
5,871
5,145
4,864
2,831
Platforms
1,448
916
693
670
264
Products / Services
994
700
613
469
216
MITRE Techniques
1,239
911
484
481
388
CVEs
6
5
2
1
1
IDS Classtypes
15
10
6
5
3
IDS Protocols
39
Detects instances where AI agents are activated through external communication channels like webhooks, email, or chat, and the provided payload includes potentially malicious imperative instructions (e.g., 'delete', 'execute', 'send credentials'). The detection logic excludes activity originating from trusted, allow-listed internal sources to reduce false positives.
Detects adversarial attempts to infer whether specific records were used in an AI model's training set by analyzing raw prediction confidence scores and identifying suspicious query patterns such as near-duplicate submissions or systematic sweeps.
This rule detects high volumes of near-identical, incrementally-varied queries directed at an AI model API. This behavior is indicative of a black-box adversarial optimization loop, where an attacker attempts to infer model vulnerabilities, bypass safety filters, or perform model evasion by observing how slight input variations change model responses.
This rule detects high volumes of near-identical, incrementally-varied queries directed at an AI model API. This behavior is indicative of a black-box adversarial optimization loop, where an attacker attempts to infer model vulnerabilities, bypass safety filters, or perform model evasion by observing how slight input variations change model responses.
This rule detects high volumes of near-identical, incrementally-varied queries directed at an AI model API. This behavior is indicative of a black-box adversarial optimization loop, where an attacker attempts to infer model vulnerabilities, bypass safety filters, or perform model evasion by observing how slight input variations change model responses.
This rule detects high volumes of near-identical, incrementally-varied queries directed at an AI model API. This behavior is indicative of a black-box adversarial optimization loop, where an attacker attempts to infer model vulnerabilities, bypass safety filters, or perform model evasion by observing how slight input variations change model responses.
This rule detects high volumes of near-identical, incrementally-varied queries directed at an AI model API. This behavior is indicative of a black-box adversarial optimization loop, where an attacker attempts to infer model vulnerabilities, bypass safety filters, or perform model evasion by observing how slight input variations change model responses.
This rule detects high volumes of near-identical, incrementally-varied queries directed at an AI model API. This behavior is indicative of a black-box adversarial optimization loop, where an attacker attempts to infer model vulnerabilities, bypass safety filters, or perform model evasion by observing how slight input variations change model responses.
This rule detects anomalous behavior in AI agent tool invocations, specifically monitoring for high volumes of tool calls, high costs associated with token consumption, or suspicious tool interactions following a flagged indirect prompt injection. This behavior is indicative of potential resource exhaustion (denial of service) or abusive agent behavior as defined by the MITRE ATLAS framework for AI security.
This rule detects anomalous behavior in AI agent tool invocations, specifically monitoring for high volumes of tool calls, high costs associated with token consumption, or suspicious tool interactions following a flagged indirect prompt injection. This behavior is indicative of potential resource exhaustion (denial of service) or abusive agent behavior as defined by the MITRE ATLAS framework for AI security.
Detects Microsoft Entra ID sign-in events where a user authenticates from a known residential proxy ASN, matching the user's historical geography but using a new, unrecognized device fingerprint. This behavior is indicative of session token replay attacks, where an adversary uses stolen session cookies to bypass standard authentication.
Detects instances where a Google Cloud Config Connector (KCC) service account performs a SetIamPolicy operation that grants high-privilege roles (roles/owner or roles/resourcemanager.organizationAdmin) at the organization or folder scope. This activity often indicates an out-of-band configuration change, a compromised CI/CD pipeline, or an unauthorized escalation, as legitimate KCC changes should be tracked via GitOps records.
Detects unauthorized or suspicious use of Google Cloud Config Connector (KCC) service accounts to apply high-privilege IAM roles ('roles/owner' or 'roles/resourcemanager.organizationAdmin') at the Organization or Folder scope. This rule monitors for 'SetIamPolicy' API calls where the principal is identified as a KCC-related service account, flagging potential exploitation of KCC's authority to grant excessive permissions.
This rule detects anomalous, high-volume activity from a single user account interacting with known public generative AI platforms (e.g., ChatGPT, Copilot, Claude). It uses a threshold-based approach on CloudAppEvents logs to identify potential reconnaissance or bulk information gathering activities which could signify unauthorized use or automated data scraping via AI interfaces.
Detects instances where a single user account exhibits an anomalously high frequency of requests to public generative-AI platforms within a one-hour window, potentially indicating automated reconnaissance or data staging activities using AI tools.
Detects GitHub repository actions (git.clone, oauth_authorization.create, repo.download_zip) from actor IPs not seen for that user in the prior 30 days, requiring either 3+ actions or activity across 2+ distinct repositories from the new IP within the same day. Aggregating to burst/multi-repo behavior (rather than alerting on a single new-IP event) filters out one-off false positives from travel, VPNs, or dynamic IP reassignment while still surfacing sustained anomalous access patterns consistent with account compromise or bulk exfiltration.
Detects instances where a user grants high-privilege permissions (Mail.Read, Files.ReadWrite.All, offline_access) to an OAuth application within 24 hours of a risky sign-in event. This pattern is commonly observed in AiTM (Adversary-in-the-Middle) or consent-phishing attacks designed to establish persistent access to cloud resources.
Detects instances where a user account successfully registers or joins a device to Entra ID (Azure AD) immediately after performing a sign-in operation that was flagged with a medium or high-risk level. This pattern may indicate an adversary is attempting to enroll a malicious device to bypass conditional access policies or establish persistence in the environment using compromised credentials.
Detects a suspicious volume of cloud resource deletions occurring within a short 15-minute window, specifically targeting multiple storage accounts and SQL database/server instances. This behavior is indicative of a malicious actor or an automated script attempting to disrupt business operations or destroy data.
Detects anomalous bursts of deletion activity targeting Azure Site Recovery and Backup resources, including management locks and backup policies. This behavior is consistent with an adversary attempting to inhibit system recovery capabilities, often a precursor to destructive activities such as ransomware deployment. The rule also correlates this activity with the deletion of other critical infrastructure components like databases or storage accounts.
Detects instances where a user account registers a new Multi-Factor Authentication (MFA) method (such as TOTP or Authenticator app) shortly (within 30 minutes) after a high-risk or potentially anomalous sign-in event. This pattern is commonly associated with adversary-in-the-middle (AiTM) phishing attacks where an attacker captures an authenticated session and uses it to enroll a secondary, attacker-controlled MFA device for persistent account access.
Page 31 of 135