Protection at every step
Credential protection, individual permissions and access limited to published resources.
-
Your password stays protected.
Not in a database, not in a file, not in a log, not in telemetry. It exists in memory for the life of the portal session, and it is explicitly wiped.
-
Authorization by SID, never by account name.
Renaming a user in Active Directory does not hand access to anyone else.
-
Deny by default.
No resource is reachable by omission. Only what was explicitly associated opens.
-
No sensitive parameter comes from the browser.
Executable path, arguments, RDP host and credential are never accepted from the client. Tampering with what the browser sends cannot ask for another program to be opened.
-
The session ticket is short-lived and single-use.
And it is bound to the authenticated session that issued it.
-
The RDP engine is never exposed to the network.
Communication with the RDP engine stays within the server.
-
No secret in logs.
Logs mask sensitive data, including passwords, authenticator secrets and temporary credentials.
Control over every connection
Applications and their settings are defined on the server. Each person can access only the resources assigned to their account through the browser.
Changing a password requires the current password. An administrator can remove two-step verification in the console, with the action recorded in the audit trail.
The RDP engine accepts connections only from the server itself. Portal access uses HTTPS and retains RDP authentication mechanisms, including NLA/CredSSP.
Authentication and second factor
The credential is presented to Windows itself and validated by it. The product keeps no parallel user base, does not query the directory and stores no password.
- Two-step verification with an authenticator app (TOTP, RFC 6238), with three policies chosen in the console: Disabled, Optional and Required.
- Enrollment is done by the person, because the secret must reach their app without passing through anyone else.
- The secret is only saved after the first code is confirmed — a bad camera read does not lock the account.
- The secret is protected at rest by the same mechanism that protects the portal certificate.
- Attempts are rate-limited per account, on top of the per-origin limit: someone who already has the password cannot spread code guesses across many origins.
- Removing an enrollment exists only in the console, and it is recorded. Changing the policy does not erase enrollments.
Two-step verification protects every access made through the web portal. To close the alternative path, keep port 3389 closed to the internet — Atrio Remote makes that opening unnecessary.
Password protection during access
Credentials remain only in memory during the portal session, so users can open resources without entering their password again. They are not saved in databases, files or logs.
Sessions have adjustable limits: by default, 30 minutes of inactivity and a maximum duration of 12 hours. An open RDP connection keeps the session active within the maximum duration. Signing out or restarting the service ends the session and removes the credential from memory.
Administration separate from the portal
The administration console runs on the server and uses a protected local channel to communicate with the service. Administrative settings stay separate from users’ browser access.
The service brings together the HTTPS portal, authentication, permissions and auditing. Configuration is stored in a local database, with no additional database server to install.
The Print Client uses an outbound connection over the portal’s HTTPS port. Users authorize printer access on their own computers.
File transfers under your control
Your team decides whether users can upload or download files and chooses the destination: a temporary product folder or the user’s own folder.
Windows permissions keep each user’s files separate. The temporary folder is cleared when the session ends; files in the user’s folder are retained. Per-file and per-session limits help manage storage use.
What is recorded
- An audit trail of every administrative change, with who asked and the outcome — refusals included.
- Sessions opened and ended, and who ended what.
- An operational log in the Windows Event Log, where the tools you already use can read it.
- Never recorded: passwords, second-factor secrets and single-use credentials — neither whole nor truncated.
Installer integrity and component licenses
Each installer has a SHA-256 checksum so you can verify the file you receive. The checksums are listed on the download page.
The product includes third-party component licenses, copyright notices and applicable source code offers. This documentation is available for your IT and procurement teams to review.
Have a security questionnaire?
Talk to the Atrio Remote team. Security questions are answered in writing.