-
Hello, everyone. I've been trying for a few days to create a playbook that allows me to generate alerts when authentication fails on any operating system, be it linux, windows, mac or other.
The objective of this playbook is failed authentications, not only of ssh, but of various types. Initially I thought of keywords, such as Failed login, invalid user, authentication failure. But I didn't get any results. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hey @Mav1814 I suggest you give the docs a read to understand the basics of Sigma rules. Then you'll have a more accurate and informed question to ask. Check it out here and the getting started To give you an over simplified answer. The logsource:
category: process_creation
product: windows Which according to the taxonomy by default it means that it maps to Sysmon EID 1 and Security Log 4688. So make sure to map it correctly. Read this for the default taxonomy meanings. Second part of your rule is the detection section which is using an non supported feature which is the Its best to give the docs a read as they have actual examples on how to use and write sigma rules :) Hope this answer your question and feel free to open another discussion if you have further questions |
Beta Was this translation helpful? Give feedback.
Hey @Mav1814
I suggest you give the docs a read to understand the basics of Sigma rules. Then you'll have a more accurate and informed question to ask. Check it out here and the getting started
To give you an over simplified answer.
The
logsource
needs to be mapped to an actually existing log. For example this rule is using the following log sourceWhich according to the taxonomy by default it means that it maps to Sysmon EID 1 and Security Log 4688. So make sure to map it correctly. Read this for the default taxonomy meanings.
Second part of your rule is the detection section which is using an non supported feature which is the