Detections

Explore public detection logic contributed by the community across SIEM and rule languages.

38 detections

KQL Query from file: Storm 1811 SE Attack Detection
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
135137
KQL Query from file: DocuShield - NRT Anti-Impersonation Email Purge
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
5061
This query visualises total emails with Phish (BEC) Impersonation detections by Detection Technology over time
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0043
This query visualises total emails with Phish (BEC) Impersonation detections by Detection Technology
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0031
This query visualises total emails with Phish (BEC) - Impersonation detections over time.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0027
This query visualises the amount of phish emails that are quarantined, summarized daily by the detection method
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1021
This query helps reviewing count of phish detections done by spoof detection methods
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
5096
'This detection uses Windows security events to look for users reading the local Device Identity Key (Machine Key).
This information can be correlated with other events for additional context and get to use-cases where a
machine key with a transport key together can be used to impersonate an Entra ID joined or registered machine.
Reference: https://o365blog.com/post/deviceidentity/'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0035
This query visualises total emails with Phish detections over time summarizing the data daily by various Phish Detection technologies/controls
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2031
This query helps to find threats using display name impersonation for users not already protected with User Impersonation
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0028
This query helps reviewing malicious email detections by detection methods
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2021
In this detection approach, we correlate email from non-prevalent senders in the organization with impersonation intents
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0018
This query helps reviewing count of spoof and impersonation detections done per sender IP
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0014
This query helps reviewing Phish detections done by some of the most frequent detection technologies in the last 7 days
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1023
The analytic detects a suspicious computer account name change in Active Directory. It leverages Event ID 4781, which logs account name changes, to identify instances where a computer account name is changed to one that does not end with a '$'. This behavior is significant as it may indicate an attempt to exploit CVE-2021-42278 and CVE-2021-42287, which can lead to domain controller impersonation and privilege escalation. If confirmed malicious, this activity could allow an attacker to gain elevated privileges and potentially control the domain.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0043
The analytic identifies emails claiming to be sent from a domain similar to one you are monitoring for potential abuse. It leverages email header data, specifically the sender's address, and cross-references it with a lookup table of known domain permutations generated by the "ESCU - DNSTwist Domain Names" search. This activity is significant as it can indicate phishing attempts or brand impersonation, which are common tactics used in social engineering attacks. If confirmed malicious, this could lead to unauthorized access, data theft, or reputational damage.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
1039
This rule detects the creation of a named pipe using `cmd.exe` or `powershell.exe` by looking for specific command-line arguments. The presence of `echo`, `>` and `\\.\pipe\` in the command line indicates an attempt to create or interact with a named pipe. This activity can be associated with privilege escalation techniques, where an attacker might use named pipes for inter-process communication to elevate privileges.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
1022
Page 2 of 2