Official sigma yaml syntax can be found here: https://github.com/SigmaHQ/sigma/wiki/Specification
Confluent Sigma will parser the entire sigma model but some fields have no impact on functionality (metadata fields) and some syntax is not yet supported.
id
related
status
description
author
references
logsource.category
logsource.definition
fields
falsepositives
level
tags
title
- Currently this field is used for the record key when the sigma rules are loaded with the cli. If a rule with the same title is published it will be considered to be a replacement of the prexisting one.logsource
product
- Confluent Sigma allows you to configure a filter to only use sigma rules with a specific product tagsigma.rule.filter.product
service
- Confluent Sigma allows you to configure a filter to only use sigma rules with a specific product tagsigma.rule.filter.service
detection
- Used to specify what matches this sigma rule. More details on what is supported for thedetection
field below.timeframe
- Specifies the window of time that the condition should be matches against. If thecondition
does have acount()
this will be ignorecondition
- used to specify how to combine the detection identifiers
detection
syntax
Confluent Sigma supports both Lists and Maps. As per the specificaiton lists are logically ORed and Maps are logically ANDed. More details can be found in the Sigma spec
Value modifiers are used to transform how a record value is interpreted in detection process. Currently we do NOT support chaining the modifiers with multiple pipes.
Supported value modifiers
contains
endswith
startswith
re
Unsupported value modifiers
all
base64
base64offset
utf16le
utf16be
utf16