Before managing your critical resources and privileged accounts, it is essential to properly set up your PAM360 account. The setup process involves several key steps: configuring the mail server, upgrading your account with the procured license key, managing the encryption key, onboarding users, and enhancing security with two-factor authentication. Let's explore each of these steps in detail to ensure your PAM360 account is configured correctly and securely.
The crucial step before configuring the PAM360 application is to update the license key in your PAM360 account. This step unlocks the complete functionality of the software. Store the purchased license file locally on your computer for easy access before beginning this process.

PAM360 employs AES-256 encryption to secure passwords and other sensitive information in its password database. The encryption key used is auto-generated and unique for each installation. By default, this key is stored in a file named pam360_key.key within the <PAM360 Installation Directory>/conf folder of the installation directory. However, for production instances, PAM360 mandates that the encryption key not be stored within its installation folder to prevent the encryption key and the encrypted data in both live and backed-up databases from residing together.
We strongly recommend relocating this encryption key to an external location outside the machine where PAM360 is installed, such as another machine or an external drive. You can specify the full path of the folder where you wish to move the pam360_key.key file, manually transfer the file to that location and remove any references within the PAM360 server installation folder. The path can be a mapped network drive or an external USB (hard drive/thumb drive) device.
PAM360 will record the location of the pam360_key.key in a configuration file named manage_key.conf, located in the <PAM360 Installation Directory>/conf folder. You can also directly edit this file to change the key file location. After configuring the folder location, move the pam360_key.key file there and ensure the file or the key value is not stored anywhere within the PAM360 installation folder.
PAM360 requires the conf path to be accessible with the necessary permissions to read the pam360_key.key file during startup. Once the startup is complete, access to the file is no longer needed, and the device containing the file can be taken offline.
Caution
From PAM360 build 8000 onwards, it is mandatory to retain the pam360_key.key file in the file path specified in the manage_key.conf file for a seamless operation. PAM360 continuously accesses this file to ensure uninterrupted operation. If the pam360_key.key file is not available in the specified path, the service may not startup or certain features such as database backup will not function.
Best Practices
The PAM360 encryption key plays a critical role in protecting the privileged credentials and other sensitive information stored in the database. Over time, prolonged use of the same encryption key increases the risk of compromise. To minimize this risk, organizations are required to rotate the encryption key periodically, in accordance with established security best practices and relevant regulatory requirements. PAM360 offers a secure and streamlined mechanism to rotate the encryption key without impacting data integrity.
Once the key rotation process is initiated, PAM360 first identifies the existing encryption key in the pam360_key.key file, located in the path specified in the manage_key.conf file. The key rotation process continues only if the existing key file is present in the location specified. PAM360 creates a database backup before rotating the encryption key to prevent any data loss in the event of unexpected failures.
During the key rotation process, all stored passwords and sensitive data are decrypted using the existing key and then re-encrypted using the newly generated encryption key. The new encryption key is written to the 'pam360_key.key' file located within the specified location. If an error occurs while generating or writing the new encryption key, the key rotation process is aborted to maintain data integrity.
Caution
Before proceeding with the encryption key rotation, ensure the following:
Follow these steps to rotate the PAM360 encryption key:
Windows:
RotateKey.bat
Linux:
sh RotateKey.sh
Follow these steps to rotate the PAM360 encryption key in environments configured with the high-availability setup:
Windows:
RotateKey.bat
Linux:
sh RotateKey.sh
Follow these steps to rotate the PAM360 encryption key in environments configured with the application scaling setup:
Windows:
RotateKey.bat
Linux:
sh RotateKey.sh
Additional Detail
In PAM360 builds before 8000, the duration of the encryption key rotation process may vary depending on the number of managed passwords and other system parameters. The process typically takes a few minutes to complete. A confirmation message is displayed once the key rotation is complete.
To update the PAM360 web server certificate from the web console, follow these steps:

Setting up the Simple Mail Transfer Protocol (SMTP) server is essential for delivering important messages to users. PAM360 uses email to notify users about their account details, such as username, password, and the URL to access the PAM360 application. Therefore, it is crucial to configure the SMTP server before onboarding users. PAM360 offers the following options:
Caution
If you choose Microsoft Exchange Online as the mail server, OAuth 2.0 authentication is required for all email communications sent from the product.
Refer to the Mail Server Settings documentation to know more about the configuration and setup.
Best Practice
Ensure you change the password of the default admin user or delete the account after adding another administrator user.
Onboarding users is a crucial step in setting up your PAM360 account. PAM360 allows you to onboard users manually or import them from various sources such as a file, Active Directory, Microsoft Entra ID, or LDAP. Detailed instructions for each method can be found through the provided links. Using the administrator account, you can add or import users and assign them roles based on their required permissions. PAM360 offers six predefined user roles but also provides the flexibility to create custom user roles. These custom roles enable you to modify access and permissions according to your organizational needs.
Additionally, PAM360 allows you to organize users into groups based on factors like designation, department, or location, facilitating efficient user management and simplifying permission assignments.
Furthermore, PAM360 supports the creation of API user accounts necessary for application-to-application password management. Users with administrator privileges can add API users. For detailed steps on adding an API user, click here.
Two-Factor Authentication (TFA) is a security mechanism that requires users to provide a secondary authentication factor to access their PAM360 account. Enabling TFA enhances account security by adding an extra layer of protection. Once TFA is enabled, users must authenticate using the selected TFA mechanism after logging in with their username and password. Administrator accounts have the ability to set up and disable TFA.
PAM360 supports various TFA mechanisms, including OTP via email, Google Authenticator, and Duo Security. Administrators can choose any of the supported mechanisms and configure them accordingly. Refer to this document for detailed steps on setting up two-factor authentication.
The first step in password management with PAM360 is adding your resources to the PAM360 database. Resources refer to the servers, applications, or devices whose user accounts and passwords will be managed by PAM360.
Resources can be added manually or imported from a file along with their user account and password information. Depending on your needs, you can set up the password reset method to be either remote or agent-based. For ease of management, resources can be grouped together to perform bulk operations. Additionally, you can create nested resource groups, maintaining a hierarchical structure for navigational convenience.
By default, only the user who added the passwords can view and edit them. However, you can share resource passwords with other PAM360 users or user groups as needed. This allows users to access and modify passwords that are owned by them or shared with them.
After adding resources, administrators can implement an access control workflow for enhanced security. Upon successful authentication into PAM360, users gain access to passwords owned by them or shared with them. In some cases, administrators might want to grant temporary access to passwords for specific users for a limited time.
Set up the access control workflow according to your organization’s requirements.
However, if you are a user responsible for viewing assigned passwords, no additional configuration is needed. You can directly view and edit the passwords of the resources or accounts if you have the necessary permissions.
To set up disaster recovery, follow these steps: