01
Observe actual state
Read device identity, software inventory, and supported control state from the endpoint itself so VitalSec works from current endpoint evidence instead of stale assumptions.
VitalSec platform
Rusty™
The endpoint should prove what changed.
Rusty is VitalSec's cross-platform endpoint agent family across Windows, macOS, Linux, iOS, and Android. On desktops and servers it reads what is actually true on the device, carries out approved host-side actions, and reads the endpoint again so VitalSec can verify the result. Rusty Mobile extends signed device identity, observation, heartbeat, and proof to iOS and Android, with management actions flowing through the customer's MDM or UEM.
WindowsmacOSLinuxiOSAndroid
Endpoint state · approved action · proof
One agent family across desktop, server, and mobile endpoints.
VitalSec keeps policy and permissions centralized. Rusty performs approved host-side actions on supported desktop and server endpoints; Rusty Mobile contributes signed mobile state and uses the customer's authorized MDM or UEM path for managed changes.
Why Rusty matters
The endpoint is where the control has to work.
Security products routinely tell you that a policy exists, an alert fired, a ticket closed, or a command was accepted. Rusty closes the last mile between that administrative record and the state reported by the endpoint itself.
02
Sign at the source
Tie endpoint observations to device identity and signed telemetry so the evidence shows which endpoint produced it.
03
Carry out approved fixes
Run supported host-side corrective actions only when the customer has approved that action for that endpoint. Rusty does not make policy or give itself permission.
04
Re-read the result
Read the relevant endpoint state again after an action so VitalSec can verify the outcome instead of treating a command receipt as proof.
Control loop
From required state to a verified result.
VitalSec still sets policy and permissions. Rusty gives it a reliable way to read the endpoint, carry out approved changes where the endpoint supports them, check the result, and preserve the evidence.
01
Observe
Read actual endpoint state
02
Act
Execute approved change
03
Validate
Re-read material state
04
Prove
Persist signed evidence
Without a local endpoint agent
Policy and desired state live somewhere else.
Endpoint state can change between scans and heartbeats.
A ticket closure or command receipt can become the proxy for success.
Evidence is reconstructed later from several disconnected systems.
With Rusty in the loop
Each endpoint reports current state tied to its device identity.
Approved actions can run on the same desktop or server endpoint that reported the problem.
Material changes are followed by a fresh read of the endpoint.
Signed evidence can flow directly into Evidence Continuity, VUMA, CAAT, ShadowAI, and risk measurement.
What Rusty records
Evidence tied to the endpoint and the change.
Each observation is tied to endpoint identity, time, and source. When Rusty carries out an approved action, the record also shows what was true before the change and what was observed afterward.
Identity
Device and operating-system identity, local trust state, and agent lineage.
Software
Installed application and package inventory used by vulnerability, ShadowAI, and operational workflows.
Controls
Supported endpoint-control observations with freshness instead of a timeless green check.
Action
Approved execution instructions, receipts, and the endpoint state observed after material change.
Permissions and limits
Rusty acts only within the permissions you set.
Rusty does not make policy decisions or give itself permission to act.
A command receipt is not proof that the required endpoint state now holds.
Desktop and server changes are limited to actions the customer has approved and the host is allowed to perform.
Mobile management actions flow through the customer's authorized MDM or UEM; Rusty Mobile does not create a separate management authority.
When an endpoint is disconnected, VitalSec shows its central view as stale or offline until fresh evidence returns.
Why the name Rusty
Built in Rust. Named accordingly.
Rusty is written in Rust. PatientLock chose Rust for an endpoint agent because the language combines memory safety with small binaries, strong cross-platform support, and a mature cryptographic ecosystem.
The name is a direct nod to that implementation lineage.
Rust lineage
Memory safety. Compact binaries. Cross-platform endpoint execution. Cryptographic primitives close to the source.
From endpoint to platform
Endpoint evidence feeds the rest of VitalSec.
VUMA
Endpoint and software evidence for vulnerability applicability, remediation, retest, and closure.
CAAT
Endpoint evidence for approved control testing when the test and customer permissions allow it.
Evidence Continuity
Endpoint observations, action history, and evidence showing what the device reported afterward.
ShadowAI
Installed AI-client and developer-tooling evidence tied back to the endpoint.