Replies: 1 comment
-
These are field mapping issues. Sigma rules are written using generic fields like "cmdLine" - and then we convert them into an EQL query to run against Elasticsearch. As part of that conversion process, we apply field mappings, so cmdline is transformed to We are still working on the field mappings - I have added the rules you noted to my list to review. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Version
2.4.70
Installation Method
Security Onion ISO image
Description
configuration
Installation Type
Distributed
Location
on-prem with Internet access
Hardware Specs
Meets minimum requirements
CPU
8
RAM
24
Storage for /
175
Storage for /nsm
350
Network Traffic Collection
span port
Network Traffic Speeds
Less than 1Gbps
Status
Yes, all services on all nodes are running OK
Salt Status
No, there are no failures
Logs
No, there are no additional clues
Detail
My network consists of both Windows and MacOS.
A number of sigma rule e.g.
Execution Of Non-Existing File
Qakbot Regsvr32 Calc Pattern
Uninstall Sysinternals Sysmon
Potential Reconnaissance For Cached Credentials Via Cmdkey.EXE
All of them are Windows
logsource:
category: process_creation
product: windows
How do I stop them firing for the MacOS Clients? I'm guessing its filtering on process_creation and not checking product.
Any ideas
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions