TTechclick ⚡ XP 0% All lessons
SentinelOne · Endpoint Security / XDR · Singularity RangerInteractive · L1 / L2 / L3

SentinelOne Singularity Ranger — Agentless Network Discovery & Attack Surface Mapping

Singularity Ranger turns every existing SentinelOne-protected endpoint into a passive network sensor, finds every IP-enabled device on the subnet — managed or not — fingerprints it with ML, and maps your real attack surface, all without deploying extra hardware or agents to the devices being discovered.

📅 2026-06-20 · ⏱ 16 min · 4 infographics · live packet demo · 🏷 10-Q assessment + AI Tutor inline

⚡ Quick Answer

Master SentinelOne Singularity Ranger in 2026: agentless device discovery, ML-based fingerprinting, rogue device detection, and network attack-surface mapping with no extra hardware.

🎯 By the end you will be able to

Read as:

Pick where you want to start

1

What it is

Agentless discovery, no hardware, no new agents.

2

How sensors work

Elected endpoints, passive ARP/DHCP, active scans.

3

Fingerprinting

ML classifies OS, firmware, services, rogue flag.

4

Attack surface & response

Console visibility, STAR rules, block unknown device.

🧠 Warm-up — 3 questions, no score

Just notice which ones make you pause. We answer all three inside the lesson.

1. Does Singularity Ranger require deploying an agent on each discovered device?

Answered in What it is.

2. How do managed endpoints learn about unmanaged devices on the subnet?

Answered in How sensors work.

3. What does ML-based fingerprinting extract from an unmanaged device?

Answered in Fingerprinting.

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.

Figure 1 — How Ranger builds the asset inventory
Ranger loops continuously: elect sensors, observe traffic, fingerprint, enrich inventory, alert on rogue devices.How Ranger builds the asset inventoryElect sensorspick managed endpointsObserveARP, DHCP, mDNSScan (opt.)ICMP/SNMP/TCP/UDPFingerprintML device profilingInventoryalert onrogue/unmanaged
Ranger loops continuously: elect sensors, observe traffic, fingerprint, enrich inventory, alert on rogue devices.
Quick check · Q1 of 10 · Understand

Singularity Ranger discovers unmanaged devices by…

Correct: c. Ranger elects a subset of your already-deployed managed endpoints to act as passive sensors. No agent is placed on the discovered device; no new hardware is needed.
👉 So far: Singularity Ranger = no new hardware, no agent on discovered devices — it recycles existing managed endpoints as distributed network sensors.

② 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.

Figure 2 — One elected sensor covers the subnet
A single Ranger-elected endpoint passively collects device data from all IP devices on its subnet and reports back to Singularity.One elected sensor covers the subnetElected sensormanaged endpointLaptops (ARP)IoT camerasPrintersOT controllersRogue deviceNetwork switches
A single Ranger-elected endpoint passively collects device data from all IP devices on its subnet and reports back to Singularity.
📡
Elected sensor
tap to flip

An existing SentinelOne-managed endpoint chosen by policy to act as a passive network listener for its subnet — no new hardware.

🔍
Passive observation
tap to flip

The elected sensor records ARP, DHCP, and mDNS broadcasts naturally emitted by every IP device — no traffic is redirected or spoofed.

🤖
ML fingerprinting
tap to flip

Machine-learning classifies each observed device into a profile: manufacturer, device type, OS, firmware hints, and active services.

🚨
Rogue device flag
tap to flip

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.

Elect sensors close to each subnet

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.

Quick check · Q2 of 10 · Remember

Which broadcast protocols do Ranger-elected endpoints passively listen for by default?

Correct: b. Ranger passive sensors listen for ARP, DHCP, and mDNS — the broadcast traffic every IP device emits naturally on the subnet. Active-scan protocols (SNMP, SMB, ICMP) are used optionally for quieter assets.
👉 So far: Elected sensors passively collect ARP, DHCP, and mDNS; active scans (ICMP/SNMP/TCP) cover quieter IoT and OT devices — all policy-controlled per subnet.

③ 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.

Figure 3 — What ML fingerprinting extracts per device
Each unmanaged device is profiled across four layers — from MAC to active services — without authenticating to the device.What ML fingerprinting extracts per deviceManufacturer & typeOUI lookup + ML classificationOS & firmwaresignature analysis of responsesActive servicesSNMP, SMB, open TCP portsAgent statusmanaged / unmanaged / rogue flag
Each unmanaged device is profiled across four layers — from MAC to active services — without authenticating to the device.
'Unmanaged' and 'rogue' are not the same

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.

① Device joinsAn unagented laptop connects to the corporate Wi-Fi and broadcasts an ARP request for the default gateway.
② Sensor sees itThe Ranger-elected managed endpoint on the same subnet captures the ARP broadcast and reports the new MAC and IP to Singularity.
③ ML fingerprintSingularity's ML engine analyses the broadcast signature and an SNMP probe response, classifying the device as a Windows laptop — manufacturer and OS identified.
④ STAR fires alertThe device has no enrolled agent — it is flagged unmanaged/rogue. A STAR rule fires an alert and optionally blocks communications from that IP via the elected sensor's OS firewall.
Press Play to step through Ranger finding a rogue laptop. Then press Break it.
Quick check · Q3 of 10 · Apply

A new IP camera joins the corporate Wi-Fi with no SentinelOne agent. How does Ranger classify it?

Correct: b. Ranger's passive sensors see the camera's ARP and DHCP broadcasts. ML fingerprinting classifies it as a camera (manufacturer, device type) and flags it as unmanaged because no Singularity agent is enrolled on it.
👉 So far: ML fingerprinting extracts manufacturer, OS, firmware hints, and active services from each discovered device; no-agent devices are flagged unmanaged, unknown ones flagged rogue.

④ 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.

Figure 4 — Passive observation vs active scanning
Ranger uses both modes — passive for always-on visibility, active for quieter assets — controlled by policy per subnet.Passive observation vs active scanningPassive (always on)Listens to ARP, DHCP, mDNSZero extra network trafficCatches devices at join timeBest for standard IT endpointsActive scan (policy-driven)ICMP, SNMP, TCP, UDP, SMBFinds quiet IoT and OT devicesConfigurable per IP rangeCan be excluded for OT subnets
Ranger uses both modes — passive for always-on visibility, active for quieter assets — controlled by policy per 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.

Likely cause

No network discovery was active — the team relied on DHCP lease logs reviewed manually each morning.

Diagnosis

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 range
Fix

Enable 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.

Verify

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.

Confirm coverage before claiming visibility

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.

Quick check · Q4 of 10 · Analyze

An interviewer asks how to automatically block a rogue device found by Ranger. Best answer?

Correct: b. STAR rules inside Singularity can trigger on Ranger discovery events. A managed endpoint on the same subnet can enforce the block, no firewall rule change required. Ranger is not read-only — it integrates with the response engine.
👉 So far: Ranger feeds the Singularity asset inventory in real time; STAR rules can auto-alert or auto-block rogue devices via managed endpoints already on the segment.

🤖 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.

Q5 · Remember

Singularity Ranger discovers unmanaged devices without deploying agents on them because it relies on…

Correct: b. Ranger's fundamental design is to repurpose already-deployed managed endpoints as passive sensors. No new hardware, no agent on the discovered device, no network changes.
Q6 · Understand

Why can a Ranger sensor on one subnet NOT automatically see devices on a different subnet?

Correct: c. ARP and DHCP are Layer-2 broadcasts — routers do not forward them. Each subnet needs at least one elected Ranger sensor that is physically (or virtually) on that segment to capture its broadcasts.
Q7 · Apply

A Ranger scan shows a device classified as an OT PLC with no SentinelOne agent. What is the safest next step?

Correct: c. OT devices often cannot run EDR agents and must not be disrupted. The right action is to verify legitimacy in the asset inventory, apply passive monitoring, and reserve blocking for confirmed rogue devices — never auto-block OT hardware.
Q8 · Analyze

What advantage does ML-based fingerprinting have over a pure OUI-lookup approach for IoT devices?

Correct: c. Many IoT/OT devices share MAC OUI prefixes with generic hardware vendors. ML uses the full combination of DHCP vendor class, SNMP response, and observed service patterns to classify the specific device type and OS more accurately than a MAC prefix lookup alone.
Q9 · Evaluate

Which statement best explains Ranger's value in the context of attack-surface management?

Correct: d. Attack surface management requires knowing everything on the network, not just managed endpoints. Ranger's core value is closing that visibility gap and converting unknown devices into inventoried, risk-scored assets the SOC can act on.
Q10 · Evaluate

An organisation wants to auto-block any new unagented device that joins the finance VLAN. What is the correct Ranger-native approach?

Correct: d. STAR rules in Singularity can trigger on Ranger discovery events and enforce blocks via managed endpoints already on the segment — no firewall ACL changes, no extra hardware. Manual daily reviews and inline IPS appliances are slower and costlier fallbacks.
Lesson complete — saved to your profile.
Almost! You need 70% (7 of 10) — re-read the path that tripped you up and tap "Try again".

🧠 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.

Expert version: Because Ranger repurposes the SentinelOne agents that are already running on your managed endpoints as distributed passive network sensors. Each elected endpoint listens to Layer-2 broadcast traffic (ARP, DHCP) that every IP device emits naturally on the subnet, and optionally runs active probes. The discovered devices never know they are being observed and nothing needs to be installed on them. The result is full network visibility built into the same console as your EDR, at zero incremental hardware cost.

🗣 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

  1. SentinelOne — Singularity Network Discovery product page (formerly Ranger). sentinelone.com/platform/singularity-network-discovery/
  2. SentinelOne — Advancing Device Fingerprinting with Singularity Ranger. sentinelone.com/resources/advancing-device-fingerprinting-with-singularity-ranger/
  3. SentinelOne — Singularity Network Discovery datasheet. assets.sentinelone.com/iotranger/singularity-network-discovery-en
  4. SentinelOne Blog — SentinelOne Ranger IoT: Technology Preview. sentinelone.com/blog/sentinelone-ranger-iot/
  5. Help Net Security — SentinelOne turns every protected endpoint into a network detection device. helpnetsecurity.com/2019/03/08/sentinelone-ranger/
  6. 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.