Online Help > Overview



All passwords stored in the application data sources are encrypted using a strong encryption algorithm, to the extent that if a user attempts to access the data directly in the database, it will be considered unreadable.


If you choose to store passwords locally, Remote Desktop Manager will use the same mechanism used by mstsc.exe (Remote Desktop Manager client), which stores the passwords in the Windows Credential manager. It must be noted that the password will not be able to be viewed due to being encrypted by Windows. For obvious reasons, this choice also means that credentials stored in this fashion are not shared. Please refer to Windows Credential Manager for more information.


U.S. Federal Government Approved Encryption


Our application integrates an Advanced Encryption Standard (AES) algorithm to protect your local files and your sensitive data in the database. A mix of our own private key and a master password (passphrase) is used to create a strong encryption key (256-bit key).


This cipher is proven to be very secure. AES/Rijndael became effective as a U.S. Federal government standard and is approved by the National Security Agency (NSA) for top secret information.




Encryption of data while in transit is offered natively by our cloud services. Whenever you decide to use an on-premise solution, implementing encryption of data in transit must be implemented by using the tools involving your chosen technologies. Most customers that have security concerns already choose one of the supported Advanced Data Sources, follow instructions specific the chosen solution.

The encryption key is built-in the application and is therefore the same for all copies of the software in circulation. It is imperative that you follow our recommended steps and apply a Security Provider to encrypt not only the passwords, but also all of the connection data that is stored in the data source. This will give you protection over your data at rest, using a key under your exclusive control.


We recommend you follow these steps to ensure security:


Use an Advanced Data Source and grant user access by assigning permissions.

Use encrypted communication with the database when available.

Use the Data Source Settings to control many setting that have an impact on security.

Use the Security Provider to encrypt entries completely instead of just the password.

If using the offline mode, add your own password to add an additional layer of protection to the local cache.

Require a password to launch the application, and even better: require two factor authentication.

If your data source supports it, choose not to save password in the data source, which will prompt for the credentials on the first connection.

Use our policies to enforce some of these settings at the system level.