This document describes the best practices in setting up and using Password Manager Pro in an enterprise network environment. It is intended to offer guidance to IT administrators when they set up the software for use in their production environment. Best practices during all stages - product installation, configuration, setup and deployment have been explained with special focus on data security. In addition, the best password management practices in general have also been explained wherever required.
Before installing PMP, you need to decide on the configuration of the system where you would install PMP. The following table provides information on the minimum hardware and software configuration required by PMP.
|Hardware||Operating Systems||Web Interface|
|| HTML client requires one of the following browsers** to be installed in the system:
Recommended Configuration for Better Performance, Scalability & Security
For better performance and security, it is recommended to install PMP in a dedicated, hardened, high-end server. Also, the performance of PMP depends a lot on the following factors:
Though PMP will very well run in the systems having the minimum configuration, you may have to choose a higher configuration if the above factors weigh high at your end. We can roughly say that if the above factors are very high of the order of hundreds of users and user groups with a few thousands of resources and resource groups and shares, you may choose a high-end configuration as below:
Installing PMP in Windows Vs Linux
PMP can be installed in Windows and Linux. Though PMP will run equally fine in both the platforms, installation in Windows has some inherent advantages.
Using MS SQL Server as Backend Database
Secure the Installation Master Key
PMP uses AES-256 encryption to secure the passwords and other sensitive information in the password database. The key used for encryption is auto-generated and is unique for every installation. By default, this encryption key is stored in a file named pmp_key.key under <PMP_HOME>/conf folder. For production instances, PMP does not allow the encryption key to be stored within its installation folder. This is done to ensure that the encryption key and the encrypted data, in both live and backed-up database, do not reside together.
We strongly recommend that you move and store this encryption key outside of the machine in which PMP is installed - in another machine or an external drive. You can supply the full path of the folder where you want to move the pmp_key.key file and manually move the file to that location and delete any reference within PMP server installation folder. The path can be a mapped network drive or external USB (hard drive / thumb drive) device.
PMP will store the location of the pmp_key.key in a configuration file named manage_key.conf present under <PMP_HOME>/conf folder. You can also edit that file directly to change the key file location. After configuring the folder location, move the pmp_key.key file to that location and ensure the file or the key value is not stored anywhere within the PMP installation folder. PMP requires the pmp_key.key folder accessible with necessary permissions to read the pmp_key.key file when it starts up every time. After a successful start-up, it does not need access to the file anymore and so the device with the file can be taken offline.
Important Note: You need to take care of sufficiently protecting the key with layers of encryption (like using Windows File Encryption for example) and access control. Only the PMP application needs access to this key, so make sure no other software, script or person has access to this key under any circumstance. You also need to take care of securely backing up the pmp_key.key file yourself. You can recover from PMP backups only if you supply this key. If you misplace the key or lose it, PMP will not start.
Take Control of Database Key
Apart from the AES encryption, the PMP database is secured through a separate key, which is auto - generated and unique for every installation. The key for the database can be stored securely in the PMP itself. There is also option to store it at some other secure location accessible to the PMP server.
It is better to store the database key outside PMP. For more details, refer to the following section of our help documentation.
Integration with Directory Services/Identity Stores
Password Manager Pro can be integrated with third party identity stores such as Active Directory / LDAP. If you have AD or LDAP in place, it is recommended to integrate them with PMP. You can import users from AD / LDAP and also leverage their authentication mechanism. Users get the advantage of logging into PMP using the AD / Credentials. Additionally, PMP user database can be synchronized with AD / LDAP database at specified, periodic intervals.
Use Local PMP Accounts for ‘Fire-Call’ Purposes Only
By default, PMP allows local authentication along with AD or LDAP authentication. The best practice approach is to use local PMP account only for 'fire call' purposes and all other user accounts should be from a directory service to leverage good user management practices.
Decide about Email notification on user creation
By default, whenever a new user account is added in PMP, an email is triggered to the respective user with information about the login password in the case of new user addition. When you integrate AD/LDAP, decide beforehand if you wish PMP to send email notification. Particularly, when you are evaluating the product, it is recommended that you disable email notification. It can be done from General Settings option.
Create User Groups
Organize the PMP users into groups - for example, Windows Administrators, Linux Administrators and so on. The grouping of users will immensely help in sharing resources. In case, you have integrated AD/LDAP, you can automatically have the same hierarchical structure in PMP just as in AD/LDAP, including the user groups.
Assign User Roles Properly
After adding users, assign proper roles to them - Administrator, Password Administrator, Password Auditor or Password User. Also, decide if your organization requires any administrator or password administrator to act as a 'Super Administrator', who will have the privilege to view all the passwords in the system.
Use Two Factor Authentication
To access the PMP web-interface, there is provision to enforce users to authenticate through two successive stages. While the first authentication is through the usual native authentication or AD / LDAP, the second level of authentication could be either through a one-time, randomly generated unique password sent by PMP to the user by Email or by leveraging RSA SecurID authentication as the second level of authentication. From security standpoint, it is recommended to make use of the Two Factor Authentication.
Remove the Default 'admin' Account
For security reasons, it is highly recommended that the default 'admin' account of PMP be removed once you add another user with 'administrator' role.
Prepare Inventory of Administrative Accounts
The first step prior to actual Password Management using Password Manager Pro is identifying all the administrative accounts in your organization. This can be done by first preparing the inventory of all servers, databases, network devices and other sensitive applications. If you are using other ManageEngine products such as Asset Explorer, OpManager, DeviceExpert etc, you can easily build an inventory of your resources. You can export the inventory as a CSV and then import them in PMP.
In addition, each resource might contain more than one administrative account. You need to identify all such accounts. These are the accounts that are to be managed by PMP.
Leverage the Power of Resource Groups
After adding resources, organize your resources into resource groups. Resource Groups are quite powerful in PMP. Most of the enterprise-class password management operations in PMP can be performed only at resource group level. Among the two types of resource group creation, "Criteria-based" resource groups are highly recommended.
Criteria-based groups act as dynamic groups providing the flexibility to automatically make a resource, which satisfies certain criteria to become part of specific groups, without any manual intervention. For example, if you create a criteria-based resource group based on the condition "Resource Type Contains Windows", all Windows resources could be made part of the Windows group automatically after resource addition.
Apart from the dynamic nature, the criteria-based resource groups allow you to create resource groups matching any required criteria - like department, location, type, name and even based on custom criteria. You can make use of a combination of criteria too. For example, you can create a group of resources belonging to type 'Linux' and location 'Second Floor' of the building.
Moreover, if you have thousands of resources in your environment, picking resources individually to make them a resource group, would be a laborious task. So, making use of the criteria-based resource group is the best practice approach.
'Resource Group - User Group' Sharing: The Best Approach
Though PMP has provision for sharing a single password or a single resource, the best practice approach here is sharing a resource group with a user group. This will come in handy when performing several bulk operations. For instance, assume there is a user group named "Windows Administrators" and there is a resource group named "Windows Servers" and all Windows Administrators should have access to all the Windows Resources.
In this case, the best practice approach is:
Another example to bring out the benefit of Resource Group – User Group Sharing:
Consider that you have integrated Active Directory and you want to manage the passwords of the Windows resources belonging to a certain OU. Also, assume that you have an IT administrator group, which is also part of that OU. In this case, you can import the resources from the domain and create a criteria-based resource group.
Similarly, you may import the users from the domain belonging to the OU and create that as a user group. In both the cases above, you can specify certain synchronization interval to keep the resources / users in PMP in sync with the ones in the Active Directory. You can then share the resource group with the user group. Once you do this, if any new resource/user is added to the OU, they will be automatically imported to PMP with the same share permissions.
Additional Fields for Easy Reference & Search
Make use of the "Additional Field" creation feature to create customized columns at resource and accounts view. The additional fields will come in handy in creating criteria-based groups, searching specific resources or passwords and in sharing the resources etc.
Assume the scenario that you have three levels of IT administrators in your organization. While creating resources, if you have an additional field specifying the level to which that particular resource belongs, it will be very convenient to share those resources to the respective level of users.
That is, you will have an additional field titled "Access Level" for resources. Each resource will then have a level associated - Level I / Level II / Level III. You can then create a criteria-based resource group based on the level. Similarly, you can create three levels of user groups - all users belonging to Level I as a group and so on. You can then assign 'Level I' resources to 'Level I' users.
Make Use of Access Control Workflow
If you have stored certain sensitive passwords, it is strongly recommended to enable 'Access Control Workflow' for that particular resource. When access control is enabled, users will have to go through a request-release flow for password access. It also helps in granting time-limited, exclusive privilege to passwords to select users.
Force Users to Provide Reason while Retrieving the Passwords
By default, when a user tries to retrieve the password of a resource, on clicking the asterisks, the passwords appear in plain text. It is better to force the users to provide a reason why access to the password is needed. You can achieve this through an option in General Settings.
Agentless Mode for Password Reset
One of the basic doubts that arise in the minds of PMP users is whether to use agentless mode or agent mode for password reset. Before recommending an option, let us first look at the requisites for both the modes:
The agent mode requires the agent to be installed as a service and run with administrative privileges to perform password changes. The agent could be used in target machines, which will communicate with the PMP server and effect password changes. All password related communication is over HTTPS and is secure. The communication is always one way - that is, the agent alone will contact the server. The PMP server will not communicate with the agent. So, there is no need to keep any port open in the host where the agent has been installed.
For the agentless mode, you must supply administrative credentials to perform the password changes. For Linux you must specify two accounts, one with root privileges and one with normal user privileges that can be used to login from remote. Telnet or SSH service must be running on the resources. For Windows domain, you must supply the domain administrator credentials. For Windows and Windows domain, PMP uses remote calls and relevant ports must be open on the resource.
Based on this you can choose which mode you want for your environment, indicated by the following tips:
Choose agent mode when,
Choose agentless mode in all other cases as it is a more convenient and reliable way of doing password changes.
Do Not Perform Password Resets Across Untrusted Domains
By design, PMP is capable of resetting even foreign domain passwords without a trust. It is strictly NOT recommended to perform password resets across untrusted domains, as the setup could be exploited for malpractices.
Keep Tab on Activities Using Password Action Notification
PMP offers provision to send email notifications upon certain password events like a password access or modification or changing the share permission or when the password expires or when password policy is violated. Enabling 'Password Action Notification' helps achieve this.
Randomize Passwords Periodically
Foremost among the 'Password Management Best Practices' is to periodically reset the administrative passwords. PMP provides option to automatically reset the passwords at pre-determined intervals. Making use of the 'Scheduled Password Reset' feature you can achieve this.
Passwords and other sensitive information are stored in encrypted form in the database. If you are using MySQL as the backend database, you can carry out the following MySQL tuning procedure to enhance the performance of PMP.
@start "MySQL" /B "%DB_HOME%\bin\mysqld-nt" --no-defaults --standalone --default-character-set=utf8 --basedir="%DB_HOME%" --port=%DB_PORT% --datadir="%DB_HOME%\data" --tmpdir="%DB_HOME%\tmp" --user=root --server- id=%TSTAMP1% --log-bin=mysql-bin --log-slave-updates --master-connect-retry=30 --slave-net-timeout=30 --expire_logs_days=7 --log-slave-updates --log-slave-updates --max_allowed_packet=32000000000 --max_binlog_cache_size=4294967295 --binlog-do-db=passtrix --binlog_cache_size=32768 --max_binlog_size=52428800 --max_relay_log_size=0 --relay_log_purge=1 --ssl-ca=..\conf\CAcert.pem --ssl-cert=..\conf\ServerCer.cer --ssl-key=..\conf\ServerKey.key
$DB_HOME/bin/mysqld --no-defaults --default-character-set=utf8 --basedir=$DB_HOME --tmpdir=$TMP_HOME --port=$DB_PORT --socket=$TMP_HOME/mysql.sock --user=root --server-id=$ID --log-bin=mysql-bin --log-slave-updates --master-connect-retry=30 --slave-net-timeout=30 --expire_logs_days=7 --log-slave-updates --log-slave-updates -- max_allowed_packet=32000000000 --max_binlog_cache_size=4294967295 --binlog-do-db=PassTrix --binlog_cache_size=32768 --max_binlog_size=52428800 --max_relay_log_size=0 --relay_log_purge=1 --ssl-ca=$PWD/../conf/CAcert.pem --ssl-cert=$PWD/../conf/ServerCer.cer --ssl-key=$PWD/../conf/ServerKey.key --log=mysql.log 2>>$TMP_HOME/mysql.out 1>>$TMP_HOME/mysql.out
Two parameters - key buffer size and innodb buffer pool size are to be tuned to make sure it makes the most of the dedicated RAM.
If the parameters are already present in the above line, just change the values as shown below. If they are not present, just add the parameters after the entry max_binlog_cache_size entry
For 1 GB RAM, you can try values
For 3 GB RAM, you can try values
Purge Audit Records
All operations performed in PMP are comprehensively audited and the trails are stored in the database. Naturally, the audit records grow at a faster rate. If you do not need the audit records that are older than a specified number of days, you can purge them. However, if regulatory compliance requirements demand retention of the audit records for longer period of time, you may have to retain the trails.
Configure Email Templates
Password Manager Pro facilitates sending email notifications on the occurrence of various password actions. By default, PMP has a specific content for the email notification. It is recommended that you configure the template to suit your needs and have your own content.
Setup Disaster Recovery
Data stored in PMP database are of critical importance. In the unlikely event of something going wrong with the production setup, all passwords would be lost. Disaster recovery provision is highly essential. PMP provides two options - live backup and scheduled backup. Choose any convenient method and backup your data. You can always rely on the backup data.
Moving PMP Installation from one Machine to Another
If you want to move the PMP installed in one machine to another, follow the procedure detailed below:
Do not remove existing installation of PMP until the new installation works fine. This is to ensure having a valid backup setup to overcome disasters/data corruption during the movement.
Always Choose SSL in all Communication
PMP offers both SSL mode and non-SSL mode for sensitive operations like password reset, resource addition/import etc. For obvious security advantages, it is recommended that you use SSL communication is used always.
Restrict plain-text password access for password users and auditors when auto logon is configured
Through the auto logon feature, PMP provides the option to establish direct connection to the resource eliminating the need for copy-paste of passwords. By default, password users and auditors will be able to retrieve the passwords that are shared with them. If auto logon is configured, they might not need access to the passwords. In such cases, it is recommended to restrict access to passwords through an option in General Settings.
Configure Inactivity Timeout
As PMP users are dealing with sensitive passwords, from the information security point of view, it would be hazardous to allow the web-interface session to remain alive if users leave their workstation unattended. Inactivity timeout could be configured by specifying the time limit in minutes through an option in General Settings.
Mask Passwords when Exporting Resources to CSV
When you export PMP resources to a CSV file, by default, password of the accounts are included in plain text. From security standpoint, it is better to mask the password in the report. You can achieve this through an option in General Settings.
Make Use of Auto-Reset Provisions
PMP provides options to carry out automatic password resets upon the completion of various activities such as changing password shares, password expiry, policy violation and when the password stored in PMP is not in sync with the one in the actual resource. From security standpoint, it is recommended that you make use of all the auto password reset options.
Audit Filters for Fine-Grained Tracking
PMP has provision for granular recording of audit events and also to send notifications on the occurrence of each event. From security standpoint, it is highly recommended that you register for specific events or to the daily notification digest to achieve granular tracking of events.
Carry Out User Deprovisioning Promptly
When an administrator leaves the organization, it is important that the passwords owned by the administrator are transferred to some other administrator. Otherwise, system lockout issues will occur. Also, it is quite possible that the administrator might have copied some / all the passwords. To rule out security breaches, it is recommended to reset all the passwords owned by the outgoing administrator before transferring the ownership.