Clicking into a single device from your device list opens its details page — a per-device breakdown that shows scoring, category status, and scan history the fleet-level views don't. A few things on this page are easy to misread if you don't know exactly what's being measured.
The device details page shows a "Type" field with three possible OS values: Windows, macOS, or Linux, based on what the installed agent reported. If a device has no recorded OS — which is the case for every device added through a one-time browser check — this field reads "Unknown device." That's expected for a browser-checked device, not a sign something failed to record. Note that this is a plainer label than the browser-and-OS format your device list shows for the same device (for example "Chrome · Windows" or "Safari · iOS") — the two pages describe it differently.
Your account has a configurable passing threshold (90% by default) that decides which category scores count as passing across the dashboard — this is the same threshold explained in what your fleet protection score means. The device details page uses that account threshold for two things: the pass/fail count next to the overall score, and the "Critical issues" list (any category currently scoring below it, worst first).
Separately, this page also sorts each category into a risk bucket — High Risk, Moderate Risk, or Stable — using fixed cutoffs of 70% and 90%. Those cutoffs are not your account's threshold. If your account uses the default 90%, the two systems happen to line up. If you've changed your threshold to something else, they won't: a category can show as "Stable" in the risk buckets while still counting against you in the pass/fail total and the Critical issues list, or the reverse.
The risk-tier labels (High Risk / Moderate Risk / Stable) always use 70% and 90%. Your pass/fail count and Critical issues list always use your account's actual passing threshold. They are not guaranteed to agree unless your threshold happens to be the default.
Neither the overall score shown at the top of the page nor the Critical issues list is a stored value — both are calculated fresh each time you load the page, from that device's latest score in each category. The overall score is the average of those latest per-category scores. Critical issues is every category currently below your account's passing threshold, listed worst-scoring first.
This page also shows the effective category list for the device — the preset or custom category set that applies to it, checked in order: group setting, then device setting, then your account's fleet default. That list reflects what's configured, not necessarily what's actively restricting the scan. Whether a chosen preset actually limits what gets tested depends on your plan tier.
Below the summary, the scan history table lists past scans for this device with five columns: Timestamp (UTC), Categories, Avg Score, Issues, and Actions.
| Column | What it shows |
|---|---|
| Timestamp (UTC) | When that scan batch completed, in UTC. |
| Categories | How many categories were tested in that scan. |
| Avg Score | That scan's average score across its tested categories. |
| Issues | How many of the tested categories failed, out of the total tested. |
| Actions | Preview the scan's category breakdown inline, or open the full report. |
Each row has two actions: "Preview Scan" expands that scan's category results right on the page, and "View Report" opens the generated report for that scan's date in a new tab.
If a device on a group-scoped team member's account isn't reachable from this page at all, that's expected — device details respects the same group scoping described in what group-scoped team members can see, even if you know the device's exact ID.