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

Differentiate between levels of effort to get Linux disk encryption + key escrow for a host in aggregate stats #24171

Open
iansltx opened this issue Nov 26, 2024 · 0 comments
Labels
#g-endpoint-ops Endpoint ops product group :product Product Design department (shows up on 🦢 Drafting board)

Comments

@iansltx
Copy link
Member

iansltx commented Nov 26, 2024

Problem

As an IT admin, I want to be able to tell which Linux users need to reinstall their OS (because their disk isn't encrypted; see limitations on #22074), vs. users who just need to walk through the escrow process, when looking at disk encryption stats.

What have you tried?

Right now both of the above states wind up in Action Required (pending). You can click through and look at hosts one by one for disk encryption status (if the disk is encrypted, all they need is to escrow), but there's no way to differentiate in the UI before then as you can't add a column for disk encryption status to the hosts list view.

Potential solutions

Either split the Action Required status into "Action Required (Encrypt)" and "Action Required (Escrow)" or have a single line item that splits host counts on a tooltip for Linux. Catch with the latter option is we'd want host counts inside the tooltip linked so admins can view a list of hosts for each individual required action.

What is the expected workflow as a result of your proposal?

As an IT admin, I can see which Linux hosts' users need to be nudged to walk through the excrow process, which hosts need to be rebuilt with encryption enabled, and how many of each I have to deal with for a given team.

@iansltx iansltx added #g-endpoint-ops Endpoint ops product group :product Product Design department (shows up on 🦢 Drafting board) :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. labels Nov 26, 2024
@sharon-fdm sharon-fdm removed the :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#g-endpoint-ops Endpoint ops product group :product Product Design department (shows up on 🦢 Drafting board)
Development

No branches or pull requests

2 participants