Skip to content

Confluent Sigma v1.2.0

Choose a tag to compare

@wlaforest wlaforest released this 06 Sep 21:04
· 48 commits to master since this release
6d8f35c

v1.2.0 Release Notes

Following are enhancements with the 1.2.0 release of Confluent Sigma. Thanks Michael Peacock (@michaelpeacock) @0x4b6169 and Will LaForest (@wlaforest)

JSON traversal with field mappings

Contributed by Kai Herrera @0x4b6169

Motivation

Previously field mappings were only flat. So the token in the sigma field mapping could only correspond to a top level JSON field. Any dot notation would be taken as part of the corresponding field in the source stream data so for instance

fieldmappings:
  dst_ip: id.resp_h
  dst_port: id.resp_p
  network_protocol: proto
  src_ip: id.orig_h
  src_port: id.orig_p

would work for a source event of

{
  "id.orig_h":"192.168.1.10",
  "id.orig_p":50477,
  "id.resp_h":"192.168.1.1",
  "id.resp_p":53,
  "proto":"udp"
}

but NOT for

{
  "id": {
    "orig_h":"192.168.1.10",
    "orig_p":50477,
    "resp_h":"192.168.1.1",
    "resp_p":53
  },
  "proto":"udp"
}

Solution

In order to references nested fields one can now use a JSON Path notation for JSON data. The field mapping would now become

fieldmappings:
  dst_ip: $.id.resp_h
  dst_port: $.id.resp_p
  network_protocol: proto
  src_ip: $.id.orig_h
  src_port: $.id.orig_p

The current requirements is that the mapped field must start at the root and thus $ will always start the mapped value.

Support client callback handler for IAM auth

Motivation

The Confluent Sigma project only supported SASL/SCRAM authentication and did not allow for someone to pass in a sasl.client.callback.handler.class. This meant, for instance, one could not setup authentication with AWS MSK.

Enhancement

One can now pass this in. Here is an example set of properties that can be included in the sigma properties

security.protocol=SASL_SSL
sasl.jaas.config=software.amazon.msk.auth.iam.IAMLoginModule required;
sasl.client.callback.handler.class=software.amazon.msk.auth.iam.IAMClientCallbackHandler
sasl.mechanism=AWS_MSK_IAM

Added support for all transformation

Motivation

Sigma rules have the concept of the all transformation. This changes how to interpret the value match tokes from an implicit or to an and. This was not yet supported but was requested by a user

Enhancement

The all transformation syntax is sigma is now supported.

Other

Various bug fixes, performance improvements, and patches in response to CVEs in dependent libraries.