Most engineers think…
Most security teams assume network discovery means buying a dedicated scanner appliance, plugging it into a SPAN port, and managing yet another console.
Singularity Ranger flips that model. You already have SentinelOne agents running on your managed endpoints — Ranger elects a subset of those endpoints to become distributed passive sensors. They listen for ARP and DHCP broadcast traffic, optionally run active scans on subnets you choose, and report every discovered IP-enabled device back to the Singularity console. No new hardware, no agent on the unmanaged device, and no network re-cabling. The result is a continuously updated asset inventory and rogue-device alert list built into the same platform your SOC already uses.
① What Singularity Ranger actually is — agentless discovery without new hardware
Singularity Ranger (now branded Singularity Network Discovery) is the network visibility layer of the SentinelOne Singularity platform. Its defining property: it discovers every IP-enabled device on the network — unmanaged, IoT, legacy, and rogue — without installing an agent on the discovered devices and without deploying any dedicated scanner hardware.
Ranger ships as a feature within the Singularity Complete and Singularity Control tiers. Enabling it takes a policy flip in the console; no network re-cabling, no new VLAN, no sensor box to rack. The inventory it builds appears directly in the Singularity console alongside endpoint telemetry, so analysts get a single pane of glass across managed endpoints and everything else on the wire.
Singularity Ranger discovers unmanaged devices by…
② How the sensors work — managed endpoints as distributed listeners
Ranger works by electing a subset of your existing managed endpoints to act as passive network sensors. Elected endpoints listen for broadcast traffic — ARP, DHCP, mDNS and similar protocol chatter — that all IP devices emit naturally. No traffic is diverted; the endpoint simply records what it already sees on the wire.
Passive vs active scanning
Passive observation alone captures devices that broadcast. For quieter assets (printers, cameras, OT controllers that rarely talk), Ranger optionally runs active scans using protocols you configure — ICMP, SNMP, UDP, TCP, SMB and more — against IP ranges you specify. Active scans are policy-controlled so you can exclude sensitive OT subnets. The elected-sensor design means discovery is distributed: one sensor per subnet, no single point of failure, no centralised probe box.
An existing SentinelOne-managed endpoint chosen by policy to act as a passive network listener for its subnet — no new hardware.
The elected sensor records ARP, DHCP, and mDNS broadcasts naturally emitted by every IP device — no traffic is redirected or spoofed.
Machine-learning classifies each observed device into a profile: manufacturer, device type, OS, firmware hints, and active services.
Any discovered device not enrolled in Singularity is flagged as unmanaged; one not in corporate inventory is flagged rogue and can trigger a STAR block.
ARP and DHCP are Layer-2 broadcasts — they don't cross routers. Make sure at least one Ranger-elected endpoint sits on each subnet you want to cover, or you will have blind spots. Ranger's sensor-election policy lets you assign coverage by IP range or VLAN tag.
Which broadcast protocols do Ranger-elected endpoints passively listen for by default?
③ ML-based fingerprinting — turning a MAC address into a full device profile
Seeing a device on the wire is just the first step. Ranger's ML-based fingerprinting engine classifies each discovered asset by analysing the combination of broadcast signatures, active-scan responses, and any device-specific identifiers it can observe. The output is a device profile containing manufacturer, device type, operating system, firmware version clues, and a list of active services — all without authenticating to or installing anything on the device.
When a newly-discovered device does not have a SentinelOne agent, Ranger flags it as unmanaged and surfaces it in the console with a risk signal. If the device matches no known corporate asset inventory record, it can be flagged as rogue. Admins can then trigger a STAR rule to block network communication from the unknown device directly from the console.
Unmanaged means the device has no SentinelOne agent — it could be a legitimate printer or camera that simply can't run an agent. Rogue means the device is unrecognised against your asset inventory. In an interview, separating these two labels shows you understand the risk triage logic, not just the vocabulary.
▶ Watch Ranger discover and flag a rogue laptop
Step through how a new unagented device is found, fingerprinted, and blocked. Press Play for the clean path, then Break it to see the classic blind-spot failure.
A new IP camera joins the corporate Wi-Fi with no SentinelOne agent. How does Ranger classify it?
④ Attack-surface mapping & automated response — from inventory to action
Ranger's discovery output feeds the Singularity asset inventory, giving you a real-time map of the network attack surface: which devices are unmanaged, which are running outdated OS versions, which appeared for the first time today. This is the data that turns a reactive SOC into a proactive one — you cannot patch or protect what you cannot see.
Automated response with STAR
Because Ranger lives inside Singularity, you can write STAR automated-response rules directly against discovery events. A common pattern: alert on any new device without an agent joining a protected VLAN, and optionally block communications from that device using the managed endpoints already on the segment. No firewall rule change needed. For interview prep, the key phrase is: Ranger closes the visibility gap between the endpoints you manage and everything else on the subnet.
Arjun, a SOC analyst at a Pune manufacturing firm, faces this
An OT engineer plugged a personal laptop into the production VLAN during a site visit. The device has no SentinelOne agent and appears as an unknown IP for six hours before anyone notices.
No network discovery was active — the team relied on DHCP lease logs reviewed manually each morning.
Singularity console has no Ranger sensors elected on the OT subnet, so the unmanaged device was invisible until a firewall log review caught unusual SMB traffic.
Singularity Console ▸ Network Discovery ▸ Sensor Policy ▸ OT VLAN rangeEnable Ranger and elect one managed Windows endpoint already on the OT VLAN as a passive sensor. Configure active ICMP scan for the OT IP range. Set a STAR rule to alert (and optionally block) any new device without an agent on that segment.
Repeat the test: plug in an unagented laptop. Within minutes, Ranger surfaces it as unmanaged, the STAR rule fires an alert, and Arjun has manufacturer, OS hint, and first-seen timestamp before the device can move laterally.
In the Singularity console, check the Network Discovery dashboard for 'Sensors active per subnet' before telling stakeholders you have full visibility. A subnet with zero active sensors is a blind spot, not a clean subnet. Validate coverage after any network change or VLAN addition.
An interviewer asks how to automatically block a rogue device found by Ranger. Best answer?
🤖 Ask the AI Tutor
Tap any question — instant, scoped to this lesson. No login, no waiting.
Pre-curated from vendor docs + community Q&A, scoped to this lesson. For a live prod issue, paste your export into chat.techclick.in.
📝 Wrap-up assessment — six more
You've answered 4 inline. Six left. 70% (7 of 10) marks the lesson complete on your profile. Tap Submit all answers at the end.
🧠 In your own words
Type one line: why does Singularity Ranger need no extra hardware or agents on the devices it discovers? Then compare with the expert version.
🗣 Teach a friend
Best way to lock it in — explain it in one line to a teammate. Tap to generate a paste-ready summary.
📖 Glossary
- Singularity Ranger
- SentinelOne's agentless network discovery and device fingerprinting feature, now called Singularity Network Discovery, built into the Singularity platform.
- Elected sensor
- An existing SentinelOne-managed endpoint chosen by policy to act as a passive network listener for its subnet — no new hardware required.
- Passive observation
- Capturing ARP, DHCP, and mDNS broadcast traffic that IP devices emit naturally, without sending any probe traffic of your own.
- Active scan
- Policy-controlled probes (ICMP, SNMP, TCP, UDP, SMB) sent to a specified IP range to discover quieter devices that rarely broadcast.
- ML fingerprinting
- Machine-learning classification of broadcast signatures and scan responses to extract manufacturer, device type, OS, firmware hints, and active services for each discovered asset.
- Unmanaged device
- A device visible on the network that has no enrolled SentinelOne agent — could be a legitimate asset (printer, camera) that cannot run an agent.
- Rogue device
- An unmanaged device not recognised in the corporate asset inventory — higher risk category that typically triggers a STAR alert or block.
- STAR rule
- Singularity Active Response rule — an automated detection-to-response workflow in the Singularity platform that can trigger on Ranger discovery events.
📚 Sources
- SentinelOne — Singularity Network Discovery product page (formerly Ranger). sentinelone.com/platform/singularity-network-discovery/
- SentinelOne — Advancing Device Fingerprinting with Singularity Ranger. sentinelone.com/resources/advancing-device-fingerprinting-with-singularity-ranger/
- SentinelOne — Singularity Network Discovery datasheet. assets.sentinelone.com/iotranger/singularity-network-discovery-en
- SentinelOne Blog — SentinelOne Ranger IoT: Technology Preview. sentinelone.com/blog/sentinelone-ranger-iot/
- Help Net Security — SentinelOne turns every protected endpoint into a network detection device. helpnetsecurity.com/2019/03/08/sentinelone-ranger/
- SecurityScientist — 12 Questions and Answers about Singularity Ranger. securityscientist.net/blog/12-questions-and-answers-about-singularity-ranger-sentinelone/
What's next?
Ranger maps the surface — next, go deeper on how Singularity XDR correlates endpoint telemetry with network visibility to build an attack storyline and auto-respond with STAR rules.