Fields names for Sigma rules (sofilter) #12203
-
Version2.4.3 Installation MethodSecurity Onion ISO image Descriptionconfiguration Installation TypeStandalone Locationon-prem with Internet access Hardware SpecsExceeds minimum requirements CPU20 RAM64 Storage for /315GB Storage for /nsm15TB Network Traffic Collectionspan port Network Traffic Speeds1Gbps to 10Gbps StatusYes, all services on all nodes are running OK Salt StatusNo, there are no failures LogsNo, there are no additional clues DetailI'm tuning some Playbook rules to keep only relevant alerts. I've read the documentation on using sofilter and I have successfully configured other rules. To use the proper fields name, I usually refer to the original Sigma configuration and I use the same field names in the custom filter. I need to filter the field named 'event_data.process.parent.command_line' (named like this in the alert dashboard) to make sure that the following value is ignored: 'sh -c /usr/bin/crontab -l 2>/dev/null' For this particuliar case, the field I need is not present in the Sigma configuration and it seems like I can't find the correct field name for 'event_data.process.parent.command_line' I've tried 'ParentCommandLine' but it doesn't work. So my question is: How can I find the correct field name ? Is there a field mapping reference somewhere, or a general rule of thumb to convert the field names ? Thank you Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
This is due to the way we map values within the docker container. We're working on a new feature called 'Detections'. Once that goes live it should be easier to add your own mappings / override existing field mappings. |
Beta Was this translation helpful? Give feedback.
This is due to the way we map values within the docker container. We're working on a new feature called 'Detections'. Once that goes live it should be easier to add your own mappings / override existing field mappings.