PAM360 offers comprehensive SSH key management for securely handling key associations, rotations, and deployments across various user accounts and resources. Key features include associating SSH keys with individual accounts or resources, automating key rotation on a schedule, dissociating keys to revoke access, and pushing key files to remote users. PAM360 also provides bulk key management with key groups, allows customization of user home directories for key deployment, and supports key file export and audit history tracking for thorough oversight and compliance.
This document traverse you through the SSH keys management operations performed from the PAM360 interface.
Upon importing or creating the SSH keys, you can associate the keys with SSH users.
Caution
If a root user or administrator credential has been provided for a resource, keys can be associated with all enumerated user accounts of the resource. If there are no keys available in the PAM360 database, then you will be prompted to create a key during association. Create a key pair and return to these steps.

Caution
For security reasons, root user login might be disabled for servers/machines. Enabling this option elevates a user login from a non-root user to a root user and allows you to associate keys with all other users on the server. Users have to provide root user and any non-root user credentials to PAM360 to elevate to a root user.

Now you have successfully associated a particular SSH key to the resources/user accounts.
You can configure PAM360 to rotate the SSH keys at periodic intervals automatically. With a single click, all the deployed keys can be replaced. The keys can be rotated based on a schedule or anytime based on your need.
To schedule the rotation of keys, follow the below steps:
A confirmation message will be displayed, and you will be redirected to the Key Rotation Audit page, where the status of rotation is updated.
Caution
Only the keys which have already been associated with user accounts of resources can be rotated.
To schedule the rotation of keys, follow the below steps:
The result of the scheduled execution will get updated in the Key Audit, and the results of the rotation of the keys will get updated in the Key Rotation Audit.
When an SSH user leaves the organization or is provided temporary privileged access, you can dissociate the keys associated with the user account and discontinue access. Until you dissociate all the SSH keys, you cannot delete the user account or the resource.
To dissociate key from the user accounts, follow the below steps:
To dissociate key from a selected user account, follow the below steps:
Additional Details
When you select and delete the user accounts enumerated in PAM360, the SSH keys associated with them are automatically dissociated.
In addition to deployment, PAM360 allows you to push a private key or a public key, or both onto its associated user accounts.
i. To push a key file to remote user accounts:

This feature is also available as a part of the Key Rotation schedule. After the scheduled key rotation is performed and fresh key pairs are created and deployed, you can automatically push either the private key or both the private and public keys onto its selected associated users by enabling the 'push key to user' option instead of pushing the key files manually after every scheduled rotation.
ii. Add commands and restrict host per key:
You can add commands to specific user accounts, thereby providing an additional layer of restriction enabling them only to execute the commands on establishing a connection with the host. Also, you can predefine the appropriate key-to-user relationship by specifying the IP address of the user in the appropriate format (as specified below).
To add a command to a public key,
To restrict hosts for a key, click on Add Command and provide the name or IP address of the hosts in the following format. i.e.,(from="host1/ip1,host2/ip2")
You can fetch authorized key files from various user accounts, edit the key content and push them to respective user accounts from PAM360. To do this,

When you try to delete the SSH keys from the PAM360 repository, they are first dissociated automatically from their user accounts. Key deletion fails for the SSH keys that are not dissociated from all their user accounts. To delete the SSH Keys:
PAM360 gives the provision to create key groups for easy organization and to carry out operations in bulk. You can assign, delete, or modify the group similar to working with a single SSH key. The list of items available in a group is enumerated in their respective tabs. You can drill down to the individual items by clicking the name of a group.
To create a group of SSH keys, follow these steps:
Additional Details
If you select the By Criteria option, the conditions specified are applicable to keys that are discovered later too. If any of those keys match the criteria, they will be automatically included in the new group.
In addition, you can directly select individual keys from the SSH Keys >> SSH Keys tab and click the Save button for faster group creation.
To make changes to an existing key group, follow these steps:
Once you make changes to the group and save, a message will be displayed confirming the update of the changes.
Caution
The name of the group cannot be modified. However, you can add or modify the description and the list of keys available in it.
To rotate all the keys of a key group, navigate to SSH Keys >> Keys Group, select the key groups and click the Rotate button. You will be now redirected to the Key Rotation Audit window, where the status of key rotation is updated.
To delete a key group, navigate to SSH Keys >> Keys Group, select the key groups and click the Delete button. A pop-up window will appear to make sure that the selected groups are to be deleted. Click OK to delete the groups.
You can customize the home directories of the users, i.e., the location where the public key is to be deployed. To do this:
To export key files by selecting them from the resources with which they are associated:
To export the key files, navigate to the SSH Keys >> SSH Keys tab and click the Export Keys icon available in the right corner of the table view corresponding to the required key.
Additional Details
Even while exporting, the passphrases used to protect the keys are still in effect. That is, if the keys are to be used elsewhere, the passphrases have to be provided.
Using PAM360, you can view the history of each SSH key, from the moment it was created or imported, and the subsequent rotations along with time stamps. To view the history of any key, navigate to the SSH Keys >> SSH Keys tab, select a single key and click the Key History button.
A report of the discovered keys can be exported as PDF or to an email id. To export the report: