Closed 13621 closed 2 weeks ago
While working on a fix for this I stumbled upon another issue on which it is dependent, tracked here: https://github.com/SigmaHQ/pySigma/issues/277
A PR to fix it is awaiting feedback, once this is solved I will start working on this one.
The PR has now been merged and I have a fix ready here. It causes a breaking change due to the way this backend handles correlations, so I'll have to wait for the next pySigma version to be released before submitting the PR.
The PR has now been merged and I have a fix ready here. It causes a breaking change due to the way this backend handles correlations, so I'll have to wait for the next pySigma version to be released before submitting the PR.
Thank you for your fix 👍 Just tested this with the code I gave above. The errors seem to be resolved now with both formats working fine. You're right though, I had to build pySigma from the main branch so that the tests would pass. Would love a new release of pySigma so that this fix can be merged.
Thank you for your feedback, nice to know it works as expected on your side too. I've opened the PR and hopefully the fix will be released soon https://github.com/SigmaHQ/pySigma-backend-elasticsearch/pull/82.
Hi, I love this project and especially like the recent introduction of correlations. I wanted to try out different formats for the ESQL backend, and I think I found a bug related to the
siem_rule
andkibana_ndjson
formats.When converting a correlation rule to these formats in the ESQL backend, I get
AttributeError: 'dict' object has no attribute 'split'
. I used this code to test it out:I found that I don't get this error when converting a normal rule to
siem_rule
orkibana_ndjson
format, or converting a correlation rule to the default format (just the query) with the ESQL backend. PySigma and the elasticsearch backend are both on the most recent version (0.11.12 and 1.1.2 respectively).