You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -32,7 +33,6 @@ Detection Rules contains more than just static rule files. This repository also
32
33
|[`hunting/`](./hunting/)| Root directory where threat hunting package and queries are stored |
33
34
|[`kibana/`](lib/kibana)| Python library for handling the API calls to Kibana and the Detection Engine |
34
35
|[`kql/`](lib/kql)| Python library for parsing and validating Kibana Query Language |
35
-
|[`rta/`](rta)| Red Team Automation code used to emulate attacker techniques, used for rule testing |
36
36
|[`rules/`](rules)| Root directory where rules are stored |
37
37
|[`rules_building_block/`](rules_building_block)| Root directory where building block rules are stored |
38
38
|[`tests/`](tests)| Python code for unit testing rules |
@@ -138,9 +138,15 @@ We welcome your contributions to Detection Rules! Before contributing, please fa
138
138
139
139
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/custom-rules.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.
140
140
141
+
## RTAs
142
+
143
+
Red Team Automations (RTAs) used to emulate attacker techniques and verify the rules can be found in dedicated
Everything in this repository — rules, code, RTA, etc. — is licensed under the [Elastic License v2](LICENSE.txt). These rules are designed to be used in the context of the Detection Engine within the Elastic Security application. If you’re using our [Elastic Cloud managed service](https://www.elastic.co/cloud/) or the default distribution of the Elastic Stack software that includes the [full set of free features](https://www.elastic.co/subscriptions), you’ll get the latest rules the first time you navigate to the detection engine.
149
+
Everything in this repository — rules, code, etc. — is licensed under the [Elastic License v2](LICENSE.txt). These rules are designed to be used in the context of the Detection Engine within the Elastic Security application. If you’re using our [Elastic Cloud managed service](https://www.elastic.co/cloud/) or the default distribution of the Elastic Stack software that includes the [full set of free features](https://www.elastic.co/subscriptions), you’ll get the latest rules the first time you navigate to the detection engine.
144
150
145
151
Occasionally, we may want to import rules from another repository that already have a license, such as MIT or Apache 2.0. This is welcome, as long as the license permits sublicensing under the Elastic License v2. We keep those license notices in `NOTICE.txt` and sublicense as the Elastic License v2 with all other rules. We also require contributors to sign a [Contributor License Agreement](https://www.elastic.co/contributor-agreement) before contributing code to any Elastic repositories.
0 commit comments