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

Scope policies and queries with labels #24091

Open
noahtalerman opened this issue Nov 22, 2024 · 0 comments
Open

Scope policies and queries with labels #24091

noahtalerman opened this issue Nov 22, 2024 · 0 comments
Labels
~customer promise A feature request from a Fleet customer that Fleet has contractually agreed to deliver ~customer request A prioritized, customer feature request. Has ≥ 1 customer codename label(s) customer-hubble

Comments

@noahtalerman
Copy link
Member

noahtalerman commented Nov 22, 2024

  • prospect-hubble: Gong snippet:
  • @allenhouchins: User requested this because they're trying to pass a compliance check and in order to do so, they want to make sure specific people's workstations meet unique compliance requirements. Some people, given what data they have access to, have to follow stricter compliance requirements (ex. longer password length, yubikey, etc.). These people's workstations will have the same baseline compliance requirements as all other workstations and thus they'll be in the same team in Fleet. In order to check the unique requirements, the user wants to add these workstations to a label and apply this label to strict policy.
    • @allenhouchins: Makes the audit smoother. Auditor is just going to see green and red. Going to have to justify red.
  • @noahtalerman: User requested this because they want to run queries that check to make sure end users aren't sharing sensitive data during their 2-week offboarding. They only want to run these queries on workstations assigned to employees who are offboarding so that they can limit the noise. They don't need this info form everyone else.
    • @noahtalerman: In the interim the user can break out separate teams for these use cases.
    • @noahtalerman: Eventually the user would be able to scope policies and queries using labels. Similar to configuration profiles.
  • @marko-lisica : Remember to add errors for cases when user enable install software automation for policy that has scope and software title has scope already.

User stories

@noahtalerman noahtalerman added :product Product Design department (shows up on 🦢 Drafting board) customer-hubble ~customer request A prioritized, customer feature request. Has ≥ 1 customer codename label(s) ~customer promise A feature request from a Fleet customer that Fleet has contractually agreed to deliver labels Nov 22, 2024
@noahtalerman noahtalerman added ~feature fest Will be reviewed at next Feature Fest and removed :product Product Design department (shows up on 🦢 Drafting board) labels Nov 26, 2024
@noahtalerman noahtalerman removed the ~feature fest Will be reviewed at next Feature Fest label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~customer promise A feature request from a Fleet customer that Fleet has contractually agreed to deliver ~customer request A prioritized, customer feature request. Has ≥ 1 customer codename label(s) customer-hubble
Development

No branches or pull requests

1 participant