This repository contains sample detection rules and dashboards for use within Chronicle Security Operations.
Rules within the community directory were created by the Chronicle Security team and members of the Chronicle user community. These rules take advantage of the latest YARA-L syntax, provide a starter set of rules that can be used with Chronicle's entity graph as well as for other use cases or as inspiration for new use cases.
Rules within the soc_prime_rules directory were created by SOC Prime and made available to Chronicle Customers.
Before deploying any rules, using Chronicle's test rule functionality is considered a best practice and provides the opportunity for users to tune rules to their environment before creating alerts for them.
Dashboard YAML files can be
imported into Chronicle
dashboards using the Add - Import Dashboard capability found next to the Personal Dashboards or Shared Dashboards
section of the UI. The intent of this is to provide sample dashboards that can serve as templates, inspiration or
starting points for your own dashboards and can be modified as you see fit.
Rules can be created within your Chronicle instance by using the Rules Editor. Simply download the rule from the repository and copy the content of the rule to the rule editor when creating a new rule.
To automate rule creation, APIs are available to create/update/delete rules.
Detailed instructions can be found in your Chronicle instance under documentation.
Interested in contributing to this project? We'd love to hear from you! Example contributions include new detection rules and updates to existing rules.
Please refer to our contribution guide for further information.
Our style guide for authoring YARA-L detection rules can be found here.
- https://cloud.google.com/chronicle/docs/reference/detection-engine-api
- https://cloud.google.com/chronicle/docs/how-to#monitoring-events-using-rules
