NetLock RMMNetLock RMM Docs
II — Console Reference

Managing Devices

Inventory, approvals, bulk actions, remote access, and the device world map.

Managing Devices

The Devices section is where most day-to-day RMM work happens. It covers the inventory of managed devices, the queue of agents waiting to be approved, device detail views with status and events, bulk operations such as remote shell commands or moving devices, remote desktop sessions, and a world map showing where your devices are located geographically.

The section is a top-level menu group with three sub-pages:

PageRoutePurpose
Devices/devicesInventory of authorized devices.
Unauthorized Devices/unauthorized_devicesQueue of agents pending approval.
Device World Map/device-world-mapGeographic view of device locations.

All three pages respect the currently selected tenant, location, and group context from the header selector. See Navigating the Console for how the context works.

Devices list with three devices with mixed status

3.1 Device inventory, filters, and labels

The Devices page lists every authorized device for the selected tenant / location / group. Each row shows status, identifying information, and quick actions.

Status indicators

Each device reports status in real time:

  • Online: the agent is currently connected to the server.
  • Online + Remote connected (pulsing): the agent is currently connected to the server and has a remote connection established.
  • Offline: the agent has not checked in within the expected interval.

Status changes appear without a page refresh (the page uses the Console's real-time update channel). If status updates stop arriving, a page reload re-establishes the connection.

A device that rate limiting on the server has blocked shows a red chip Blocked until <time> next to its name. Its requests are refused until that time, so the device goes Offline as well; the tooltip of the chip names the reason (for example Request rate above the limit for a sustained period) and the request class. With the permission settings_rate_limiting_enabled the chip is a link to the Rate limiting tab, where the block can be released. Blocks recorded in observe mode do not show a chip.

A device with an open security incident, or a device that is isolated after one, is shown with a red row and the chip 🕵️ Script kiddie alert; an isolated device also carries the chip Isolated. See 3.8 Security incidents.

Filtering and searching

The Devices list offers two filter controls: a free-text search box and an online-only toggle.

The search box performs a case-insensitive contains match across 14 fields at once. Rows where any of the following fields contains the search text remain visible:

  • device name and label
  • tenant, location, and group name
  • agent version and last-access timestamp
  • IP address, operating system, and domain
  • country, by its name in the language of your console (a two-letter term matches the country code whole)
  • antivirus solution and firewall status
  • last active user

The online-only toggle, when enabled, restricts the list to devices whose status is currently Online + Remote connected. Combined with a search term, it narrows the list to online devices matching the search text.

Columns

The column button (tooltip Configure columns) at the right end of the toolbar above the list opens the column chooser. It lists every column of the table: tick a column to show it, untick it to hide it, and drag a row or use its arrows to change the order (the arrows are the way on touch devices). The Name column is always shown and only its position can be changed. Reset to default restores the standard order and the standard set of visible columns. The column Endpoint protection is hidden by default.

The order and the visible columns are stored with your user account, not in the browser, and apply in every browser you sign in with; each table keeps its own layout. The same chooser is available on the SNMP tab of the list and on Unauthorized Devices (there the checkbox column and the actions column stay in place). Hiding a column only changes the view: the search box still matches the values of hidden columns, and the exports of the list always contain every column. Columns added by later releases appear visible at the end of the list.

Country of a device

The Country column shows the flag and the name of the country the device's external IP address belongs to, in the language of your console. The list sorts by it, the search box matches the name (or the exact two-letter code), and the column can be moved or hidden in the column chooser like the others (see Columns). The exports of the list (CSV, JSON, HTML) carry the country as country_code (ISO 3166-1 alpha-2) and country_name (the English name).

The country is determined by the server at every check-in, from the address the device connects from, against the GeoIP database bundled with the server; no lookup leaves the installation. A device that reaches the server through a private address (on the LAN of an on-premises server, through a VPN into the server's network, or on a single-host Docker installation) has no country and shows an empty cell. A device that leaves through a VPN or a proxy shows the country of that exit. The same value feeds the global search (country: operator), the public API (geoCountryCode and geoCountryName, see X.9.8), the Devices by country tile of the country restriction tab and the country restriction of the server.

Labels

Every device can carry a human-readable label. Rename it to something meaningful (Anna's laptop, Warehouse POS 3) using the Edit_Label dialog.

  1. Select the device in the list.
  2. Right click the label and open Edit_Label.
  3. Enter the new label and save.

Tenant / location / group assignment

Every device belongs to exactly one group, in exactly one location, in exactly one tenant. To move a device between groups, use the Move Device dialog. Moving a device may change which policy it receives, because policy assignment is driven by Automations that match on device attributes such as group name. Policy changes take effect within the device's sync interval.

3.2 Unauthorized devices and the approval flow

An agent that successfully contacts the server but has not yet been approved appears in Unauthorized Devices, not in the main Devices list. This keeps unknown or misconfigured agents out of your inventory until an administrator approves them.

Unauthorized devices queue

Next to the internal and external IP address of an entry, the queue shows the flag of the country the external address resolves to, so an agent that registers from an unexpected place stands out before it is approved; the country is resolved the same way as for authorized devices (see Country of a device).

The approval flow is:

  1. The agent is installed on a device with configuration that targets a specific tenant / location / group.

  2. The agent contacts the server and registers as unauthorized.

  3. An administrator reviews the entry in /unauthorized_devices: confirm the hostname, operating system, and the target tenant / location / group are correct.

  4. If the row carries the chip Name already exists, an authorized device of the same name exists in your tenants and the entry is most likely that device after a reinstall of its operating system (a reinstalled system gets a new hardware ID and, with a fresh installer, a new access key). Use the row action Adopt as reinstall instead of approving.

    The dialog lists the devices of that name with tenant and location, last contact, external IP address and online state, and preselects the device of the same tenant that is offline with the oldest contact. The chosen device takes over the new agent's access key and hardware ID and keeps its tenant, location, group, policy, label and history; the unauthorized entry is removed. Approving instead creates a second device. The action needs the same permission as approving. If the previous device still shows as online, the reinstalled agent also appears here for you to adopt.

  5. Adjust the target group if needed.

  6. Approve the entry. The device is created in the authorized inventory and begins receiving policies and automations.

  7. Optionally set a label immediately after approval using the Edit_Label dialog.

Entries that reported a security incident are shown in red with the chip 🕵️ Script kiddie alert, and the row action Show security incident opens the incident (see 3.8 Security incidents). Check such an entry before you approve it.

Rejecting an unauthorized device removes it from the queue; the agent re-registers on its next poll and reappears unless you block it at the network or agent level.

See the First-Run Walkthrough for a full end-to-end example, and Guide H.2 for a task-focused recipe.

3.3 Device detail view

Selecting a device in the list opens its detail view. The detail view shows everything the Console knows about the device:

  • Identifying information: hostname, label, tenant / location / group assignment, operating system, last-seen timestamp, IP addresses reported by the agent. The hardware section lists the manufacturer and model of every device; desktop agents report them from 3.3.0.11 on (Windows, Linux, and macOS as Apple with Model Name (Model Identifier)), older agents show Not reported.

  • Geo location: below the external IP address, the line Geo location shows the flag, the city, the region and the country of the external address. City and region are resolved against the GeoIP database of the Web Console when the device is opened; the country stored with the device is used when the database has no record. The line appears only for a public external address; a device behind a private address shows Geo location: Not available for a private address instead, and a device that leaves through a VPN shows the location of the VPN exit, as on the world map.

  • Status: current online / offline / error state, and the agent version.

  • Custom fields: values for every custom field defined in Collections, editable per device. Each field is one Label: value line like the other device details: a multiline value keeps its line breaks, a long value is shortened to four lines with Show more, an empty field shows -, and the copy button next to a value copies it. A manual field without a device value shows the value inherited from the group, location, tenant or global level greyed out, with an icon whose tooltip reads Inherited from …; a value written by a script or the public API has an icon with the tooltip Set by script on … or Set by API on …. On phones and touch devices these texts appear under the value instead. A Secret field shows a mask and a Reveal secret button for accounts with the reveal permission.

  • Events: recent operational events scoped to this device; a link into the full Events page is available.

  • Policy: the single policy currently assigned to the device (or - if no automation matched and no default policy is set). A policy that comes from the default policy is marked Default policy.

    A +N chip next to the policy in the list counts the sensors and jobs that automation rules add on top of it; its tooltip names them and the rule each comes from. The detail view lists them under Assigned policy as Additional sensors and Additional jobs, expandable to name and rule, and warns when rules would add items to a device that has no policy, because nothing is handed out then. Only items the device actually receives are shown: a sensor for the device's platform, a job for its platform or platform System.

    The list and the detail show the state the device last received from the server (the decision of its last evaluation), not a fresh evaluation of the rules. A device that has no stored state yet, while rules on services, applications or custom fields exist, shows - with an hourglass and the tooltip Evaluated at the device's next sync. See Chapter 5 — Automations for how assignment works, Chapter 5.2.2 for when a change shows up and Chapter 5.6 for the items.

  • Actions: per-device operations (remote control, remote shell, file browser, registry editor, event log viewer, service manager, wake-on-LAN, uninstall application, SNMP tools) and the bulk actions covered in 3.4 and 3.5.

The per-device actions open the dialogs below. Each dialog targets the currently selected device (or the set selected for bulk actions):

CategoryDialogs
Lifecycle and assignmentEdit Label, Move Device, Move Devices (bulk), Remote Authentication
Remote controlRemote Control
Remote shellRemote Shell, Bulk Remote Shell, Bulk Remote Shell Results
Remote file browserFile Browser, Create File, Create Directory, Rename File, Rename Directory, Move File, Move Directory, View File, operation results
Remote registry editor (Windows)Registry Editor, Create Key, Create Value, Edit Value
Remote event log (Windows)Event Log viewer, Event Details, Event Log Statistics
Services managementService Editor (Windows), Service Editor (Linux / macOS)
Diagnostics and toolsEvent Details, SNMP Tools, Uninstall Application
NetworkWake on LAN

The exact availability of some dialogs depends on the device's operating system: for example, the Registry Editor is Windows-only, and the Linux / macOS Service Editor applies only to Linux and macOS devices.

Editing custom fields on a device

  1. Open the device detail view and the tab or section the definition contributes.
  2. Click the pencil next to the value. The field opens for editing on its line; a Secret value is typed into an empty password field.
  3. Save with the check mark, or press Enter (Ctrl+Enter in a Multiline field). Escape or the cross discards the change. Leaving the field does not save it, and an empty value cannot be saved.
  4. To let the device inherit the group, location, tenant or global value again, open the editor, click Remove device value and confirm. The device's own value is deleted and the inherited value appears greyed out with its Inherited from … icon; without an inherited value the field shows -.
  5. Reveal secret next to a secret field shows the stored value. It requires collections_custom_fields_reveal_secrets and writes an audit entry each time.

Editing needs collections_custom_fields_edit; without it no pencil is shown and the fields are read-only. Only Manual fields can be edited; Job Result and SQL Select fields are read-only for every account. Every saved value marks the device for a policy re-sync, so scripts that use the value receive it at the next check-in. When an automation rule compares the field, the rules are evaluated for the device right away and the device is pushed when its assignment changed (see Chapter 5.2.2). Defining which custom fields exist, and setting values on tenant, location, group or global level, happens at the Collections level; see Chapter 8.4 — Custom Fields. Scripts read the values through variables and can write them back; see Script variables and custom fields in scripts and Write custom field values from a script.

Viewing per-device events

The detail view shows the Events feed filtered to the events of this device. This is usually where you go first to diagnose why an action did not take effect: a failed policy deployment, a script that did not run, a sensor without readings.

For the full events reference, see Chapter 12.

USB Devices tab (Windows)

The USB Devices tab of a Windows device lists the whitelist entries that apply to the device and the devices it reported as blocked. Above the list, a status line shows the device's Device Control learning state:

Status lineMeaning
Learning connected devices until …A learning period runs. Every device connected in this time is whitelisted for this device.
Learning the devices connected when learning started (at the latest until …)A period of the kind Devices connected when learning starts runs.
Learning requested; it starts at the next policy sync of the deviceA re-learn was requested and starts when the device fetches its policy.
Connected devices learned on … under policy …The last learning period has ended.
Learned under the policy-wide auto-whitelist of an earlier version; no learning period is runningThe device learned before 3.3.0.11.
Connected devices have not been learned on this deviceNo learning has happened yet.

Two actions sit next to the status line:

  • Re-learn connected devices: the device learns the devices connected to it again, for the learning period of its policy, starting at its next policy sync. The sync is requested right away, so a connected device starts within moments. The device's policy must have Device Control on; otherwise the console says so and nothing is changed.
  • End learning now: shown while a period runs or is requested. It ends the period at once; devices connected afterwards are blocked unless a whitelist entry applies to them.

Both actions ask for confirmation and, where it is set up, for the same additional sign-in confirmation as the other remote tools. They require the permission devices_usb_learning and access to the device's tenant, and each one is written to the audit log. devices_usb_learning is part of the built-in Administrator role and of the Technician template; the Helpdesk, Read-only and Reporting templates do not include it. For the learning options of a policy, see Chapter 6.8. To let several devices re-learn at once, use Re-learn connected devices on the Whitelist tab of Device Control (see Chapter 8.7).

3.4 Bulk actions

The Devices page can run one operation on many selected devices at once:

  • Bulk remote shell: execute a command on every selected device and collect the results.
  • Move devices: move the selected devices to another group with the Move Devices dialog.

Only one selection mode is active at a time: switching on moving devices or bulk remote shell switches the other off and clears the selection.

The bulk remote shell flow uses two dialogs:

  • Bulk Remote Shell: pick the command to run, confirm the target set, and launch.
  • Bulk Remote Shell Results: display per-device results as they arrive, including stdout, stderr, and exit status.

Each device in the bulk dialog shows a status:

StatusMeaning
PendingNothing has been executed yet.
ExecutingThe command was sent and the device has not answered yet.
CompletedThe device returned its output. An answer that arrives after the timeout is still shown and switches the device to Completed.
TimeoutThe device did not answer within the timeout set in the dialog.
Not connectedThe device has no connection to the remote agent. The command is not sent to it.
RejectedThe command was not executed because the device's policy disables the remote shell or your account may not use the remote shell on this device. The output names the reason.
FailedThe command could not be sent or delivered, or the connection between the console and the NetLock RMM server was lost before the device answered.

"Online" in the device list is not the same as "remote connected". A device counts as online while its Comm agent checks in, but remote shell commands go through the Remote agent's connection to the server. A device whose Remote agent is stopped, still reconnecting or blocked by rate limiting, as well as every Android and iOS device, can show as online and still be "Not connected". The dialog checks the remote connection when it opens and again when you execute, lists how many devices are skipped, and counts them as done in the progress counter. The pulsing green status icon in the device list marks devices whose Remote agent is connected.

Warning: Bulk actions run on every selected device without further per-device confirmation. Double-check the selection before you launch a bulk command on a production fleet.

Tip: For repeatable work, save the command as a script in Collections and invoke the script rather than typing the command every time.

3.5 Remote control and remote shell

Individual devices support remote access via the Console:

  • Remote shell: a fire-and-forget shell session on the device (PowerShell on Windows, Bash or the default shell on Linux and macOS), opened from the Remote Shell dialog. Every completed classic remote shell command writes an event "Remote shell command executed." (type Remote Shell) on the device with the output; the command text itself is not stored.
  • Real-Time Remote shell: an interactive shell session on the device (PowerShell on Windows, Bash or the default shell on Linux and macOS), opened from the Remote Shell dialog.
  • Remote control: a graphical remote-control session to the device's desktop, opened from the Remote Control window.

How remote control works

Remote control in NetLock RMM does not use VNC or RDP. The agent captures the device's screen and streams it as JPEG frames through the NetLock server to the viewer; mouse, keyboard and clipboard travel the same way back. Remote Control on the device opens the remote control window, which connects to the server and starts the session; there is no transport to choose.

The same session can be opened from the Relay App and the NetLock app with a relay API key. What each viewer offers, how a session starts on Windows, Linux and macOS devices, recording, the clipboard and pasting files are described in A.7 Remote screen control; the stream modes are in A.7.5, the viewers in A.7.9. For the Relay App see Remote-control a device with the Relay App.

3.6 The Device World Map

The Device_World_Map page at /device-world-map visualises your fleet geographically. Each device is plotted on a world map based on IP-geolocation data captured when it reports to the server.

Device world map with clustered pins

Use cases include:

  • Confirming a device claims to be where you expect it to be (an unexpected pin in another country deserves a closer look).
  • Assessing the impact of a regional issue, for example how many devices are on a specific coast during a power event.
  • Communicating fleet spread to non-technical stakeholders in a single screenshot.

The map respects your tenant / location / group context: selecting a tenant in the header narrows the map to that tenant's devices only.

Note: Map accuracy depends on the quality of IP geolocation for the device's external IP. Devices behind a VPN will appear at the VPN exit rather than the physical device location. The IP lookup happens locally on your NetLock RMM server; no lookup leaves the server. The details drawer of a marker shows the flag of the country next to the resolved place. The Country column of the devices list and the Geo location line of the device details use the same database (see Country of a device), and so does the country restriction of the Web Console and the server.

3.7 Web interface

Many devices carry a web interface of their own: the management pages of a printer, a switch, a UPS, a NAS, or a web server running on the device itself. Web interface opens such a page in a browser window of its own, without a VPN and without a Relay App. The agent fetches the page and the NetLock server serves it to your browser through a temporary relay session, so the page appears under the address of your NetLock server.

Agent devices

For a device with an agent, the entry sits in two places:

  • Context menu: right-click the device row. The Web interface sub menu offers HTTPS (443), HTTP (80) and Custom…. The first two open the interface of the device itself straight away; Custom… opens the dialog.
  • Device details: the Web interface button in the action bar of the selected device opens the dialog.

The dialog asks for the target, the scheme and the port:

  • Web interface on this device: the interface the device serves itself (the agent connects to 127.0.0.1).
  • Remote host reachable from this device: a host on the device's network, given as hostname or IP address without scheme, path or port. The device acts as a jump host, as it does for a relay session.
  • HTTPS / HTTP: switching the scheme moves the port between 443 and 80 as long as the port is still one of the two defaults; a custom port stays.
  • Port: 1 to 65535.

Open opens a new browser window. The window checks your permissions and the device, asks the server for the session and then shows the device page. The first request can take up to 20 seconds while the agent opens the connection.

SNMP devices

The SNMP list of the devices page offers the same action for printers, switches and other SNMP devices. The Actions column of the list and the Web interface button in the detail panel open the dialog with the address of the SNMP device filled in. Because an SNMP device has no agent, one of the agents that know the device carries the connection: the agent that monitors it, the agent that discovered it, or any agent that has reported it in a discovery scan. The dialog lists these agents, online agents first, with the monitoring agent preselected. An SNMP device that no agent monitors, discovered or reported has no agent to carry the connection; the action is shown disabled and the tooltip says why.

Sessions and limits

Every web interface opened this way is a web access session: a temporary relay session of kind "Web" that is listed on the Relay Server page and can be closed there (see Chapter 9.2 — Web access sessions). What to expect:

  • The session ends after 15 minutes without a request or WebSocket traffic, or after 8 hours at the latest, whichever comes first. Closing the browser tab does not end it; the idle timeout does. Opening the same target again while the session is alive reuses it.
  • Only the account that opened the session can use the window. The link the window follows works once and for 60 seconds; afterwards a browser cookie bound to the session is required, so the address cannot be handed to somebody else.
  • Device pages with self-signed certificates work. The connection between your browser and the NetLock server keeps its own certificate.
  • Downloads (logs, configuration backups) and uploads (firmware) are streamed. Behind your own reverse proxy make sure request bodies are not limited and read timeouts allow long uploads.
  • Pages that load their assets from absolute paths, redirect, set cookies, ask for a password (Basic or Digest authentication) or use WebSockets work. WebSockets are forwarded like any other request, also when the page opens them on an absolute root path (wss://<server>/api/...), which single-page interfaces of NAS systems, hypervisors and network controllers do. A page that only talks over its WebSocket after loading counts as active; the idle timeout starts once the socket is quiet.
  • Pages that declare a base address (<base href="/">, usual for Blazor, Angular and many other single-page interfaces) are delivered with the base address inside the session, so their links, scripts, sockets and client-side navigation stay in the session. Sign-in forms of such applications, including their protection cookies, work as well. Pages that set their base address from a script or build addresses from the server root keep using the redirect of absolute paths described above.
  • Two limits of WebSockets on absolute root paths: a socket whose handshake needs a cookie the device set works only when the page opens it under the session address (device cookies are scoped to the session; a socket on a root path carries none), and with two device pages open in the same browser such a socket goes to the page that was shown last.
  • Web app manifests (site.webmanifest) are fetched by browsers without cookies and therefore answered with 404 through the proxy; the page itself is not affected.
  • Two device pages in two tabs work.

Every opened interface is written to the audit trail with scheme, host, port and the device that carried the connection, and the step-up authentication of the remote tools applies.

3.8 Security incidents

The NetLock agent recognizes signs that it is being analyzed or tampered with on a device, for example tools for analyzing or modifying software, an attempt to inspect the agent's own components while they run, signs that the agent's connection is intercepted or redirected, traces of such tools on the device, and signs that the device is operated as an analysis or sandbox environment. When it finds them, it sends an encrypted report to your NetLock server, and only to your server. The detection applies to authorized and unauthorized devices.

What a report contains

A report describes the finding and the state of the device at that moment:

  • Reason: one or more of analysis tools, inspection of the agent, interception of the connection, traces of analysis tools, a device that appears to be operated as an analysis or sandbox environment.
  • Findings: the tool name, the kind of finding (process, shortcut, folder, proxy, certificate and similar), path, user, start time and whether the file is signed.
  • Network: configured proxies, local listeners, interception certificates, network adapters with addresses, gateways and DNS servers.
  • System: device name, domain, operating system and build, architecture, last boot, time zone, manufacturer and model, virtual machine hint, antivirus and firewall state.
  • Sessions: signed-in users with session type and logon time (client name and address for remote sessions), and the local administrators.
  • Processes: a compact list of running processes (name, process ID, parent, user, path).
  • New software: programs installed within the last 30 days.
  • Agent: installation time, installer package and authorization state.

A report contains no file contents, credentials, browser data or history, screenshots, keystrokes, clipboard contents, e-mails or document names. The server adds the public IP address the report came from. The content comes from the device and is treated as untrusted: the Web Console shows it as plain text only.

The incident dialog

Click the chip, use Security incidents in the right-click menu of /devices, or the row action on /unauthorized_devices. The dialog shows the device, its tenant and location, the status (open, acknowledged, whitelisted, isolated), first and last report and the number of reports. For each incident it shows the reason, the findings, the data the agent deleted (for an isolated device, see below) and the context sections listed above. A device with several incidents has a selector; the newest is preselected.

Actions:

  • Export JSON: downloads all incidents of the device with their full reports (security-incident-<device>-<date>.json). The export is written to the audit log.
  • Acknowledge: marks the open incidents as acknowledged. The row is no longer red unless the device is isolated; a new report marks it again.
  • Whitelist device: the server no longer stores reports of this device and never isolates it. Open incidents are acknowledged and an active isolation is released. Use it for technician machines that legitimately run analysis tools. Remove from whitelist reverts it.
  • Release isolation: see below.

Isolation

Unless the device is whitelisted or the automatic isolation is switched off, a device with a new incident is isolated:

  • It receives no policy, no jobs, sensors or scripts, no software deployments and no files from the server. Automations, App Hub, SNMP results and NetMesh links are refused for it as well.
  • The agent deletes locally cached data that came from the server (jobs, sensors, scripts, policy, App Hub data, logs and similar) and resets its local settings to defaults. Its connection to the server, its identity and the Endpoint Protection state stay in place. Device Control and App Control keep running with their last known state. The agent reports what it deleted, reset, kept and could not delete; the dialog shows this as Data deleted by the agent.
  • The device moves to the location Isolated of its tenant (Isolated (NetLock) if the tenant already has a location of that name). The system creates this location on first use; it cannot be renamed or deleted and no installers are built for it. The previous location and group are kept for the release. Technicians of the tenant keep seeing the device.
  • An unauthorized device stays unauthorized and remains on /unauthorized_devices. To analyze it, use Release for analysis in the incident dialog: the device is authorized, so remote shell, file browser and the other remote functions become available, but it stays isolated, stays in the location Isolated and still receives no policy, scripts or files. Releasing the isolation later returns it to the unauthorized state. Approving such a device the normal way keeps the isolation as well; that approval is kept when the isolation is released.
  • Remote functions (shell, file browser, task manager, services, screen control, event log and registry) stay available for an analysis, subject to the usual permissions, Endpoint Protection rules and audit log. Treat everything that comes from the device as untrusted and open downloaded files only in an analysis environment.

Release isolation acknowledges the open incidents, returns the device to its previous location and group, restores its previous authorization state and marks it for a sync; the agent leaves the isolation with its next status check and receives its policy again. The device is isolated again only if the agent reports new tools; to stop the reports entirely, whitelist the device. If the previous location no longer exists, the device stays in Isolated and has to be moved manually; a device that was moved out of Isolated by hand keeps its location.

Installer package

The dialog names the installer package the agent was installed with and how many devices were installed with it. If the installer has leaked, two options are available:

  • Block new registrations only: the package can no longer register new devices; devices already installed with it keep working. This works for every package, including packages created through the agent download. Allow new registrations again reverts it.
  • Revoke and regenerate package: for managed packages only. The package ID is revoked and a new one is created, with new installers built in the background. Every device installed with the old package loses its connection and has to be installed again; a warning lists the number and the names of the affected devices first. This additionally needs the permission agent_installers_enabled.

Settings and events

Settings → Security → Security incidents has two switches, both on by default: Detect security incidents (off: the server stores no reports and isolates no devices) and Isolate automatically on an incident. Changing them needs the permission of the rate limiting settings.

Each incident writes one event of the type Script kiddie alert with the reason, the isolation and the deleted data, available in the event list and the dashboard event widgets.

Permissions

Device-related permissions follow the standard pattern:

  • A top-level permission enables the Devices section.
  • Per-action permissions gate bulk actions, remote shell, remote desktop, approvals, and label editing.
  • The Web interface action needs relay_server_enabled and relay_web_access from the Relay Server group; for SNMP devices the sensors permission that shows the SNMP list as well.
  • Security incidents: devices_security_incidents_view opens the incident dialog and the JSON export, devices_security_incidents_manage acknowledges, whitelists, releases a device for analysis, releases an isolation and blocks the installer package. The red row and the chip are visible to everyone who sees the list.
  • Android devices: devices_remote_control covers viewing their screen and, when the policy allows it, controlling it (A.7.12); devices_mobile_locate locates a device and lets it ring, devices_mobile_message sends it a message.
  • Tenant-scoped users only see devices in tenants they have access to.

See the Permission reference for the full list.