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

Fetch rules on start time #533

Closed
itaysk opened this issue Feb 10, 2021 · 2 comments
Closed

Fetch rules on start time #533

itaysk opened this issue Feb 10, 2021 · 2 comments

Comments

@itaysk
Copy link
Collaborator

itaysk commented Feb 10, 2021

currently rules has to be either built into the container image or mounted in by the user. Tracee should be able to automatically check for updates for it's rules DB on start time.

TBD: should this be implemented in tracee-rules or in the entrypoint?

TBD: where/how we package rules

@simar7
Copy link
Member

simar7 commented Mar 2, 2021

Leaving my commentary as we discussed last:

  1. Existing setup to package rules into a object file can be used but their distribution can be decoupled.
  2. One of the distribution channels for rule object files can be through GitHub releases.
  3. Tracee checks for updates to download new said object release file and does so, if found.

Pros to this approach:

  1. Leverage existing setup and build on top.
  2. Proven with Trivy DB distribution model.
  3. Relatively lightweight and simple.

Cons to this approach:

  1. Tracee no longer self contained, needs a download to be functional in any capacity.
  2. Runtime dependencies can fail in unexpected/untested ways (network failure, disk failure etc.)
  3. Not leveraging something more suited for storing policies (only OPA based) like Artifact Hub.

@yanivagman
Copy link
Collaborator

This is currently out of scope for the project

@yanivagman yanivagman closed this as not planned Won't fix, can't repro, duplicate, stale Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants