-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Add support for investigation_fields
in Detection Rules
#3224
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This has been closed due to inactivity. If you feel this is an error, please re-open and include a justifying comment. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This has been closed due to inactivity. If you feel this is an error, please re-open and include a justifying comment. |
Is your feature request related to a problem? Please describe.
Not related to a problem. The Detection Rules custom rule schemas need to be updated to support
investigation_fields
. The original feature was introduced here and the recent type change here.Describe the solution you'd like
We do not support
investigation_fields
in our custom rule schemas.Describe alternatives you've considered
Support
investigation_fields
by determining which rule schema it should be defined in. We should also set a minimum compatibility to 8.11 to avoid a bug discussed here.Additional context
A rule will need to be created in the UI to determine what options are allowed and how we should structure the support in the rule schemas for this field.
The text was updated successfully, but these errors were encountered: