Table access control

[pintomi1989]

As a Fleet user, I would like to dictate which tables certain roles may access. Adding a config to the Observer+ role to restrict the tables that user can run queries against (On a per user basis) would accomplish this.

[noahtalerman]

Noah: Observer+ users can run arbitrary queries.

@pintomi1989 what are the tables that the customer would prevent Observer+ users from running?

[noahtalerman]

@pintomi1989 we discussed this during the last feature fest.

We decided not to work on drafts for this in the upcoming sprint (4.49)

Removing from feature fest.

[pintomi1989]

@noahtalerman

Security dictates in this environment that only members of the security org should have access to security-related data, i.e., an desktop admin or help desk tech can't use Fleet tables which expose this data, e.g.,

carves anything that would return browser history "personal" data

Could be a white or black list, i.e.,

• a help desk user could have access to a single, vetted query, or a list of vetted queries
• a query would present an error in the UI if their user privilege was restricted for specified tables.

Customer believes this would make the product more useful to users outside their security org