Splunk Security

@SplunkSecurity
35 followers31,507 downloads1,688 copies11 likes90,253 views

2,515 detections

This detection searches for Windows Defender ASR block events. ASR is a feature of Windows Defender Exploit Guard that prevents actions and apps that are typically used by exploit-seeking malware to infect machines. ASR rules are applied to processes and applications. When a process or application attempts to perform an action that is blocked by an ASR rule, an event is generated. This detection searches for ASR block events that are generated when a process or application attempts to perform an action that is blocked by an ASR rule. Typically, these will be enabled in block most after auditing and tuning the ASR rules themselves. Set to TTP once tuned.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0034
The following analytic detects multiple attempts to stop or delete services on a system using `net.exe` or `sc.exe`. It leverages Endpoint Detection and Response (EDR) telemetry, focusing on process names and command-line executions within a one-minute window. This activity is significant as it may indicate an adversary attempting to disable security or critical services to evade detection and further their objectives. If confirmed malicious, this could lead to the attacker gaining persistence, escalating privileges, or disrupting essential services, thereby compromising the system's security posture.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0034
This analytic detects the creation of files without extensions in critical Windows folders like "System32\drivers" and "syswow64\drivers". This activity is significant as it may indicate the presence of destructive malware, such as HermeticWiper, which drops driver components in these directories. If confirmed malicious, this behavior could lead to severe system compromise, including boot sector wiping, resulting in potential data loss and system inoperability.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
1034
The following analytic detects a modification in the Windows registry to disable Windows Defender PUA protection by setting PUAProtection to 0. This detection leverages data from the Endpoint.Registry datamodel, focusing on registry path changes related to Windows Defender. Disabling PUA protection is significant as it reduces defenses against Potentially Unwanted Applications (PUAs), which, while not always malicious, can negatively impact user experience and security. If confirmed malicious, this activity could allow an attacker to introduce adware, browser toolbars, or other unwanted software, potentially compromising system integrity and user productivity.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0034
This rule detects modifications to the Windows registry that disable the Windows Defender real-time signature delivery feature. Specifically, it looks for changes to the `RealtimeSignatureDelivery` registry value under `*\Windows Defender\Signature Updates\` to `0x00000000`. Disabling this feature can prevent Windows Defender from receiving timely malware definitions, thereby reducing its effectiveness and potentially allowing attackers to bypass malware detection, leading to system compromise and persistent threats.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0034
The following analytic detects modifications to the registry related to the disabling of autostart functionality for certain antivirus products, such as Kingsoft and Tencent. Malware like ValleyRAT may alter specific registry keys to prevent these security tools from launching automatically at startup, thereby weakening system defenses. By monitoring changes in the registry entries associated with antivirus autostart settings, this detection enables security analysts to identify attempts to disable protective software. Detecting these modifications early is critical for maintaining system integrity and preventing further compromise by malicious actors.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0034
The analytic detects the execution of programs initiated by `forfiles.exe`. This command is typically used to run commands on multiple files, often within batch scripts. The detection leverages data from Endpoint Detection and Response (EDR) agents, focusing on process creation events where `forfiles.exe` is the parent process. This activity is significant because `forfiles.exe` can be exploited to bypass command line execution protections, making it a potential vector for malicious activity. If confirmed malicious, this could allow attackers to execute arbitrary commands, potentially leading to unauthorized access or further system compromise.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0034
The following analytic detects excessive usage of the forfiles.exe process, which is often indicative of post-exploitation activities. The detection leverages data from Endpoint Detection and Response (EDR) agents, focusing on process execution logs that include process GUID, process name, and parent process. This activity is significant because forfiles.exe can be abused to execute commands on multiple files, a technique used by ransomware like Prestige. If confirmed malicious, this behavior could allow attackers to enumerate files, potentially leading to data exfiltration or further malicious actions.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0034
The analytic detects the use of the `[Adsisearcher]` type accelerator in PowerShell Script Block Logging (EventCode=4104) to query Active Directory for domain organizational units. This activity indicates potential reconnaissance efforts by adversaries to gain situational awareness of the domain structure, which could lead to further exploitation, such as privilege escalation or lateral movement within the network.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0034
The following analytic identifies the use of Ldifde.exe, a command-line utility for creating, modifying, or deleting LDAP directory objects. This detection leverages data from Endpoint Detection and Response (EDR) agents, focusing on process execution and command-line arguments. Monitoring Ldifde.exe is significant because it can be used by attackers to manipulate directory objects, potentially leading to unauthorized changes or data exfiltration. If confirmed malicious, this activity could allow an attacker to gain control over directory services, escalate privileges, or access sensitive information within the network.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0034
Page 210 of 252