Detections

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

743 detections

This KQL Query focuses on summarising the number of devices attempting to connect to exposed servers, categorised by vendor, by decoding their MAC addresses. This information can help you to identify unexpected devices vendors, detect virtual devices or correlate specific manufacturers with known threats.
avatar
Sergio Albea@Sergio_Albea
avatar
01 | 🇨🇭 Swiss Cyber Hunters
1 year ago
7079
This hunting rule searches for incoming ADWS connections on Domain Controllers from IP Addresses that cannot be linked to Microsoft Defender for Endpoint (MDE) onboarded devices. It aims to detect enumeration activities using ADWS from unmanaged or unknown devices, which might bypass typical monitoring tools.
avatar
Robbe Van den Daele@RobbeVdDaele
avatar
Detections.ai Community
1 year ago
2067
Identifies devices that have been observed as being directly exposed to the public internet. This is based on Microsoft Defender for Endpoint's device discovery capabilities. Such devices may be at higher risk of attack and should be reviewed to ensure the exposure is intentional and properly secured.
avatar
Rica Grande@cbrarkitect
avatar
Detections.ai Community
1 year ago
4384
This detection identifies network traffic to or from IP addresses known to be associated with command and control (C2) infrastructure or active exploitation in recent SharePoint vulnerability campaigns. Communication with these IPs is a strong indicator of either an attempted attack or an existing compromise.
avatar
R W@shiftyroot
avatar
Detections.ai Community
1 year ago
0025
Microsoft Releases Guidance on Exploitation of SharePoint Vulnerability (CVE-2025-53770)
Josh Grimes@Grimbo
avatar
Detections.ai Community
1 year ago
5446
KQL Query from file: Hunting Exposed JDWP
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
5359
KQL Query
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
184165
KQL Query from file: Sniffing Out UNC3944 on Teams
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
80111
KQL Query
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
90103
KQL Query from file: External Attack Surface Monitoring KQL
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
13090
KQL Query
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
3082
KQL Query from file: Mitigating security risks in MCP implementations
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
4075
KQL Query from file: DefenderXDR Medusa Ransomware Detection
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
5070
KQL Query from file: Endpoint SMB exposed on Public Internet
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
6169
KQL Query from file: Enhanced Cloudflare Phishing Email Detections
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
4041
KQL Query
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
4038
KQL Query
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
2030
The analytic identifies anomalous inbound network traffic volumes from processes within containerized workloads. It leverages Network Performance Monitoring metrics collected via an OTEL collector and pulled from Splunk Observability Cloud. The detection compares recent metrics (tcp.bytes, tcp.new_sockets, tcp.packets, udp.bytes, udp.packets) over the last hour with the average over the past 30 days. This activity is significant as it may indicate unauthorized data reception, potential breaches, vulnerability exploitation, or malware propagation. If confirmed malicious, it could lead to command and control installation, data integrity damage, container escape, and further environment compromise.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0044
'Discover all critical ports from a list having rules like 'Any' for sourceIp, which means that they are opened to everyone. Critial ports should not be opened to everyone, and should be filtered.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
160178
This query helps you design client firewall rules based on data stored within DeviceNetworkEvents. Folder paths are alias'ed to help represent the
files making or receiving network connections without dealing with duplication from path variance due to different root drive letter or user profile
association.
To make the report easy to read, inbound remote IP addresses are not calculated by default (this can be changed by setting the value of IncludeInboundRemoteIPs to true).
Also, the ephemeral range is defaulted to 49152 to help eliminate false detections.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1089
'Query detects potential lateral movement within a network by identifying when an RDP connection (EventID 4624, LogonType 10) is made to an initial system, followed by a subsequent RDP connection from that system to another, using the same account within a 60-minute window.
To reduce false positives, it excludes scenarios where the same account has made 5 or more connections to the same set of computers in the previous 7 days. This approach focuses on highlighting unusual RDP behaviour that suggests lateral movement, which is often associated with attacker tactics during a network breach.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
4075
Page 34 of 36