Devolutions Server staging checklist

Before deploying a Devolutions Server instance to production, it is recommended to run a few tests to make sure that essential configurations are working properly.

We've compiled this checklist to ensure you don't miss anything:

• Vaults root folders are correctly configured.
• Logs are functional.
• The system dashboard shows a high security score and the services are up and running.
• Permissions at vault, folder, and/or entry levels are customized and assigned to users and/or user groups.
• Product licenses have been added and assigned to the right users.
• Cache/offline mode is enabled.
• System settings fits your needs, e.g., to determine if users can access user vaults.
• Advanced connection settings are verified.
• Authentication methods have been enabled.
• Service accounts used by Devolutions Server are validated.
• The SSL/TLS certificate is valid and trusted.
• An automatic user creation policy is defined.
• Vaults are accessible through the web interface.
• Notification policies are defined for specific users and user groups.

Optional verifications based on configuration

Devolutions Gateway

• Devolutions Gateway is properly installed and configured.
• RDP and SSH session can be launched through the web.
• Session recording and monitoring are functional.

PAM module

Make sure the PAM accounts and providers used in staging are not the same as the ones used in production.

• The PAM module is configured correctly.
• Permissions are assigned to users and user groups for PAM entries.
• Password resets are working.
• The checkout request and check-out/check-in processes are operational.
• Conditional access policies have been defined.
• GeoIP security is enabled.
• Email integration is completed.
• IP and auto-lock settings are configured.
• The documentation feature for entries works.
• The entry and password templates function as intended.
• Files can be attached to entries.
• The backup configuration is valid.
• Clean up logs allows archiving and deleting logs properly.
• Notification preferences have been defined.
• Applications identities can be created and modified. Applications can communicate with Devolutions Server seamlessly.