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

[Security Solution] Explore using Git for prebuilt rules delivery #190691

Open
xcrzx opened this issue Aug 19, 2024 · 4 comments
Open

[Security Solution] Explore using Git for prebuilt rules delivery #190691

xcrzx opened this issue Aug 19, 2024 · 4 comments
Assignees
Labels
Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed

Comments

@xcrzx
Copy link
Contributor

xcrzx commented Aug 19, 2024

Related to: #187649

Summary

We've been using Fleet for a while to deliver prebuilt detection rules to Kibana. This delivery method has proven unreliable and unsuited for our needs. Explore the possibilities of using Git for prebuilt rule delivery.

TODO

@xcrzx xcrzx added triage_needed Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Rule Management Security Detection Rule Management Team labels Aug 19, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

@xcrzx
Copy link
Contributor Author

xcrzx commented Aug 19, 2024

Things to figure out:

  • Space isolation when fetching repositories
  • Safe access token storage
  • Possible rule ID collisions and repository validation. We might need to prefix rule IDs with a repo name
  • Use connectors instead of Kibana config to set up rule repositories (?)
  • Extend rule_source to store repo info
  • Changes apply and push
  • Use GitHub API instead of executing git commands (?)
  • Serverless suport. Is it possible to use on-disk rules repository cache in Serverless environment?
  • GitHub API limit
  • How to implement Kibana version constraints?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed
Projects
None yet
Development

No branches or pull requests

3 participants