VitalSec / Rusty
Minimum system requirements
Use this page to qualify desktop, server, mobile, browser, and network environments for VitalSec and Rusty. Deployment credentials, software-distribution authority, and provider permissions are handled as part of setup.
Rusty desktop and server agent
These are the minimum operating systems and architectures for the Rusty desktop and server installers.
| Platform | Minimum OS | Architecture | Package | Service | Installation notes |
|---|---|---|---|---|---|
| macOS | macOS 11.0 (Big Sur) or later | Intel x86_64 or Apple silicon | Signed + notarized .pkg | launchd daemon | Local administrator or enterprise software-deployment authority required. |
| Windows Server | Windows Server 2019 or later | 64-bit x64 | MSI | Windows Service | Older Windows Server releases are below the supported deployment minimum. |
| Windows client | Windows 10 version 1607 or later | 64-bit x64 | MSI | Windows Service | Enterprise deployment may use Intune or another software-distribution system. |
| Ubuntu | Ubuntu 20.04 LTS or later | x86_64 or ARM64 | DEB | systemd | A systemd-based installation is required. |
| Debian | Debian 11 or later | x86_64 or ARM64 | DEB | systemd | A systemd-based installation is required. |
| RHEL family | RHEL 8 or later; CentOS Stream 9 or later | x86_64 | RPM | systemd | Use the RPM package and service path. |
macOS installer signing
The Rusty macOS installer is signed with PatientLock LLC’s Apple Developer ID and notarized by Apple. macOS can validate the publisher and detect changes made after signing. Notarization checks the software for known malware before distribution.
How Apple checks downloaded software- Signing organization
- PatientLock LLC
- Apple Team ID
- 6SP7CJ499W
- Installer certificate identity
- Developer ID Installer: PatientLock LLC (6SP7CJ499W)
Rusty Mobile
Rusty Mobile extends signed device identity, enrollment, observation, heartbeat, and proof to iOS and Android. Device-management actions run through the organization's MDM/UEM or connected management system.
| Platform | Minimum OS | Device identity | VitalSec operation | Deployment |
|---|---|---|---|---|
| iOS | iOS / iPadOS 16 or later | Device-backed P-256 identity with Apple App Attest in the trust path | Signed enrollment, device observations, heartbeat, and proof | Install through the organization's Apple app-distribution path and enroll to the intended VitalSec environment. |
| Android | Android 9 / API 28 or later | Android Keystore P-256 identity with hardware-backed key support | Signed enrollment, device observations, background heartbeat, and proof | Install through the organization's Android app-distribution path and enroll to the intended VitalSec environment. |
VitalSec web application
No browser extension is required for normal workspace access.
- Current vendor-supported Chrome, Microsoft Edge, Safari, or Firefox
- JavaScript enabled
- Secure cookies enabled
- DNS resolution and outbound HTTPS to VitalSec
Network requirements
- Outbound traffic
- TCP 443 / HTTPS to the configured VitalSec service endpoints.
- Inbound ports
- No inbound Internet-facing port is required for the standard Rusty endpoint deployment; the agent initiates its connections.
- DNS + TLS
- The device must resolve the configured VitalSec endpoints and establish TLS connections.
- Proxy / filtering
- Proxy, TLS inspection, egress filtering, EDR, and application-control policy must permit enrollment, evidence delivery, and update traffic.
- Restricted networks
- Air-gapped, isolated, or intermittently connected environments use a deployment-specific connectivity plan.
Before deployment
Use the installer or mobile application and enrollment material assigned to the intended customer environment. Administrator, enterprise software-distribution, or mobile-management authority is used as appropriate. Existing firewall, proxy, EDR, MDM/UEM, application-allowlist, and change-control policy remains in force.
Integrations
Connecting a provider requires the organization's API credentials, permissions, tenant identifiers, and vendor handshake where applicable.
View integrations