Secure DeskRemote Support Built With Security in Mind.
When the screens you support may show sensitive information, you need to know who can connect, where the traffic goes, and that no one in the middle can watch.
Sound familiar?
Sensitive screens
Remote support can expose patient records, financial data or other confidential information.
Third-party clouds
Many tools route every session through a vendor's servers you don't control.
Proving control
Auditors and security teams want clear answers on access, encryption and logging.
Practical tools for exactly this job.
Encrypted sessions
End-to-end encryption between the console and the device. The relay forwards ciphertext only.
Self-hosted
Run the portal and relay on your own infrastructure — no vendor cloud in the path.
Controlled access
Enforced two-factor sign-in, SSO, and admin/operator/viewer roles on Business.
Administrative visibility
A portal audit log of the last 200 events on Business, plus events to ship to your SIEM.
Credentials stay local
Admin passwords used for elevation are used once on the target and never stored or logged.
Smaller exposure
Endpoints dial out — no inbound firewall rules on the machines you support.
Security-conscious IT workflows.
Prefer attended sessions for everyday help, and reserve unattended and SYSTEM access for the cases that need it.
- Portable connector — user starts and stops it
- Matching 6-digit code to confirm the right PC
- TLS 1.2+ on every hop, AEAD ciphers
- Relay designed to sit outside the cardholder-data environment
Select any part of the diagram to see what it does.
A note on compliance. Secure Desk is designed with safeguards such as access controls, encryption and auditability in mind. That is not a claim that Secure Desk is “HIPAA certified” or “PCI certified,” or that any deployment meets a specific regulation. Compliance depends on your environment, configuration and processes — validated by you and your assessor. Where Rubix acts as a business associate, a Business Associate Agreement is available when applicable.
Common questions
Is Secure Desk HIPAA compliant?
No software is compliant on its own. Secure Desk is designed with HIPAA safeguards in mind and can support a compliant deployment, but it is not HIPAA certified. A Business Associate Agreement is available when applicable.
Can Secure Desk be used in a PCI-scoped environment?
It's designed to support a PCI-scoped deployment — TLS 1.2+, a relay outside the cardholder-data environment, per-session identity and loggable events. Validating compliance is the work of your organization and your assessor.
Who can see a session?
Only the technician's browser and the Windows device. The relay you host forwards encrypted data it holds no key for.
Are backstage commands logged?
No. Backstage commands are not logged and roles don't isolate backstage per technician, so limit who can open sessions on enrolled devices.
Support sensitive environments with confidence.
Evaluate Secure Desk on your own infrastructure with the free Starter plan.