[FR] [DaC] Update Readme with DaC Support References (#4526)
* Update Readme with DaC Support References * Patch bump * Call out DaC Pipeline support
This commit is contained in:
@@ -24,13 +24,13 @@ This repository was first announced on Elastic's blog post, [Elastic Security op
|
||||
|
||||
## Overview of this repository
|
||||
|
||||
Detection Rules contains more than just static rule files. This repository also contains code for unit testing in Python and integrating with the Detection Engine in Kibana.
|
||||
Detection Rules contains more than just static rule files. This repository also contains code for building Detections-as-code pipelines, unit testing in Python and integrating with the Detection Engine in Kibana.
|
||||
|
||||
| folder | description |
|
||||
|------------------------------------------------ |------------------------------------------------------------------------------------ |
|
||||
| [`detection_rules/`](detection_rules) | Python module for rule parsing, validating and packaging |
|
||||
| [`etc/`](detection_rules/etc) | Miscellaneous files, such as ECS and Beats schemas |
|
||||
| [`hunting/`](./hunting/) | Root directory where threat hunting package and queries are stored |
|
||||
| [`etc/`](detection_rules/etc) | Miscellaneous files, such as ECS and Beats schemas and configuration files |
|
||||
| [`hunting/`](./hunting/) | Root directory where threat hunting package and queries are stored |
|
||||
| [`kibana/`](lib/kibana) | Python library for handling the API calls to Kibana and the Detection Engine |
|
||||
| [`kql/`](lib/kql) | Python library for parsing and validating Kibana Query Language |
|
||||
| [`rules/`](rules) | Root directory where rules are stored |
|
||||
@@ -136,7 +136,7 @@ We welcome your contributions to Detection Rules! Before contributing, please fa
|
||||
|
||||
## Detections as Code (DaC)
|
||||
|
||||
The Detection Rules repo includes a number of commands to help one manage rules with an "as code" philosophy. We recommend starting with our [DaC Specific Documentation](https://dac-reference.readthedocs.io/en/latest/) for strategies and recommended setup information. However, if you would prefer to jump right in, please see our [custom rules documentation](docs-dev/custom-rules-management.md) for information on how to configure this repo for use with custom rules followed by our [CLI documentation](CLI.md) for information on our commands to import and export rules.
|
||||
The Detection Rules repo includes a number of commands to help one manage rules with an "as code" philosophy. We recommend starting with our [DaC Specific Documentation](https://dac-reference.readthedocs.io/en/latest/) for strategies and recommended setup information. However, if you would prefer to jump right in, please see our local [detections as code documentation](docs-dev/detections-as-code.md) and [custom rules documentation](docs-dev/custom-rules-management.md) for information on how to configure this repo for use with custom rules followed by our [CLI documentation](CLI.md) for information on our commands to import and export rules.
|
||||
|
||||
## RTAs
|
||||
|
||||
@@ -156,3 +156,4 @@ Occasionally, we may want to import rules from another repository that already h
|
||||
- This repository includes new and updated rules that have not been released yet. To see the latest set of rules released with the stack, see the [Prebuilt rule reference](https://www.elastic.co/guide/en/security/current/prebuilt-rules-downloadable-updates.html).
|
||||
- If you’d like to report a false positive or other type of bug, please create a GitHub issue and check if there's an existing one first.
|
||||
- Need help with Detection Rules? Post an issue or ask away in our [Security Discuss Forum](https://discuss.elastic.co/c/security/) or the **#security-detection-rules** channel within [Slack workspace](https://www.elastic.co/blog/join-our-elastic-stack-workspace-on-slack).
|
||||
- For DaC specific cases, pleases see our [support and scope documentation](docs-dev/detections-as-code.md#support-and-scope) for more information.
|
||||
Reference in New Issue
Block a user