Skip to main content

Device Agent

Overview​

The Device Agent is a lightweight beacon you install on managed endpoints. It checks in to Dralvia on a schedule so workspace admins can see which devices are active, what version of the agent they run, and (optionally) the results of target URL checks the device performed. It is built for visibility and presence, not for heavy endpoint control.

What it is for​

  • Confirm that protected devices are online and reporting.
  • Track agent version spread so you can plan upgrades.
  • Give your team lightweight endpoint context next to scan and email signals.
  • Feed device presence into the workspace activity views.

What it collects​

  • Hostname and operating system details.
  • Agent version.
  • Target URL check results (optional, only when enabled).
  • Minimal metadata for context (for example a device label).

It does not collect file contents, keystrokes, or browsing history. The beacon is intentionally small.

How to use it​

  1. Download the agent from the workspace device guide and install it on the endpoint.
  2. Enroll the device against your workspace using the enrollment token from the console.
  3. Confirm the device appears in the workspace device activity view after the first check-in.
  4. Roll out to more devices once you have verified one end to end.

UI: device check-ins appear in the workspace device activity view. API and automation details (enrollment, reading recent device signals) are in the workspace guide below.

Why use it​

A scan or email verdict tells you about a target. The Device Agent tells you about the fleet that is doing the work: which endpoints are live, which are stale, and which still run an old agent. That presence layer makes the rest of your Dralvia signals easier to act on.

Where it appears​

  • The workspace device activity view, for workspace admins.

Limits​

  • The agent reports presence and lightweight metadata; it is not an EDR replacement.
  • Target URL check results only appear when that option is enabled on the device.
  • Device history follows the standard workspace data retention window.