Added mappings for some logsources using the SigmaHQ taxanomy. #496
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
|
recheck |
|
With the release of 2.4.70 yesterday, we have reworked all of the Sigma backend mappings, and it is now available to be overridden via the web interface. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi
I have added some mappings for logsources using the Sigma Taxanomy. This should correspond well with the rules made by the Sigma communtiy using more generic syntax instead of specifying by different event id's from Sysmon.
I have tested this mapping in 2.4.20 and the conversion of rules worked fine.
I have also added some experimental rules which uses elasticagent instead of sysmon, the conversion of the rules works but I havent evaluated the impact of using elasticagent instead of Sysmon.
e.g. elasticagents monitoring of network connections seems to be more thorough than Sysmon EventID 3.
I have commented these rules out but left them in the code as inspiration.
Cheers
//Tobias