Search
Ctrl+K
Usability
5
Automation
3
Security
4
Infrastructure
4
On this page
Documentation for monitoring endpoint compliance, inspecting installed software and code dependencies, using the remote web terminal, and running host response actions in Shuffle Security.
Shuffle Security (shuffle.security/monitors) provides lightweight endpoint posture monitoring, software/dependency discovery, and live remote response across macOS, Windows, and Linux hosts.
Instead of deploying a separate endpoint tool that cannot talk to your incidents or vulnerabilities, Host Monitors connects your endpoints directly to your Shuffle workspace so you can verify compliance, spot vulnerable packages, and run live forensics or containment from a single UI.
package.json, requirements.txt, Cargo.toml, go.mod) to surface CVEs in Vulnerabilities.NoteZero License Paywalls
Host Monitors is included in both Shuffle Cloud and self-hosted open-source deployments with no per-seat or per-agent license fees. Normal heartbeats and posture checks consume zero app runs; standard app runs only execute when your automation workflows trigger remote actions.
Navigate to /monitors to view compliance posture and manage all registered endpoints across your fleet:
healthy, stale, offline).All, macOS, Windows, Linux) or search by hostname and IP address.Use the interactive panel above, or navigate to /monitors and click Add Host in the top-right header bar to generate an installer command for your endpoint.
/monitors in Shuffle Security.hd_encrypted)screenlock)installed_software)code_scanner_enabled)response_actions)The Add Host dialog generates a pre-authenticated one-liner for your tenant and monitoring group:
macOS & Linux:
cURL
Editable
Response
Windows (PowerShell as Administrator):
powershell
Editable
Response
If you prefer to deploy the binary manually or via configuration management (Ansible, Chef, Puppet, MDM):
orborus binary for your OS and CPU architecture from github.com/Shuffle/orborus/releases.Bash
Editable
Response
Host Monitors continuously evaluate endpoints against baseline security controls and report compliance back to /monitors:
hd_encrypted)Verifies that full-disk encryption is active on the primary system volume:
C:).screenlock)Verifies that the operating system locks the display after a maximum of 15 minutes of user inactivity and requires password or biometric authentication immediately upon wake.
log_forwarding)Active event and log streaming from monitored hosts is currently in development and not generally available yet.
When Installed Software (installed_software) is enabled on a host:
/monitors, or click any application to view all hosts running that software at /software/<name>.When Code Package Scanner (code_scanner_enabled) is enabled on developer workstations or build servers:
package.json (npm/yarn), requirements.txt / Pipfile (pip), Cargo.toml (Cargo), and go.mod (Go)./packages/<name>.Open an interactive shell on any monitored host from the Actions column in /monitors, inside the host detail drawer, or at /monitors/:id/terminal:
ps aux, netstat, df -h, log inspection) directly in your browser and share terminal output across your team.When Response Actions (response_actions) is enabled on a host, admins and authorized workflows can trigger predefined actions from the host detail panel or /monitors/response:
screenshot): Captures the current display of the active user session.isolate_host): Restricts network connectivity on the endpoint while keeping the Shuffle management channel alive (requires root on Linux/macOS or SYSTEM on Windows).unisolate_host): Restores normal network connectivity on an isolated endpoint (requires root or SYSTEM).disable_rce): Permanently disables remote command execution on the host monitor daemon.remote_control): Sends automated input actions (mouse click/move, keystrokes, shortcuts) on Windows hosts.NoteControlled execution (restricting commands to pre-approved script files) is currently in development. You can manage which automated response actions AI agents are permitted to run at
/monitors/response.
Under the hood, Host Monitors runs Orborus (Shuffle's lightweight Go worker binary) in sensor mode (--sensor_mode=true) rather than requiring a separate third-party agent:
| Platform | Supported Versions | Monitored Controls |
|---|---|---|
| macOS | macOS 12 Monterey, 13 Ventura, 14 Sonoma, 15 Sequoia | FileVault 2 disk encryption, screen lock idle timeout, installed applications catalog, local repository manifests |
| Windows | Windows 10, Windows 11, Windows Server 2016+ | BitLocker drive protection, screen lock inactivity policy, installed applications, local repository manifests |
| Linux | Ubuntu, Debian, RHEL, CentOS, Fedora, Arch | LUKS volume encryption, screen lock idle timeout, system packages, local repository manifests |
Each Monitoring Group in /monitors maps to an Orborus sensor queue, allowing you to segment endpoints by environment or location (e.g. production-eu, corporate-laptops, staging) while orchestrating actions from Shuffle workflows.
Host Monitors stores endpoint telemetry across four specialized datastore categories so hardware specs, application inventories, manifest dependencies, and live heartbeats remain decoupled and fast to query:
shuffle-security_assets: Hardware inventory, system specifications, ownership, and network metadata.shuffle-security_software: Operating system applications, daemon versions, and installed binary catalogs across hosts.shuffle-security_packages: Code libraries and project manifest dependencies (package.json, requirements.txt, Cargo.toml, go.mod) scanned from developer repositories.shuffle-security_sensors: Monitor daemon runtime state, heartbeats, posture check baselines (hd_encrypted, screenlock), and response capabilities.Inspect these categories directly in the Datastore console:
/admin/datastore?category=shuffle-security_assets (Shuffle Datastore)/admin/datastore?category=shuffle-security_software (Shuffle Datastore)/admin/datastore?category=shuffle-security_packages (Shuffle Datastore)/admin/datastore?category=shuffle-security_sensors (Shuffle Datastore)shuffle-security_assets)Keyed by hostname or asset identifier (e.g. srv-prod-db-01 or dev-macbook-pro-14).
| Field | Type | Description |
|---|---|---|
id | String | Unique asset identifier (e.g. asset-srv-prod-01). |
hostname | String | Primary hostname reported by the endpoint. |
os | String | Operating system name and release (e.g. Ubuntu 22.04.4 LTS, macOS 15.1 Sequoia). |
architecture | String | CPU architecture (x86_64, arm64). |
cpu_cores | Number | Number of virtual or physical CPU cores. |
ram_gb | Number | Total physical memory in gigabytes. |
disk_gb | Number | Total system storage capacity in gigabytes. |
ip | String | Primary IPv4 address. |
mac_address | String | Network interface MAC address. |
serial_number | String | Hardware or hypervisor serial number. |
environment | String | Environment tier (production, staging, workstation). |
tags | Array | Organizational labels (e.g. ["database", "postgresql", "critical"]). |
owner | String | Responsible email or team handle. |
status | String | Lifecycle status (active, decommissioned, maintenance). |
shuffle-security_software)Keyed by software identifier (e.g. sw_docker_engine_26, sw_openssh_server_9).
| Field | Type | Description |
|---|---|---|
name | String | Application or binary name (e.g. Docker Engine, OpenSSH Server). |
version | String | Detected software release version string. |
publisher | String | Vendor or software maintainer. |
install_type | String | Packaging format (system_binary, deb_package, rpm_package, application_bundle). |
install_path | String | Primary executable path (e.g. /usr/bin/docker, /Applications/Google Chrome.app). |
hosts_count | Number | Total count of fleet endpoints running this application. |
associated_hosts | Array | List of hostnames where this software version was detected. |
last_scanned | Number | Unix epoch timestamp of the most recent inventory sweep. |
shuffle-security_packages)Keyed by package identifier (e.g. pkg_lodash_4_17_20, pkg_requests_2_31_0).
| Field | Type | Description |
|---|---|---|
name | String | Package library name (e.g. lodash, requests, xz-utils). |
version | String | Exact installed version discovered in manifest. |
ecosystem | String | Package ecosystem (npm, pip, cargo, go, deb, maven). |
manifest_file | String | Source manifest filename (package.json, requirements.txt, Cargo.toml, go.mod). |
repository_path | String | Absolute directory path where the dependency manifest resides. |
host | String | Hostname of the machine running the code scanner. |
has_vulnerability | Boolean | True if the package version matches an active OSV/CVE advisory. |
advisory_id | String | Linked CVE or GHSA identifier (e.g. GHSA-7867-xwm8-2v3q), or null if clean. |
fixed_version | String | Recommended patched version if vulnerable. |
shuffle-security_sensors)Keyed by host sensor ID (e.g. sensor_srv_prod_db_01).
| Field | Type | Description |
|---|---|---|
host_id | String | Unique daemon runtime identifier. |
hostname | String | Hostname associated with the daemon instance. |
platform | String | Operating system family (linux, macos, windows). |
agent_version | String | Running Orborus sensor version. |
sensor_group | String | Configured Orborus queue group (e.g. production-eu). |
status | String | Daemon heartbeat status (online, offline). |
last_heartbeat | Number | Unix epoch timestamp of the latest ping. |
compliance | Object | Posture check results: hd_encrypted, screenlock, filevault, firewall_active. |
capabilities | Array | Enabled monitor features: installed_software, code_scanner, remote_terminal, response_actions. |
Python
Editable
Response
Every key across all four monitor categories (shuffle-security_assets, shuffle-security_software, shuffle-security_packages, shuffle-security_sensors) is stored with immutable revisions:
hd_encrypted, screenlock) changed state.API Call
Response
No response received.
Python
Editable
Response
List Sensor Groups / Environments: GET /api/v1/getenvironments (filter by sensor_group === true)
Execute Remote Host Action:
API Call
Response
No response received.
Query Host from Datastore Directly:
API Call
Response
No response received.
Python
Editable
Response
For more details on backend API endpoints and datastore caching rules, see the API documentation.