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
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.
The text was updated successfully, but these errors were encountered:
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
changed the title
Osquery configuration must be stored per-organization instead of globally
Osquery configuration must be stored per-organization
Nov 5, 2024
RebeccaMahany
changed the title
Osquery configuration must be stored per-organization
Osquery configuration and data must be stored per-organization
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.
The text was updated successfully, but these errors were encountered: