You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because this rule is using the old | syntax for aggregations, it is rejected by pysigma. I suppose this is also the reason why this rule is in the unsupported directory, just like a few other rules using | aggregations.
I did not find any rules in the repository using the new correlation syntax, maybe because correlations are not yet officially and fully supported?
However, I´m following the development of pysigma and because converting correlation rules is possible now, I was curious and tried to change this rule following the correlation specification so that pysigma can convert it.
Because this attempt was successful (using Elasticsearch ESQLBackend), I wanted to ask if it is planned that the rules in the unsupported directory will be updated in the future to follow the new specification or if correlations are not yet to be used in the main rule repository.
Here is a suggestion for the updated rule using the event_count correlation:
title: Rare Service Installsid: 66bfef30-22a5-4fcd-ad44-8d81e60922aename: rare_service_installsstatus: testdescription: Detects rare service installs that only appear a few times per time frame and could reveal password dumpers, backdoor installs or other types of malicious servicesauthor: Florian Roth (Nextron Systems)date: 2017/03/08modified: 2024/05/14tags:
- attack.persistence
- attack.privilege_escalation
- car.2013-09-005
- attack.t1543.003correlation:
type: event_countrules:
- service_installsgroup-by:
- ServiceName timespan: 7dcondition:
lt: 5level: lowfalsepositives:
- Software installation
- Software updates
---
title: Service Installationsid: 1b4db7eb-4057-5ddf-91e0-36dec72071f5name: service_installsstatus: testlogsource:
product: windowsservice: systemdetection:
selection:
Provider_Name: 'Service Control Manager'EventID: 7045condition: selectionlevel: informational
The text was updated successfully, but these errors were encountered:
Hey @Mat0vu thanks for reaching out.
You are correct in your assumptions. While correlations were recently added to PySigma we still haven't announced the V2 spec (which include correlationà.
We are now in the process of adding a folder to allow for the submitting of correlation rules and as you guessed old rules in the supported using the old pipe notation will also be converted to use the new format.
Thanks for your understanding.
Will take your rule suggestion as input when the new folder is added.
Hi,
as my company is trying to move from
sigmac
topysigma
for translating our detection rules, I´m currently checking if I get the same output with the new tool.For quite some time, in our environment the following rule was used to check for rare service installs: (https://github.com/SigmaHQ/sigma/blob/master/unsupported/windows/win_system_rare_service_installs.yml)
Because this rule is using the old
|
syntax for aggregations, it is rejected by pysigma. I suppose this is also the reason why this rule is in theunsupported
directory, just like a few other rules using|
aggregations.I did not find any rules in the repository using the new correlation syntax, maybe because correlations are not yet officially and fully supported?
However, I´m following the development of
pysigma
and because converting correlation rules is possible now, I was curious and tried to change this rule following the correlation specification so thatpysigma
can convert it.Because this attempt was successful (using Elasticsearch
ESQLBackend
), I wanted to ask if it is planned that the rules in theunsupported
directory will be updated in the future to follow the new specification or if correlations are not yet to be used in the main rule repository.Here is a suggestion for the updated rule using the
event_count
correlation:The text was updated successfully, but these errors were encountered: