Skip to content
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

[Research] Supporting response actions with alerting and connectors #155644

Closed
mikecote opened this issue Apr 24, 2023 · 2 comments
Closed

[Research] Supporting response actions with alerting and connectors #155644

mikecote opened this issue Apr 24, 2023 · 2 comments
Labels
Feature:Actions/Framework Issues related to the Actions Framework Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework research Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Apr 24, 2023

Response actions are used by security solution as automation workflows when an alert is detected. These actions are currently coded within the rule executor given we have limitations with the actions framework to fully support this.

We should research how we can enhance the actions framework to support actions within Kibana and providing a solution in these areas:

  1. There shouldn't be a need to create a connector saved in the UI when the integration is within our own products and doesn't require a configuration (ex: case, OS Query, server log, etc)
  2. The RBAC should re-use the feature privilege of the existing product (ex: case feature privileges for the case action)
  3. Guidance on how the connector can handle the response of a request (ex: OS Query response) for re-use
@mikecote mikecote added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) research Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Actions/Framework Issues related to the Actions Framework labels Apr 24, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@mikecote
Copy link
Contributor Author

Closing as outdated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Actions/Framework Issues related to the Actions Framework Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework research Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

No branches or pull requests

2 participants