Browse Rules

Search and filter across all detection sources

142 rules

chronicle low yara-l

Network Traffic To Specific Country

Identify network traffic based on target country

sagan informational other

[SOPHOS] Malicious outbound network traffic blocked

[SOPHOS] Malicious outbound network traffic blocked

sagan informational other

[SOPHOS] Malicious outbound network traffic blocked

[SOPHOS] Malicious outbound network traffic blocked

sagan informational other

[VEEAM] Global Network Traffic Rules Deleted

[VEEAM] Global Network Traffic Rules Deleted

sagan informational other

[SOPHOS] Network Traffic Protection cleaned up a threat

[SOPHOS] Network Traffic Protection cleaned up a threat

yara unknown yara

network_traffic_njRAT [malware]

sagan informational other

[SOPHOS] Malicious inbound network traffic blocked from a remote computer

[SOPHOS] Malicious inbound network traffic blocked from a remote computer

sagan informational other

[SOPHOS] Network Traffic Protection could not clean up a threat

[SOPHOS] Network Traffic Protection could not clean up a threat

yara unknown yara

sniff_lan [capabilities]

Sniff Lan network traffic

sentinel low kql

Global Network Traffic Rules Deleted

Detects when a global network traffic rule is deleted in Veeam Backup & Replication. This might indicate unauthorized removal of critical components.

chronicle low yara-l

Suspicious ASN

Identify network traffic based on a specific ASN

sigma medium sigma

Kerberos Network Traffic RC4 Ticket Encryption

Detects kerberos TGS request using RC4 encryption which may be indicative of kerberoasting

splunk unknown spl

Prohibited Network Traffic Allowed

The following analytic detects instances where network traffic, identified by port and transport layer protocol as prohibited in the "lookup_interesting_ports" table, is allowed. It uses the Network_Traffic data model to cross-reference traffic data against predefined security policies. This activity is significant for a SOC as it highlights potential misconfigurations or policy violations that could lead to unauthorized access or data exfiltration. If confirmed malicious, this could allow attac

sentinel medium kql

Detect Windows Allow Firewall Rule Addition/Modification

This analytic rule detects any registry value creation or modification of Windows firewall registry keys to allow network traffic. This could be an indication of defense evasion by an adversary to allow network traffic to/from a compromised host.

splunk unknown spl

Network Traffic to Active Directory Web Services Protocol

The following analytic identifies network traffic directed to the Active Directory Web Services Protocol (ADWS) on port 9389. It leverages network traffic logs, focusing on source and destination IP addresses, application names, and destination ports. This activity is significant as ADWS is used to manage Active Directory, and unauthorized access could indicate malicious intent. If confirmed malicious, an attacker could manipulate Active Directory, potentially leading to privilege escalation, un

elastic-protections high eql

Potential Network Traffic Tunneling via Proxychains

This rule identifies the use of proxychains to potentially tunnel network traffic. Attackers can leverage proxychains to establish hidden communication channels and gain unauthorized access to internal resources, facilitating data exfiltration or lateral movement via proxychains while evading direct connection blocking.

sigma medium sigma

Flush Iptables Ufw Chain

Detect use of iptables to flush all firewall rules, tables and chains and allow all network traffic

splunk unknown spl

Hosts receiving high volume of network traffic from email server

The following analytic identifies hosts receiving an unusually high volume of network traffic from an email server. It leverages the Network_Traffic data model to sum incoming bytes to clients from email servers, comparing current traffic against historical averages and standard deviations. This activity is significant as it may indicate data exfiltration by a malicious actor using the email server. If confirmed malicious, this could lead to unauthorized data access and potential data breaches,

mdecrevoisier high sigma

DNS hosts file modified

Detects scenarios where an attacker attempts to modify the Hosts file to perform DNS interception and/or redirect network traffic.

splunk unknown spl

Detect Remote Access Software Usage Traffic

The following analytic detects network traffic associated with known remote access software applications, such as AnyDesk, GoToMyPC, LogMeIn, and TeamViewer. It leverages Palo Alto traffic logs mapped to the Network_Traffic data model in Splunk. This activity is significant because adversaries often use remote access tools to maintain unauthorized access to compromised environments.

sigma medium sigma

Potential Hello-World Scraper Botnet Activity

Detects network traffic potentially associated with a scraper botnet variant that uses the "Hello-World/1.0" user-agent string.

sigma medium sigma

Google Full Network Traffic Packet Capture

Identifies potential full network packet capture in gcp. This feature can potentially be abused to read sensitive data from unencrypted internal traffic.

elastic low eql

Spike in Network Traffic

A machine learning job detected an unusually large spike in network traffic. Such a burst of traffic, if not caused by a surge in business activity, can be due to suspicious or malicious activity. Large-scale data exfiltration may produce a burst of network traffic; this could also be due to unusually large amounts of reconnaissance or enumeration traffic. Denial-of-service attacks or traffic floods may also produce such a surge in traffic.

sentinel medium kql

Remote Desktop Network Brute force (ASIM Network Session schema)

'This detection identifies RDP application network traffic and filters any source/destination pair generating more than 25 events hard threshold.'

sentinel medium kql

DCOM Lateral Movement

This detection looks for cases of close-time proximity between incoming network traffic on RPC/TCP, followed by the creation of a DCOM object, followed by the creation of a child process of the DCOM object. The query first identifies incoming network traffic over RPC/TCP, followed by the creation of a DCOM object (process) within 2 seconds, followed by the creation of a child process of this DCOM object.