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

Osquery configuration and data must be stored per-organization #1939

Closed
RebeccaMahany opened this issue Nov 5, 2024 · 0 comments · Fixed by #1984
Closed

Osquery configuration and data must be stored per-organization #1939

RebeccaMahany opened this issue Nov 5, 2024 · 0 comments · Fixed by #1984
Assignees

Comments

@RebeccaMahany
Copy link
Contributor

RebeccaMahany commented Nov 5, 2024

Store osquery data (node key, uuid, config, keys, ATC config, KATC config) in bbolt and in sqlite per-organization as well as globally. (We want to keep storing globally because this change must be backwards compatible.) To start, store everything under the current tenant. We may want to key off the node key, or a "registration ID" that doesn't yet exist in K2; we don't want to key off munemo in case we end up wanting multiple instances per single tenant.

@RebeccaMahany RebeccaMahany changed the title Store osquery data (node key, uuid, config, keys, ATC config, KATC config) in bbolt and in sqlite per-organization as well as globally. (We want to keep storing globally because this change must be backwards compatible.) To start, store everything under the current tenant. We may want to key off the node key, or a "registration ID" that doesn't yet exist in K2; we don't want to key off munemo in case we end up wanting multiple instances per single tenant. Osquery configuration must be stored per-organization instead of globally Nov 5, 2024
@RebeccaMahany RebeccaMahany changed the title Osquery configuration must be stored per-organization instead of globally Osquery configuration must be stored per-organization Nov 5, 2024
@RebeccaMahany RebeccaMahany changed the title Osquery configuration must be stored per-organization Osquery configuration and data must be stored per-organization Nov 5, 2024
@RebeccaMahany RebeccaMahany self-assigned this Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant