databricks-industry-solutions / rules-engine-microbenchmark

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

image

CLOUD POC

Rules Engine Microbenchmark

Contact Author: lipyeow.lim@databricks.com

Use Cases

Personas: security engineers, software architects

  1. A microbenchmark for evaluating rules engine implementation on top of Databricks Lakehouse.

Rules engines have wide applicability in both cybersecurity and observability domains:

  1. Detection engine in an XDR-like scenario - typically a few thousand rules. Some rules to be applied at 5m, 15m, 60m, 24h periodicity
  2. Auto-disposition engine in an XDR/SOAR-like scenario - applied to alerts to auto-disposition known true positive or false positive conditions
  3. Alerting for fusion-center fraud detection or other fusion analytics.
  4. An engine for regular threat hunting campaigns

Reference Architecture using Rules Engines in Cybersecurity Operations

image

Scope

  1. Users can test their rules engine implementation ideas by modifying and using the microbenchmark notebook
  2. Users can modify the cost estimation notebook to perform cost estimates of their rules engine implementation.

© 2023 Databricks, Inc. All rights reserved. The source in this notebook is provided subject to the Databricks License [https://databricks.com/db-license-source]. All included or referenced third party libraries are subject to the licenses set forth below.

library description license source
Durable rules Rete's algorithm for inferencing MIT https://github.com/jruizgit/rules

Getting started

Although specific solutions can be downloaded as .dbc archives from our websites, we recommend cloning these repositories onto your databricks environment. Not only will you get access to latest code, but you will be part of a community of experts driving industry best practices and re-usable solutions, influencing our respective industries.

add_repo

To start using a solution accelerator in Databricks simply follow these steps:

  1. Clone solution accelerator repository in Databricks using Databricks Repos
  2. Attach the RUNME notebook to any cluster and execute the notebook via Run-All. A multi-step-job describing the accelerator pipeline will be created, and the link will be provided. The job configuration is written in the RUNME notebook in json format.
  3. Execute the multi-step-job to see how the pipeline runs.
  4. You might want to modify the samples in the solution accelerator to your need, collaborate with other users and run the code samples against your own data. To do so start by changing the Git remote of your repository to your organization’s repository vs using our samples repository (learn more). You can now commit and push code, collaborate with other user’s via Git and follow your organization’s processes for code development.

The cost associated with running the accelerator is the user's responsibility.

Project support

Please note the code in this project is provided for your exploration only, and are not formally supported by Databricks with Service Level Agreements (SLAs). They are provided AS-IS and we do not make any guarantees of any kind. Please do not submit a support ticket relating to any issues arising from the use of these projects. The source in this project is provided subject to the Databricks License. All included or referenced third party libraries are subject to the licenses set forth below.

Any issues discovered through the use of this project should be filed as GitHub Issues on the Repo. They will be reviewed as time permits, but there are no formal SLAs for support.

About

License:Other


Languages

Language:Python 100.0%