SigmaHQ Detections
@sigmaHQ12 followers122,473 downloads2,593 copies16 likes160,510 views
6,800 detections
Filters
Last updated
All Time
Detection languages
6,800
Categories
2,695
910
506
407
372
Platforms
5,315
505
263
204
164
Products / Services
2,051
1,570
475
423
316
MITRE Techniques
2,652
1,739
1,656
1,503
764
CVEs
19
19
19
16
10
This rule detects attempts to load malicious DLLs into the LSASS process by modifying undocumented registry keys. Specifically, it looks for modifications to 'DirectoryServiceExtPt' or 'LsaDbExtPt' registry keys that are not associated with the legitimate 'ntdsa.dll' or 'lsadb.dll' files, which are typically loaded by 'lsass.exe' on domain controllers. This technique can be used for privilege escalation, persistence, and credential access.
Detects the installation of new shim databases that attempt to patch sections of known processes for potential process injection or persistence. This rule specifically looks for modifications to the AppCompatFlags\Custom registry key where shims are typically registered, targeting common system processes.
Detects various activities associated with the 'Operation Wocao' campaign, including the use of 'checkadmin.exe', 'netsh' commands to modify firewall rules, PowerShell execution with bypass and encoded commands, scheduled task creation, and attempts to query KeePass configuration files and PuTTY sessions from the registry. These activities indicate potential privilege escalation, persistence, discovery, and defense evasion techniques used by the threat actor.
Detects the execution of GuLoader malware where a rundll32.exe process is spawned by an injected browser process (chrome.exe, firefox.exe, or msedge.exe). This behavior indicates potential malware activity, specifically GuLoader initiating network connections.
This rule detects when a user's account type is changed from 'Guest' to 'Member' within Azure Active Directory. This change signifies an elevation of privileges for the user, as 'Member' accounts typically have broader access and capabilities compared to 'Guest' accounts. Such a modification could be an indicator of an adversary attempting to gain higher privileges or establish persistence within the cloud environment.
Detects when a Privileged Identity Management (PIM) elevation request is approved or denied within Azure AD. This rule helps monitor critical administrative actions related to privilege escalation. Any approvals or denials outside of expected administrative operations should be investigated as they could indicate unauthorized privilege management or attempts to bypass security controls.
This rule detects successful sign-in attempts to Azure AD from devices that are not registered in Active Directory (non-compliant devices) and where Multi-Factor Authentication (MFA) was not required. The sign-in is also flagged as 'atRisk' by Azure AD. This scenario can indicate an adversary attempting to gain initial access or maintain persistence using compromised credentials from an unregistered device, bypassing stronger authentication controls.
This rule detects instances where a user denies a multi-factor authentication (MFA) prompt. This could indicate that an attacker has successfully obtained the user's password and is attempting to gain unauthorized access, prompting the legitimate user for MFA approval. The user's denial signals that they did not initiate the login attempt.
Identifies when an admission controller is executed in GCP Kubernetes. A Kubernetes Admission controller intercepts, and possibly modifies, requests to the Kubernetes API server. The behavior of this admission controller is determined by an admission webhook (MutatingAdmissionWebhook or ValidatingAdmissionWebhook) that the user deploys in the cluster. An adversary can use such webhooks as the MutatingAdmissionWebhook for obtaining persistence in the cluster. For example, attackers can intercept and modify the pod creation operations in the cluster and add their malicious container to every created pod. An adversary can use the webhook ValidatingAdmissionWebhook, which could be used to obtain access credentials. An adversary could use the webhook to intercept the requests to the API server, record secrets, and other sensitive information.
Detects a suspicious local successful logon event where the Logon Package is Kerberos, the remote address is set to localhost, and the target user SID is the built-in local Administrator account. This may indicate an attempt to leverage a Kerberos relay attack variant that can be used to elevate privilege locally from a domain joined limited user to local System privileges.
Page 194 of 680