Detections

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

743 detections

The following queries pivot from an IP address assigned to a machine to the relevant machine or logged-on users.
To read more about it, check out this post: https://techcommunity.microsoft.com/t5/What-s-New/Advanced-hunting-now-includes-network-adapters-information/m-p/224402#M74.
Query #1: get machines that have used a given local IP address at a given time - as configured on their network adapters.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
008
Detects instances where an FTP service on an OpenCanary honeypot has had a login attempt. This indicates an adversary is attempting to access or interact with the honeypot's services, which could be part of reconnaissance, initial access, or lateral movement activities.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
1 year ago
0021
Detects connections from routable IPs to an RDP listener. Which is indicative of a publicly-accessible RDP service.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
1 year ago
001
The analytic detects the creation of a Kubernetes NodePort service, which exposes a service to the external network. It identifies this activity by monitoring Kubernetes Audit logs for the creation of NodePort services. This behavior is significant for a SOC as it could allow an attacker to access internal services, posing a threat to the Kubernetes infrastructure's integrity and security. If confirmed malicious, this activity could lead to data breaches, service disruptions, or unauthorized access to sensitive information.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0040
Detects instances where a VNC service on an OpenCanary node has had a connection attempt. This indicates an adversary attempting to connect to a VNC service, likely for remote access or reconnaissance.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0021
Detects inbound network connections to ports 5985 or 5986, which are commonly used for PowerShell Remoting (WinRM). This rule specifically looks for EventID 5156 (Windows Filtering Platform Connection) with a LayerRTID of 44, indicating an inbound connection.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
3030
This detection excludes known namped pipes accessible remotely and notify on newly observed ones, may help to detect lateral movement and remote exec using named pipes
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
000
Detects basic PowerShell Remoting (WinRM) by monitoring for network inbound connections to ports 5985 OR 5986
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
000
Page 36 of 36