Sigma Rules Reference

222 events across 47 providers with Sigma detection rules, 3700 rule mappings total.

Application-Error (1 event, 2 rules) #

Application - Event ID 1000 - Faulting application name: Faulting_application_name, version: version, time stamp: 0xFaulting_module_name. #
  • LSASS Process Crashed - Application - Detects Windows error reporting events where the process that crashed is LSASS (Local Security Authority Subsystem Service). This could be the cause of a provoked crash by techniques such as Lsass-Shtinkering to dump credentials.
  • Microsoft Malware Protection Engine Crash - This rule detects a suspicious crash of the Microsoft Malware Protection Engine

Application-Popup (1 event, 1 rule) #

System - Event ID 26 - Application popup: Caption : Message. #
Sysmon Application Crashed - Detects application popup reporting a failure of the Sysmon service

ESENT (4 events, 5 rules) #

Application - Event ID 216#
Ntdsutil Abuse - Detects potential abuse of ntdsutil to dump ntds.dit database
Application - Event ID 325#
Also fires on: ESENT EID 216, ESENT EID 326, ESENT EID 327
Application - Event ID 326#
Ntdsutil Abuse - Detects potential abuse of ntdsutil to dump ntds.dit database
Application - Event ID 327#
Ntdsutil Abuse - Detects potential abuse of ntdsutil to dump ntds.dit database

LsaSrv (3 events, 3 rules) #

Operational - Event ID 300 - Groups assigned to a new logon. #
Standard User In High Privileged Group - Detect standard users login that are part of high privileged groups such as the Administrator group
System - Event ID 6038 - Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. #
NTLMv1 Logon Between Client and Server - Detects the reporting of NTLMv1 being used between a client and server. NTLMv1 is insecure as the underlying encryption algorithms can be brute-forced by modern hardware.
System - Event ID 6039 - Microsoft Windows Server has detected that NTLM authentication is being used between clients and this server. #
NTLMv1 Logon Between Client and Server - Detects the reporting of NTLMv1 being used between a client and server. NTLMv1 is insecure as the underlying encryption algorithms can be brute-forced by modern hardware.

Microsoft-Windows-AppLocker (4 events, 4 rules) #

EXE and DLL - Event ID 8004 - FilePathBuffer was prevented from running. #
AppLocker Prevented Application or Script from Running - Detects when AppLocker prevents the execution of an Application, DLL, Script, MSI, or Packaged-App from running.
MSI and Script - Event ID 8007 - FilePathBuffer was prevented from running. #
AppLocker Prevented Application or Script from Running - Detects when AppLocker prevents the execution of an Application, DLL, Script, MSI, or Packaged-App from running.
Packaged app-Execution - Event ID 8022 - PackageBuffer was prevented from running. #
AppLocker Prevented Application or Script from Running - Detects when AppLocker prevents the execution of an Application, DLL, Script, MSI, or Packaged-App from running.
Packaged app-Deployment - Event ID 8025 - PackageBuffer was prevented from running. #
AppLocker Prevented Application or Script from Running - Detects when AppLocker prevents the execution of an Application, DLL, Script, MSI, or Packaged-App from running.

Microsoft-Windows-AppModel-Runtime (1 event, 1 rule) #

Admin - Event ID 201 - Created process ProcessID for application ApplicationName in package PackageName. #
Sysinternals Tools AppX Versions Execution - Detects execution of Sysinternals tools via an AppX package. Attackers could install the Sysinternals Suite to get access to tools such as psexec and procdump to avoid detection based on System paths.

Microsoft-Windows-AppXDeployment-Server (9 events, 13 rules) #

Operational - Event ID 400 - Deployment DeploymentOperation operation with target volume MountPoint on Package PackageFullName from: Path finished successfully. #
Also fires on: AppXDeployment-Server EID 401
Operational - Event ID 401 - Deployment DeploymentOperation operation with target volume MountPoint on Package PackageFullName from: Path failed with error ErrorCode. #
Also fires on: AppXDeployment-Server EID 400
Operational - Event ID 412 - error ErrorCode: Deployment of package PackageFullName was blocked by AppLocker. #
Deployment AppX Package Was Blocked By AppLocker - Detects an appx package deployment that was blocked by AppLocker policy.
Operational - Event ID 441 - The package deployment operation is blocked by the "Allow deployment operations in special profiles" policy. #
Deployment Of The AppX Package Was Blocked By The Policy - Detects an appx package deployment that was blocked by the local computer policy. The following events indicate that an AppX package deployment was blocked by a policy: - Event ID 441: The package deployment operation is blocked by the "Allow deployment operations in special profiles" policy - Event ID 442: Deployments to non-system volumes are blocked by the "Disable deployment of Windows Store apps to non-system volumes" policy." - Event ID 453: Package blocked by a platform policy. - Event ID 454: Package blocked by a platform policy.
Operational - Event ID 442 - Deployment of package PackageFullName to volume MountPoint failed because deployments to non-system volumes are blocked by the "Disable deployment of Windows Store apps... #
Deployment Of The AppX Package Was Blocked By The Policy - Detects an appx package deployment that was blocked by the local computer policy. The following events indicate that an AppX package deployment was blocked by a policy: - Event ID 441: The package deployment operation is blocked by the "Allow deployment operations in special profiles" policy - Event ID 442: Deployments to non-system volumes are blocked by the "Disable deployment of Windows Store apps to non-system volumes" policy." - Event ID 453: Package blocked by a platform policy. - Event ID 454: Package blocked by a platform policy.
Operational - Event ID 453 - Package PackageFullName is blocked by a platform policy: PolicyReason. #
Deployment Of The AppX Package Was Blocked By The Policy - Detects an appx package deployment that was blocked by the local computer policy. The following events indicate that an AppX package deployment was blocked by a policy: - Event ID 441: The package deployment operation is blocked by the "Allow deployment operations in special profiles" policy - Event ID 442: Deployments to non-system volumes are blocked by the "Disable deployment of Windows Store apps to non-system volumes" policy." - Event ID 453: Package blocked by a platform policy. - Event ID 454: Package blocked by a platform policy.
Operational - Event ID 454 - Package PackageFullName is blocked by a platform policy: PolicyReason. #
Deployment Of The AppX Package Was Blocked By The Policy - Detects an appx package deployment that was blocked by the local computer policy. The following events indicate that an AppX package deployment was blocked by a policy: - Event ID 441: The package deployment operation is blocked by the "Allow deployment operations in special profiles" policy - Event ID 442: Deployments to non-system volumes are blocked by the "Disable deployment of Windows Store apps to non-system volumes" policy." - Event ID 453: Package blocked by a platform policy. - Event ID 454: Package blocked by a platform policy.
Operational - Event ID 603 - Started deployment DeploymentOperation operation on a package with main parameter Path and Options Flags and FlagsHigh. #
Windows AppX Deployment Unsigned Package Installation - Detects attempts to install unsigned MSIX/AppX packages using the -AllowUnsigned parameter via AppXDeployment-Server events
Operational - Event ID 854 - Successfully added the following uri(s) to be processed: Path. #

Microsoft-Windows-AppxPackagingOM (1 event, 1 rule) #

Operational - Event ID 157 - The app package signature was validated for core content of the app package published by subjectName. #
Suspicious Digital Signature Of AppX Package - Detects execution of AppX packages with known suspicious or malicious signature

Microsoft-Windows-Audit-CVE (1 event, 1 rule) #

Application - Event ID 1 - Possible detection of CVE: PossibleDetectionOfCVE. #
Audit CVE Event - Detects events generated by user-mode applications when they call the CveEventWrite API when a known vulnerability is trying to be exploited. MS started using this log in Jan. 2020 with CVE-2020-0601 (a Windows CryptoAPI vulnerability. Unfortunately, that is about the only instance of CVEs being written to this log.

Microsoft-Windows-Backup (1 event, 1 rule) #

Application - Event ID 524 - The system catalog has been deleted. #
Backup Catalog Deleted - Detects backup catalog deletions

Microsoft-Windows-Bits-Client (2 events, 7 rules) #

Operational - Event ID 3 - The BITS service created a new job: jobTitle, with owner jobId. #
Operational - Event ID 16403#

Microsoft-Windows-CAPI2 (1 event, 1 rule) #

Operational - Event ID 70 - For more details for this event, please refer to the "Details" section #
Certificate Private Key Acquired - Detects when an application acquires a certificate private key

Microsoft-Windows-CertificateServicesClient-Lifecycle-System (1 event, 1 rule) #

Operational - Event ID 1007 - A certificate has been exported. #
Certificate Exported From Local Certificate Store - Detects when an application exports a certificate (and potentially the private key as well) from the local Windows certificate store.

Microsoft-Windows-CertificationAuthority (1 event, 1 rule) #

Operational - Event ID 53#
Active Directory Certificate Services Denied Certificate Enrollment Request - Detects denied requests by Active Directory Certificate Services. Example of these requests denial include issues with permissions on the certificate template or invalid signatures.

Microsoft-Windows-CodeIntegrity (14 events, 14 rules) #

Operational - Event ID 3001 - Code Integrity determined an unsigned kernel module FileNameBuffer is loaded into the system. #
CodeIntegrity - Unsigned Kernel Module Loaded - Detects the presence of a loaded unsigned kernel module on the system.
Operational - Event ID 3021 - Code Integrity determined a revoked kernel module FileNameBuffer is loaded into the system. #
CodeIntegrity - Revoked Kernel Driver Loaded - Detects the load of a revoked kernel driver
Operational - Event ID 3022 - Code Integrity determined a revoked kernel module FileNameBuffer is loaded into the system. #
CodeIntegrity - Revoked Kernel Driver Loaded - Detects the load of a revoked kernel driver
Operational - Event ID 3023 - The driver FileNameBuffer is blocked from loading as the driver has been revoked by Microsoft. #
CodeIntegrity - Blocked Driver Load With Revoked Certificate - Detects blocked load attempts of revoked drivers
Operational - Event ID 3032 - Code Integrity determined a revoked image FileNameBuffer is loaded into the system. #
CodeIntegrity - Revoked Image Loaded - Detects image load events with revoked certificates by code integrity.
Operational - Event ID 3033 - Code Integrity determined that a process (ProcessNameBuffer) attempted to load FileNameBuffer that did not meet the RequestedPolicy signing level requirements. #
CodeIntegrity - Unmet Signing Level Requirements By File Under Validation - Detects attempted file load events that did not meet the signing level requirements. It often means the file's signature is revoked or a signature with the Lifetime Signing EKU has expired. This event is best correlated with EID 3089 to determine the error of the validation.
Operational - Event ID 3034 - Code Integrity determined that a process (ProcessNameBuffer) attempted to load FileNameBuffer that did not meet the RequestedPolicy signing level requirements or violated code integrity p... #
CodeIntegrity - Unmet Signing Level Requirements By File Under Validation - Detects attempted file load events that did not meet the signing level requirements. It often means the file's signature is revoked or a signature with the Lifetime Signing EKU has expired. This event is best correlated with EID 3089 to determine the error of the validation.
Operational - Event ID 3035 - Code Integrity determined a revoked image FileNameBuffer is loaded into the system. #
CodeIntegrity - Revoked Image Loaded - Detects image load events with revoked certificates by code integrity.
Operational - Event ID 3036 - Windows is unable to verify the integrity of the file FileNameBuffer because the signing certificate has been revoked. #
CodeIntegrity - Blocked Image Load With Revoked Certificate - Detects blocked image load events with revoked certificates by code integrity.
Operational - Event ID 3037 - Code Integrity determined an unsigned image FileNameBuffer is loaded into the system. #
CodeIntegrity - Unsigned Image Loaded - Detects loaded unsigned image on the system
Operational - Event ID 3077 - Code Integrity determined that a process (Process Name) attempted to load File Name that did not meet the Requested Signing Level signing level requirements or violated code integrity p... #
CodeIntegrity - Blocked Image/Driver Load For Policy Violation - Detects blocked load events that did not meet the authenticode signing level requirements or violated the code integrity policy.
Operational - Event ID 3082 - Code Integrity determined kernel module FileNameBuffer that did not meet the WHQL requirements is loaded into the system. #
CodeIntegrity - Unmet WHQL Requirements For Loaded Kernel Module - Detects loaded kernel modules that did not meet the WHQL signing requirements.
Operational - Event ID 3083 - Code Integrity determined kernel module FileNameBuffer that did not meet the WHQL requirements is loaded into the system. #
CodeIntegrity - Unmet WHQL Requirements For Loaded Kernel Module - Detects loaded kernel modules that did not meet the WHQL signing requirements.
Operational - Event ID 3104 - Windows blocked file FileNameBuffer which has been disallowed for protected processes. #
CodeIntegrity - Disallowed File For Protected Processes Has Been Blocked - Detects block events for files that are disallowed by code integrity for protected processes

Microsoft-Windows-DHCP-Server (4 events, 4 rules) #

Operational - Event ID 1031 - [EVENT_SERVER_CALLOUT_UNHANDLED_EXCEPTION] The installed server callout .dll file has caused an exception. #
DHCP Server Error Failed Loading the CallOut DLL - This rule detects a DHCP server error in which a specified Callout DLL (in registry) could not be loaded
Operational - Event ID 1032 - [EVENT_SERVER_CALLOUT_LOAD_EXCEPTION] The installed server callout .dll file has caused an exception. The .dll file couldn't be loaded. #
DHCP Server Error Failed Loading the CallOut DLL - This rule detects a DHCP server error in which a specified Callout DLL (in registry) could not be loaded
Operational - Event ID 1033 - [EVENT_SERVER_CALLOUT_LOAD_SUCCESS] The DHCP service has successfully loaded one or more callout DLLs. #
DHCP Server Loaded the CallOut DLL - This rule detects a DHCP server in which a specified Callout DLL (in registry) was loaded
Operational - Event ID 1034 - [EVENT_SERVER_READ_ONLY_GROUP_ERROR] The DHCP service has failed to load one or more callout DLLs. #
DHCP Server Error Failed Loading the CallOut DLL - This rule detects a DHCP server error in which a specified Callout DLL (in registry) could not be loaded

Microsoft-Windows-Diagnosis-Scripted (1 event, 1 rule) #

Operational - Event ID 101 - The scripted diagnostic engine started initializing a diagnostic package located at PackagePath. #
Loading Diagcab Package From Remote Path - Detects loading of diagcab packages from a remote path, as seen in DogWalk vulnerability

Microsoft-Windows-DistributedCOM (1 event, 1 rule) #

Operational - Event ID 10001 - Unable to start a DCOM Server: param3 as param4/param5. #
Local Privilege Escalation Indicator TabTip - Detects the invocation of TabTip via CLSID as seen when JuicyPotatoNG is used on a system in brute force mode

Microsoft-Windows-DNS-Client (1 event, 6 rules) #

Operational - Event ID 3008 - DNS query is completed for the name QueryName, type QueryType, query options QueryOptions with status QueryStatus Results QueryResults. #

Microsoft-Windows-DNS-Server-Service (4 events, 4 rules) #

DNS Server - Event ID 150 - The DNS server could not load or initialize the plug-in DLL Name. #
DNS Server Error Failed Loading the ServerLevelPluginDLL - Detects a DNS server error in which a specified plugin DLL (in registry) could not be loaded
DNS Server - Event ID 770 - A DNS server plugin DLL has been loaded from location param1 on server param2. #
DNS Server Error Failed Loading the ServerLevelPluginDLL - Detects a DNS server error in which a specified plugin DLL (in registry) could not be loaded
DNS Server - Event ID 771 - The V1 plugin interface has been implemented in server level plugin DLL. #
DNS Server Error Failed Loading the ServerLevelPluginDLL - Detects a DNS server error in which a specified plugin DLL (in registry) could not be loaded
DNS Server - Event ID 6004 - The DNS server received a zone transfer request from param1 for a non-existent or non-authoritative zone param2. #
Failed DNS Zone Transfer - Detects when a DNS zone transfer failed.

Microsoft-Windows-DriverFrameworks-UserMode (3 events, 3 rules) #

Operational - Event ID 2003 - The UMDF Host Process (UMDFHostDeviceArrivalBegin.LifetimeId) has been asked to load drivers for device UMDFHostDeviceArrivalBegin.InstanceId. #
USB Device Plugged - Detects plugged/unplugged USB devices
Operational - Event ID 2100 - Received a Pnp or Power operation (UMDFHostDeviceRequest.RequestMajorCode, UMDFHostDeviceRequest.RequestMinorCode) for device UMDFHostDeviceRequest.InstanceId. #
USB Device Plugged - Detects plugged/unplugged USB devices
Operational - Event ID 2102 - Forwarded a finished Pnp or Power operation (UMDFHostDeviceRequest.RequestMajorCode, UMDFHostDeviceRequest.RequestMinorCode) to the lower driver for device UMDFHostDeviceRequest.InstanceId with status UMDFHostDeviceRequest.Status. #
USB Device Plugged - Detects plugged/unplugged USB devices

Microsoft-Windows-Eventlog (1 event, 2 rules) #

System - Event ID 104 - The LogFileCleared.Channel log file was cleared. #
  • Eventlog Cleared - One of the Windows Eventlogs has been cleared. e.g. caused by "wevtutil cl" command execution
  • Important Windows Eventlog Cleared - Detects the clearing of one of the Windows Core Eventlogs. e.g. caused by "wevtutil cl" command execution

Microsoft-Windows-IIS-Configuration (1 event, 4 rules) #

Operational - Event ID 29#

Microsoft-Windows-Iphlpsvc (1 event, 1 rule) #

System - Event ID 4100 - ISATAP router address IsatapRouter was set with status ErrorCode. #
ISATAP Router Address Was Set - Detects the configuration of a new ISATAP router on a Windows host. While ISATAP is a legitimate Microsoft technology for IPv6 transition, unexpected or unauthorized ISATAP router configurations could indicate a potential IPv6 DNS Takeover attack using tools like mitm6. In such attacks, adversaries advertise themselves as DHCPv6 servers and set malicious ISATAP routers to intercept traffic. This detection should be correlated with network baselines and known legitimate ISATAP deployments in your environment.

Microsoft-Windows-Kernel-General (1 event, 1 rule) #

System - Event ID 16 - The access history in hive HiveName was cleared updating KeysUpdated keys and creating DirtyPages modified pages. #
Critical Hive In Suspicious Location Access Bits Cleared - Detects events from the Kernel-General ETW indicating that the access bits of a hive with a system like hive name located in the temp directory have been reset. This occurs when an application tries to access a hive and the hive has not be recognized since the last 7 days (by default). Registry hive dumping utilities such as QuarksPwDump were seen emitting this behavior.

Microsoft-Windows-LDAP-Client (1 event, 1 rule) #

Debug - Event ID 30#
Potential Active Directory Reconnaissance/Enumeration Via LDAP - Detects potential Active Directory enumeration via LDAP

Microsoft-Windows-Ntfs (1 event, 1 rule) #

System - Event ID 98 - Volume DriveName (DeviceName) CorruptionActionState. #
Volume Shadow Copy Mount - Detects volume shadow copy mount via Windows event log

Microsoft-Windows-NTLM (2 events, 2 rules) #

Operational - Event ID 8001 - NTLM client blocked audit: Audit outgoing NTLM authentication traffic that would be blocked. #
Potential Remote Desktop Connection to Non-Domain Host - Detects logons using NTLM to hosts that are potentially not part of the domain.
Operational - Event ID 8002 - NTLM server blocked audit: Audit Incoming NTLM Traffic that would be blocked. #
NTLM Logon - Detects logons using NTLM, which could be caused by a legacy source or attackers

Microsoft-Windows-PowerShell (2 events, 193 rules) #

Operational - Event ID 4103 - Payload Context: ContextInfo User Data: UserData. #
Operational - Event ID 4104 - Creating Scriptblock text (MessageNumber of MessageTotal). 160 rules#
Show 160 rules

Microsoft-Windows-Security-Auditing (63 events, 1346 rules) #

Security - Event ID 4611 - A trusted logon process has been registered with the Local Security Authority. #
Register new Logon Process by Rubeus - Detects potential use of Rubeus via registered new trusted logon process
Security - Event ID 4616 - The system time was changed. #
Unauthorized System Time Modification - Detect scenarios where a potentially unauthorized application or user is modifying the system time.
Security - Event ID 4624 - An account was successfully logged on. #
Also fires on: Security-Auditing EID 4625, Security-Auditing EID 4776
Security - Event ID 4625 - An account failed to log on. #
Security - Event ID 4634 - An account was logged off. #
User Logoff Event - Detects a user log-off activity. Could be used for example to correlate information during forensic investigations
Security - Event ID 4647 - User initiated logoff. #
User Logoff Event - Detects a user log-off activity. Could be used for example to correlate information during forensic investigations
Security - Event ID 4648 - A logon was attempted using explicit credentials. #
Suspicious Remote Logon with Explicit Credentials - Detects suspicious processes logging on with explicit credentials
Security - Event ID 4649 - A replay attack was detected. #
Replay Attack Detected - Detects possible Kerberos Replay Attack on the domain controllers when "KRB_AP_ERR_REPEAT" Kerberos response is sent to the client
Security - Event ID 4656 - A handle to an object was requested. #
Security - Event ID 4657 - A registry value was modified. #
Security - Event ID 4658 - The handle to an object was closed. #
Potential Secure Deletion with SDelete - Detects files that have extensions commonly seen while SDelete is used to wipe files.
Security - Event ID 4661 - A handle to an object was requested. #
Security - Event ID 4662 - An operation was performed on an object. #
Also fires on: Security-Auditing EID 5136, Security-Auditing EID 5137
  • AD Object WriteDAC Access - Detects WRITE_DAC access to a domain object
  • Active Directory Replication from Non Machine Account - Detects potential abuse of Active Directory Replication Service (ADRS) from a non machine account to request credentials.
  • Potential AD User Enumeration From Non-Machine Account - Detects read access to a domain user from a non-machine account
  • Mimikatz DC Sync - Detects Mimikatz DC sync security events
  • DPAPI Domain Backup Key Extraction - Detects tools extracting LSA secret DPAPI domain backup key from Domain Controllers
  • Potential Kerberos Coercion by Spoofing SPNs via DNS Manipulation - Detects modifications to DNS records in Active Directory where the Distinguished Name (DN) contains a base64-encoded blob matching the pattern "1UWhRCAAAAA...BAAAA". This pattern corresponds to a marshaled CREDENTIAL_TARGET_INFORMATION structure, commonly used in Kerberos coercion attacks. Adversaries may exploit this to coerce victim systems into authenticating to attacker-controlled hosts by spoofing SPNs via DNS. It is one of the strong indicators of a Kerberos coercion attack,. where adversaries manipulate DNS records to spoof Service Principal Names (SPNs) and redirect authentication requests like CVE-2025-33073. Please investigate the user account that made the changes, as it is likely a low-privileged account that has been compromised.
  • WMI Persistence - Security - Detects suspicious WMI event filter and command line event consumer based on WMI and Security Logs.
Security - Event ID 4663 - An attempt was made to access an object. #
  • Azure AD Health Monitoring Agent Registry Keys Access - This detection uses Windows security events to detect suspicious access attempts to the registry key of Azure AD Health monitoring agent. This detection requires an access control entry (ACE) on the system access control list (SACL) of the following securable object HKLM\SOFTWARE\Microsoft\Microsoft Online\Reporting\MonitoringAgent.↳ also fires on: Security-Auditing EID 4656
  • Azure AD Health Service Agents Registry Keys Access - This detection uses Windows security events to detect suspicious access attempts to the registry key values and sub-keys of Azure AD Health service agents (e.g AD FS). Information from AD Health service agents can be used to potentially abuse some of the features provided by those services in the cloud (e.g. Federation). This detection requires an access control entry (ACE) on the system access control list (SACL) of the following securable object: HKLM:\SOFTWARE\Microsoft\ADHealthAgent. Make sure you set the SACL to propagate to its sub-keys.↳ also fires on: Security-Auditing EID 4656
  • Processes Accessing the Microphone and Webcam - Potential adversaries accessing the microphone and webcam in an endpoint.↳ also fires on: Security-Auditing EID 4656, Security-Auditing EID 4657
  • ISO Image Mounted - Detects the mount of an ISO image on an endpoint
  • LSASS Access From Non System Account - Detects potential mimikatz-like tools accessing LSASS from non system account↳ also fires on: Security-Auditing EID 4656
  • WCE wceaux.dll Access - Detects wceaux.dll access while WCE pass-the-hash remote command execution on source host↳ also fires on: Security-Auditing EID 4656
  • Service Registry Key Read Access Request - Detects "read access" requests on the services registry key. Adversaries may execute their own malicious payloads by hijacking the Registry entries used by services. Adversaries may use flaws in the permissions for Registry keys related to services to redirect from the originally specified executable to one that they control, in order to launch their own code when a service starts.
  • Potential Secure Deletion with SDelete - Detects files that have extensions commonly seen while SDelete is used to wipe files.↳ also fires on: Security-Auditing EID 4656, Security-Auditing EID 4658
  • File Access Of Signal Desktop Sensitive Data - Detects access to Signal Desktop's sensitive data files: db.sqlite and config.json. The db.sqlite file in Signal Desktop stores all locally saved messages in an encrypted SQLite database, while the config.json contains the decryption key needed to access that data. Since the key is stored in plain text, a threat actor who gains access to both files can decrypt and read sensitive messages without needing the users credentials. Currently the rule only covers the default Signal installation path in AppData\Roaming. Signal Portable installations may use different paths based on user configuration. Additional paths can be added to the selection as needed.
  • Potentially Suspicious AccessMask Requested From LSASS - Detects process handle on LSASS process with certain access mask↳ also fires on: Security-Auditing EID 4656
  • SysKey Registry Keys Access - Detects handle requests and access operations to specific registry keys to calculate the SysKey↳ also fires on: Security-Auditing EID 4656
  • Sysmon Channel Reference Deletion - Potential threat actor tampering with Sysmon manifest and eventually disabling it↳ also fires on: Security-Auditing EID 4657
  • Suspicious Teams Application Related ObjectAcess Event - Detects an access to authentication tokens and accounts of Microsoft Teams desktop application.
  • Windows Defender Exclusion Registry Key - Write Access Requested - Detects write access requests to the Windows Defender exclusions registry keys. This could be an indication of an attacker trying to request a handle or access the object to write new exclusions in order to bypass security.↳ also fires on: Security-Auditing EID 4656
Security - Event ID 4673 - A privileged service was called. #
  • User Couldn't Call a Privileged Service 'LsaRegisterLogonProcess' - The 'LsaRegisterLogonProcess' function verifies that the application making the function call is a logon process by checking that it has the SeTcbPrivilege privilege set. Possible Rubeus tries to get a handle to LSA.
  • Potential Privileged System Service Operation - SeLoadDriverPrivilege - Detects the usage of the 'SeLoadDriverPrivilege' privilege. This privilege is required to load or unload a device driver. With this privilege, the user can dynamically load and unload device drivers or other code in to kernel mode. This user right does not apply to Plug and Play device drivers. If you exclude privileged users/admins and processes, which are allowed to do so, you are maybe left with bad programs trying to load malicious kernel drivers. This will detect Ghost-In-The-Logs (https://github.com/bats3c/Ghost-In-The-Logs) and the usage of Sysinternals and various other tools. So you have to work with a whitelist to find the bad stuff.
Security - Event ID 4674 - An operation was attempted on a privileged object. #
SCM Database Privileged Operation - Detects non-system users performing privileged operation os the SCM database
Security - Event ID 4688 - A new process has been created. 1167 rules#
Also fires on: Sysmon EID 1
Show 1167 rules