Splunk Security

@SplunkSecurity
35 followers31,482 downloads1,576 copies11 likes89,203 views

2,496 detections

The following analytic detects suspicious modifications to the sdclt.exe registry, a technique often used to bypass User Account Control (UAC). It leverages data from Endpoint Detection and Response (EDR) agents, focusing on specific registry paths and values associated with sdclt.exe. This activity is significant because UAC bypasses can allow attackers to execute payloads with elevated privileges without user consent. If confirmed malicious, this could lead to unauthorized code execution, privilege escalation, and potential persistence within the environment, posing a severe security risk.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0036
The following analytic detects suspicious process access by spoolsv.exe, potentially indicating exploitation of the PrintNightmare vulnerability (CVE-2021-34527). It leverages Sysmon EventCode 10 to identify when spoolsv.exe accesses critical system files or processes like rundll32.exe with elevated privileges. This activity is significant as it may signal an attempt to gain unauthorized privilege escalation on a vulnerable machine. If confirmed malicious, an attacker could achieve elevated privileges, leading to further system compromise, persistent access, or unauthorized control over the affected environment.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0036
The following analytic detects the execution of msbuild.exe from a non-standard path. It leverages data from Endpoint Detection and Response (EDR) agents, focusing on process execution logs that deviate from typical msbuild.exe locations. This activity is significant because msbuild.exe is commonly abused by attackers to execute malicious code, and running it from an unusual path can indicate an attempt to evade detection. If confirmed malicious, this behavior could allow an attacker to execute arbitrary code, potentially leading to system compromise and further malicious activities.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0036
The following analytic detects the execution of renamed instances of msbuild.exe. It leverages data from Endpoint Detection and Response (EDR) agents, focusing on process names and original file names within the Endpoint data model. This activity is significant because msbuild.exe is a legitimate tool often abused by attackers to execute malicious code while evading detection. If confirmed malicious, this behavior could allow an attacker to execute arbitrary code, potentially leading to system compromise, data exfiltration, or further lateral movement within the network.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
1136
This analytic identifies instances where `wmiprvse.exe` spawns `msbuild.exe`. This behavior is unusual and indicates potential misuse of a COM object or a Living Off The Land (LOLBAS) technique. `msbuild.exe` is typically spawned by `devenv.exe` during legitimate Visual Studio use, not by `wmiprvse.exe`. If confirmed malicious, this could indicate an attacker executing arbitrary code or scripts, potentially leading to system compromise or further malicious activities.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
1036
The analytic identifies the use of `sqlite3` querying the MacOS preferences to determine the original URL from which a package was downloaded. This detection leverages data from Endpoint Detection and Response (EDR) agents, focusing on process names and command-line executions involving `LSQuarantine`. This activity is significant as it is commonly associated with MacOS adware and other malicious software. If confirmed malicious, this behavior could indicate an attempt to track or manipulate downloaded packages, potentially leading to further system compromise or persistent adware infections.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0036
The following analytic detects the process of logging off a user through the use of the quser and logoff commands. By monitoring for these commands, the analytic identifies actions where a user session is forcibly terminated, which could be part of an administrative task or a potentially unauthorized access attempt. This detection helps identify potential misuse or malicious activity where a user’s access is revoked without proper authorization, providing insight into potential security incidents involving account management or session manipulation.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0036
This detection identifies an Active Directory access-control list (ACL) modification event, specifically focusing on changes that apply deny permissions to prevent enumeration of object permissions. Such modifications can be used by adversaries for persistence or to hide malicious objects within Active Directory by making them harder to discover.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0036
This detection identifies when an Active Directory Group Policy is deleted using the Group Policy Management Console. Deleting Group Policy Objects (GPOs) can be a legitimate administrative action, but it can also be used by adversaries to remove security controls, disable logging, or clean up traces of their activity. Monitoring for GPO deletions is crucial for maintaining the integrity of an Active Directory environment.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0036
This rule detects when the owner of an Active Directory object is updated. Changing an object's owner grants full control over that object, which can be a significant privilege escalation or a precursor to hiding an AD object. The rule specifically looks for EventCode 5136 in Windows Security Event Logs, filtering for changes in the 'owner' attribute.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
2 years ago
0036
Page 193 of 250