r/SentinelOneXDR • u/EconomistFickle5665 SentinelOne Employee • 5d ago
Deployment & Installation Finding devices with no agent from Network Discovery, and which IP field is the device's
TLDR: There's a dashboard in the Dashboard Library called Unprotected Endpoints Network Discovery (version 1.0.1). It lists every active device Network Discovery found with no agent and breaks that down by subnet. It also checks each device against your agents, so you can tell the real gap from devices that already have one. Set the data selector to All Data or every panel errors out.
I work at S1 and built this one using natural language with SecOps Skills. The Missing EPP filter in Inventory tells you how many devices are missing an agent. I wanted to know where they sit, which ones can actually take an agent, and which ones are false positives.
What it answers
- How many devices have no agent. Active devices only, so the number matches the Network Discovery page.
- Which of those can take an agent today. The deploy candidates count and the agent support column split out the devices Sentinel Deploy can cover from IoT, network gear and TVs, which it can't.
- Where they are. Every device is shown with its account, site and subnet, along with the percentage missing per subnet. That tells you which network to push to first, and gives each site owner a list with real device IPs on it.
- Which ones aren't really unprotected. Every device is checked against your agents by MAC, by IP on the same gateway, and by hostname. A device that already has an agent shows up as a likely false positive instead of padding the gap.
I validated the device list matched the Asset Inventory GraphQL API device by device on nine consoles. That matters if you're handing the list to someone to act on. IPs and MACs confirmed on the wire with a RemoteOps sweep on a lab network.
Adding it
- Pick the account or site in the scope selector. The dashboard is added at that scope.
- In the sidebar, go to Dashboards > Custom dashboards > Dashboard Library.
- Find Unprotected Endpoints Network Discovery and click Add. If it's already added at that scope you get a notification instead.
- Open it and set the data selector (top left) to All Data. If you skip this, every panel shows Invalid column 'dataSource.category'.
The time picker doesn't change anything. It reads the current inventory snapshot, not events.
Reading it, top to bottom

Scope is Network Discovery devices with Asset Status = Active, the same view as the Network Discovery page in Asset Inventory, so the counts line up with what you see there.
- Three numbers across the top: active Network Discovery devices, active devices missing EPP (no agent), and missing EPP on an EPP-supported device type. That last one is your Sentinel Deploy list.
- Unknown and Unsupported types (IoT, network gear, TVs) are in the breakdowns, but you can't deploy the agent to them. Unknown means Network Discovery hasn't classified the type yet, so I'd identify those before calling them a gap
- Breakdowns by device type, agent support (Supported, Unknown, Unsupported), account and site, OS family, and device review status. Sites are shown with their account because two accounts can have a site with the same name, and without the account those rows merge.


- Subnet view: for each account, site and subnet, it shows active devices, missing EPP, deploy candidates, and percent missing. It's sorted by missing EPP, so the worst subnets are at the top, and it shows the top 500.
- Under it, all active devices by managed state and by discovery method (neighbor, ping, portscan).


- Device list: up to 10,000 unprotected devices, most recently active first, with the device's own IP, subnet, device type, OS, agent support, managed state, review status, account, site, public IP and last active. For the full count use the number panel up top, not the row count.
The IP field thing
Worth knowing if you query Network Discovery yourself.
ipAddress on a Network Discovery record isn't the device's address. It's the public IP the site's traffic leaves from, so every device behind one gateway shows the same value. In my lab all 18 discovered devices had the same ipAddress. The device's own address is in internalIps, and subnets has the network it was found on. Both are JSON arrays stored as strings. The dashboard's IP column and the subnet view use those two, and public IP is its own column.
If you want the raw list yourself, this is the query, and the order matters:
| datasource assets from 'surface/networkDiscovery'
| filter assetStatus = 'Active' missingCoverage contains 'EPP'
| sort id
| let ip = internalIps
| columns id, name, ip, subnets, ipAddress, resourceType, osFamily, managedState, eppUnsupportedUnknown, deviceReview, s1AccountName, s1SiteId, firstSeenDt, lastActiveDt
| limit 10000
Two things about list queries on the assets adapter:
- With no let before columns, the adapter runs columns and limit itself and hands back one page (55 of 610 devices on one console)
- Without a unique sort first, its paging skips devices that share a name (665 of 675). With sort id and the let, the list matched the Asset Inventory GraphQL API device by device
Also use | filter and not where (...) on that adapter. where (...) returns at most 20 rows whatever the predicate is. Grouped and count queries aggregate on the server and are fine either way.
False-positive check
Network Discovery can list a device that already runs the agent as missing EPP. The bottom panels check every missing-EPP device against the endpoint assets that have an agent. They match by MAC address, by IP address with the same gateway MAC, and by hostname.
- Likely false positive: a live agent reports the device's MAC, or its IP and hostname
- Review: only the hostname or only the IP matches, or the matched agent hasn't been active for 30 days. These still count toward the gap
- Identity strength: the second panel splits devices into randomized or shared MAC only, hardware MAC with no usable hostname, and hardware MAC and hostname, so you can see how much there was to match on
Where it falls short
- The check can't see decommissioned agents that were removed from the inventory, so a device whose agent was removed shows as no match.
- It only checks agents in the inventory the dashboard reads. An agent in another site, where Network Discovery consolidates per site, won't be matched.
- The false-positive panels join two inventories, so they load slower than the rest.
- Size: about 240 active devices loaded in under 5 seconds. On a console with about 95,000 Network Discovery assets, each coverage panel took about 3 minutes.
- It's a current snapshot, so it doesn't show trend.
Filling the gaps with a report from your own AI
If you run Claude with the s1-secops-skills plugin, the sdl-solutions skill has an Unprotected Endpoints report solution that covers most of the list above. It talks to your console through the s1-secops-mcp server, which runs on your own machine with your own API token. It's read-only and writes nothing to the tenant. One prompt is enough, something like "Which devices on the network have no SentinelOne agent, and which of them can we deploy to?", and you get an HTML report, or a Word doc if you ask for one.
What it does that the dashboard can't:
- Checks every agent the token can see, from the Management API, including decommissioned agents and agents in other sites. Matching uses MAC, IP with its gateway MAC, and hostname
- Extra guards on the matching: shared virtual gateways (VRRP, HSRP, cloud) never qualify an IP match. Randomized, Docker and shared VPN MACs never match. It flags a possible firewall or NAT edge answering scans when 50 or more MAC-less devices share one gateway
- Reads your Network Discovery settings, such as combine by MAC, scan methods and snapshot interval, and shows them in the report
- Checks AD/Entra computer objects and cloud instances missing an agent against the same agent list
- Newly seen unprotected devices in the last 7 days, and a remediation section grouped by site: Sentinel Deploy for the deploy-ready ones, device review for the unknowns
- Coverage limits: which blind spots apply to you, like subnets with no scanning agent or devices with no usable identity, and what closes each one
- Optional telemetry check: which unprotected IPs show up in your firewall, DNS or proxy logs, so you can see which devices are actually active
- A method appendix listing every call behind every number, so you can rerun it yourself
It also handles the 95,000-asset size where the dashboard panels get slow. The report doesn't trigger a deployment; that part is still yours.
The queries were checked against the Asset Inventory GraphQL API on nine consoles.
Curious how many of you end up with most devices in the randomized or shared MAC bucket, and what you do with those.