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

Improve Sorting & Matching Capabilities In Fleet UI Vulnerabilities View #19099

Open
nonpunctual opened this issue May 17, 2024 · 1 comment
Open
Assignees
Labels
~csa Issue was created by or deemed important by the Customer Solutions Architect. customer-honoria #g-endpoint-ops Endpoint ops product group :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature

Comments

@nonpunctual
Copy link
Contributor

nonpunctual commented May 17, 2024

Current State:

  • All end users at customer organization have admin privileges on computers.
  • Security tightly manages / monitors a subset of celebrity apps.
  • There is less control over apps that users install on their own...
    • E.g., "How risky is Opera?"

Problem

The team wants to:

  • triage problems faster
  • be more proactive
  • respond more quickly to trending threats

Tools other than Fleet have been tried for collecting data.

  • Security team must massage data.
  • Workflows are too hard, too manual.

Data in Fleet needs to be synthesized so it's:

  • easier to read
  • quicker to act on
  • can be incorporated into regular checks
  • easier to show to partners / execs / auditors

Desirable metrics & features:

  • Better column sorting
    • Number of vulnerabilities
    • All high-risk vulnerabilities
      • a "cut list", eg,
        • 300 hosts with app that has low exploit risk - not important
        • 7 hosts with app that has high exploit risk - needs to be more visible
    • A high-severity column ("filter by severity") with links to CVEs
      • Display by severity with something like a "pivot table" of exploitability
    • Display an “actively exploited” value
      • SInce "actively exploited" is a binary value a toggle for this sort makes sense...
Screenshot 2024-05-16 at 11 06 14 PM Screenshot 2024-05-16 at 11 11 13 PM

Potential solutions

  1. Add columns & actively exploited toggle for searching & sorting in the Vulnerabilities view in Fleet UI per screen shots.
@nonpunctual nonpunctual added :product Product Design department (shows up on 🦢 Drafting board) customer-honoria ~feature fest Will be reviewed at next Feature Fest ~csa Issue was created by or deemed important by the Customer Solutions Architect. labels May 17, 2024
@nonpunctual
Copy link
Contributor Author

@noahtalerman summary of discussion as problem statement. Thanks.

@noahtalerman noahtalerman removed the :product Product Design department (shows up on 🦢 Drafting board) label May 17, 2024
@noahtalerman noahtalerman added :product Product Design department (shows up on 🦢 Drafting board) #g-endpoint-ops Endpoint ops product group story A user story defining an entire feature and removed ~feature fest Will be reviewed at next Feature Fest labels May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~csa Issue was created by or deemed important by the Customer Solutions Architect. customer-honoria #g-endpoint-ops Endpoint ops product group :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature
Development

No branches or pull requests

3 participants