Password rotation support is only available for shared elevated access accounts that are tied to Active Directory (On-Premise or Azure).

Why is password rotation important?

For shared accounts if an employee were to leave the organization, they can take the knowledge of that password with them. This alone is why it is important to rotate passwords.

It is also good practice to rotate your passwords to remain secure.

How often should passwords be rotated?

The frequency to which the passwords should rotate is completely up to you. It can be as frequently as every 1-hour, to as much as every 30-days.

Why automate password rotations?

Automating password rotation, allows your technicians to focus on what is important – your customers.

Plus, if they’re busy on an urgent matter with a customer, there could be a delay in the passwords being rotated, or forgotten all together, as the day got away from them.

Password best practices

Best practices for passwords have changed over the years. Here are a few DOs and DON’Ts to keep in mind for passwords:

• DO rotate shared account passwords on a regular cadence.
• DO enforce MFA (multi-factor authentication), to add another layer of protection.
• DO set a password length of 12-characters or greater. Remember the longer the password, the harder it can be to crack.
• DO make passwords hard to guess.
• DON’T configure account passwords to never expire.
• DON’T enforce regular users to change their passwords. Reasoning, most will increment the password (e.g.: Password!123 > Password!1234), which weakens the password.
• DON’T reuse passwords across systems or services. Although it might be easy to remember, passwords should always be unique.
• DON’T use a single word for a password.
• DON’T use personal information in the password.
• DON’T keep your password on a sticky note for all to see.