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
Describe the solution you'd like
The provider can be used to create Security rules with the siem.* type. It would be a holistic solution for users of the Elasticstack provider if exception lists can also be created and updated in the Provider without requiring another solution - e.g. DaC
Describe the resource you would like to have implemented.
I'd like to manage the Exception Lists using the provider:
A resource to allow creation/updates
create exception container: https://www.elastic.co/guide/en/security/current/exceptions-api-create-container.html
create exception item: https://www.elastic.co/guide/en/security/current/exceptions-api-create-exception-item.html
create a shared exception list: https://www.elastic.co/guide/en/security/current/exceptions-api-create-shared-exception-list.html
update: https://www.elastic.co/guide/en/security/current/exceptions-api-update-container.html
update: https://www.elastic.co/guide/en/security/current/exceptions-api-update-item.html
delete: https://www.elastic.co/guide/en/security/current/exceptions-api-delete-container.html
delete: https://www.elastic.co/guide/en/security/current/exceptions-api-delete-item.html
Data
https://www.elastic.co/guide/en/security/current/exceptions-api-get-container.html
https://www.elastic.co/guide/en/security/current/exceptions-api-create-shared-exception-list.html
https://www.elastic.co/guide/en/security/current/exceptions-api-get-item.html
Describe the solution you'd like
The provider can be used to create Security rules with the
siem.*
type. It would be a holistic solution for users of the Elasticstack provider if exception lists can also be created and updated in the Provider without requiring another solution - e.g. DaCDescribe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: