Webroot Endpoint Health
Overview
The daily "is Webroot protecting everyone?" pass. Start wide with the statistics tools,
then drill into the sites and endpoints that stand out. Every tool here is in Conduit's
Read group; none needs Admin access.
Anti-triggers
Workflow: console-wide triage
webroot_statistics_console_get: devices installed, infected, requiring attention and
with active threats, plus active, trial, expired, expiring, suspended and deactivated
site counts. If infected, attention and active-threat counts are all zero, say so and
stop unless the user asked for staleness.
webroot_sites_list: every site in one call. Rank by PCs infected in the last 24 hours,
and note deactivated or suspended sites that still report endpoints.
- For each flagged site,
webroot_statistics_site_get for its current counts.
- Drill into a site with the per-site workflow below.
Workflow: one site
- Resolve the
siteId (webroot_sites_list, or webroot_sites_lookup from a keycode).
- Infected or recently infected.
webroot_endpoints_list with type = active,
order = lastinfected, orderDirection = D. The top of the list is the most
recently infected. Hand those to threat-review for detail.
- Stale agents.
webroot_endpoints_list with type = active, order = lastseen,
orderDirection = A. Endpoints not seen for 7+ days are either offline, rebuilt
without the agent being deactivated, or have a broken agent. More than 30 days usually
means a retired machine still holding a seat.
- Agent versions.
webroot_endpoints_list with order = agentversion. Group by
version; a long tail of old versions on machines that are online means updates are
failing, not that the machines are off.
- Policy.
webroot_policies_list_site (and webroot_policies_list for GSM-level
policies) to map policy IDs to names, then group the endpoint list by policy. Webroot's
built-in policies include a detect-only Silent Audit policy and an Unmanaged
policy; endpoints on either are not being remediated automatically. Confirm the names
from the policy list rather than assuming them.
- Groups.
webroot_groups_list and webroot_groups_list_endpoints when the
customer organises endpoints by group (servers, laptops, a branch office) and the
question is about one group.
- Coverage gap. Compare the site's total endpoints with the device count the
customer expects (from the RMM or PSA, if those plugins are connected). Webroot cannot
see machines that never got the agent.
Agent status (SkyStatus)
webroot_agent_status_site (by site keycode) and webroot_agent_status_gsm (all
sites) return the agent's own view: versions, first/last seen, and the info classes you
request. Ask for only what you need:
| Question |
returnedInfo |
| Which protection features are on |
EnabledFeatures |
| Scan and seen times, counters |
TimesAndStats |
| OS and agent versions |
OSAndVersions |
| Scan schedule |
Scheduling |
Use modifiedSince for "what changed since yesterday" runs, and follow
ContinuationToken until it stops.
Output
For each site reviewed: endpoints total, infected now, needing attention, stale (7+ and
30+ days), on a detect-only or unmanaged policy, and on an outdated agent version. End
with the actions a technician should take in the GSM console (scan, cleanup, deactivate
retired devices, move to a protective policy). This plugin cannot perform any of them.
Gotchas
webroot_endpoints_list includes deactivated endpoints unless type = active.
Deactivated devices are not protected; count them separately.
- Statistics are current counts, not trends. For a trend, compare against a previous
report or use threat history.
- Page with
pageNr until you have TotalAvailable endpoints before reporting a count.
1---2name: webroot-endpoint-health3description: >4 Webroot endpoint protection posture triage: console-wide and per-site5 statistics (infected, needs attention, active threats), stale agents by6 last seen, outdated agent versions, endpoints on detect-only or unmanaged7 policies, SkyStatus agent status classes, and coverage gaps against the8 site's expected device count. Read-only; remediation happens in the GSM9 console.10when_to_use: >-11 When checking whether a customer's or the whole console's Webroot12 protection is healthy, finding infected or stale endpoints, or confirming13 a new client's deployment. Use when: webroot health, infected devices,14 webroot needs attention, stale webroot agents, webroot agent version,15 webroot coverage, webroot deployment check, or webroot policy audit.16metadata:17 source: https://skillmd.com/skills/wyre-ai/webroot-endpoint-health18---1920# Webroot Endpoint Health2122## Overview2324The daily "is Webroot protecting everyone?" pass. Start wide with the statistics tools,25then drill into the sites and endpoints that stand out. Every tool here is in Conduit's26Read group; none needs Admin access.2728## Anti-triggers2930- **Detection details** (which file, which malware group, which URL or domain): use31 [threat-review](../threat-review/SKILL.md).32- **Seat counts and billing**: use [usage-reconciliation](../usage-reconciliation/SKILL.md).3334## Workflow: console-wide triage35361. `webroot_statistics_console_get`: devices installed, infected, requiring attention and37 with active threats, plus active, trial, expired, expiring, suspended and deactivated38 site counts. If infected, attention and active-threat counts are all zero, say so and39 stop unless the user asked for staleness.402. `webroot_sites_list`: every site in one call. Rank by PCs infected in the last 24 hours,41 and note deactivated or suspended sites that still report endpoints.423. For each flagged site, `webroot_statistics_site_get` for its current counts.434. Drill into a site with the per-site workflow below.4445## Workflow: one site46471. Resolve the `siteId` (`webroot_sites_list`, or `webroot_sites_lookup` from a keycode).482. **Infected or recently infected.** `webroot_endpoints_list` with `type` = `active`,49 `order` = `lastinfected`, `orderDirection` = `D`. The top of the list is the most50 recently infected. Hand those to [threat-review](../threat-review/SKILL.md) for detail.513. **Stale agents.** `webroot_endpoints_list` with `type` = `active`, `order` = `lastseen`,52 `orderDirection` = `A`. Endpoints not seen for 7+ days are either offline, rebuilt53 without the agent being deactivated, or have a broken agent. More than 30 days usually54 means a retired machine still holding a seat.554. **Agent versions.** `webroot_endpoints_list` with `order` = `agentversion`. Group by56 version; a long tail of old versions on machines that are online means updates are57 failing, not that the machines are off.585. **Policy.** `webroot_policies_list_site` (and `webroot_policies_list` for GSM-level59 policies) to map policy IDs to names, then group the endpoint list by policy. Webroot's60 built-in policies include a detect-only *Silent Audit* policy and an *Unmanaged*61 policy; endpoints on either are not being remediated automatically. Confirm the names62 from the policy list rather than assuming them.636. **Groups.** `webroot_groups_list` and `webroot_groups_list_endpoints` when the64 customer organises endpoints by group (servers, laptops, a branch office) and the65 question is about one group.667. **Coverage gap.** Compare the site's total endpoints with the device count the67 customer expects (from the RMM or PSA, if those plugins are connected). Webroot cannot68 see machines that never got the agent.6970## Agent status (SkyStatus)7172`webroot_agent_status_site` (by **site keycode**) and `webroot_agent_status_gsm` (all73sites) return the agent's own view: versions, first/last seen, and the info classes you74request. Ask for only what you need:7576| Question | `returnedInfo` |77|---|---|78| Which protection features are on | `EnabledFeatures` |79| Scan and seen times, counters | `TimesAndStats` |80| OS and agent versions | `OSAndVersions` |81| Scan schedule | `Scheduling` |8283Use `modifiedSince` for "what changed since yesterday" runs, and follow84`ContinuationToken` until it stops.8586## Output8788For each site reviewed: endpoints total, infected now, needing attention, stale (7+ and8930+ days), on a detect-only or unmanaged policy, and on an outdated agent version. End90with the actions a technician should take in the GSM console (scan, cleanup, deactivate91retired devices, move to a protective policy). This plugin cannot perform any of them.9293## Gotchas9495- `webroot_endpoints_list` includes deactivated endpoints unless `type` = `active`.96 Deactivated devices are not protected; count them separately.97- Statistics are current counts, not trends. For a trend, compare against a previous98 report or use threat history.99- Page with `pageNr` until you have `TotalAvailable` endpoints before reporting a count.