Replies: 2 comments 2 replies
-
Can you write these rules as Sigma within Detections? |
Beta Was this translation helpful? Give feedback.
0 replies
-
We probably could rewrite our rules as Sigma but we'd then have to rewrite our backend to ingest Sigma - each of our Elastalerts sends a POST request to an endpoint for our SOAR platform. It's a good idea though - just something that may take a while to rewrite. |
Beta Was this translation helpful? Give feedback.
2 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.
-
Our organization relies on a set of custom Elastalert rules that use a POST request to an alerting/incident triage tool. We have DevOps pipelines that will push the rules from a Git repository to the "/opt/so/rules/elastalert/rules/custom/" folder in test or production SO environments.
Testing these rules has always been painful. We developed a CLI app that uses the npm elasticdump package to copy index data between prod and dev SO environments. The app can then use SSH and issue the "elastalert-test-rule" to test a particular rule and make sure there are no syntax errors.
This is all too clunky, however, and there are too many manual steps for an analyst/developer to take. What we would love to see in Security Onion is a GUI similar to what's already there for Suricata rules where you can just create a new rule and have it auto-deploy in 15 minutes. If the syntax is bad, the GUI would tell you before the rule deployed and broke the so-elastalert container...
Beta Was this translation helpful? Give feedback.
All reactions