Best Practice for password rotation

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Best Practice for password rotation

L1 Bithead

Hi all,

We're about a year into our CyberArk journey and, overall, things are going really well.

I do have one challenge with some of our privileged users that I'd be interested in getting the community's thoughts on.

 

We manage privileged and Domain Admin accounts through CyberArk, with passwords rotated and verified daily. Passwords are rotated at 03:00 and verified at 06:00 so accounts are ready for

use during the next working day.

 

Our users access Windows hosts through a combination of Secure Infrastructure Access (SIA) and Privilege Cloud. From a connectivity and operational perspective, everything works well.

 

The issue we're seeing is user behaviour. Despite regular education and reminders, some users leave RDP sessions logged in or have disconnected SIA sessions that remain active on target systems. When CyberArk rotates the password, those sessions still hold the old credentials. The result is that when the stale credentials are subsequently used, Active Directory locks the account. We typically see this through the CyberArk rotation/verification notifications and corresponding AD lockout events.

 

We've explored several options, including:

  • Scheduled tasks on target servers to automatically log off privileged users.
  • Expanding the use of WinRM and automation to close sessions before password rotation.
  • Reviewing other technical controls that could help eliminate stale sessions before rotations occur.

So I'd be interested to hear how others are handling this.

 

How do you ensure, or enforce, that privileged users properly log off their sessions before password rotation takes place? Are you using technical controls to terminate sessions, adjusting rotation schedules, leveraging CyberArk-specific features, or taking a different approach altogether?

 

Any lessons learned or best practices would be greatly appreciated.

 

Thanks!

2 REPLIES 2

L2 Linker

I'd recommend looking into GPOs at the target servers. You can read about it here: https://community.cyberark.com/s/article/PSM-How-to-configure-Timeout-idle-and-Re-connection-Settings-for-Remote-Desktop-Services-and-PSM-Sessions

Specifically, you should be looking into "Set time limit for disconnected sessions" in Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Session Time Limits

L1 Bithead

I agree with Przemek_'s comment.

 

Forward-looking:

In addition, you can tweak the MinValidityPeriod at the platform layer. Tweak it in conjunction with the GPO's - could help tighten controls and minimize the issues you are seeing.

 

Keep in mind, in regards to MinValidityPeriod the following events start or extend (by default) the timer:

-Use Password

-Show Password

-Copy Password

 

Particular note: activities within a PSM session do not count towards resetting the MinValidityPeriod. Entering a new session will extend the timer.

 

With SIA, I imagine the same event triggers apply.

  • 37 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!