MinValidity breaks PSM session

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

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

MinValidity breaks PSM session

L4 Transporter

Hi Community,

we have the following setup:

  • Exclusive usage
  • One-Time password without manual change <<< despite the name it is only to set the account automatically free
  • MinValidity = 60 mins
  • Account won't be set free if PSM session closes

Users told me, that after 60 mins of session start (=checkout) the session is closed and the accounts are set free.

 

Is there a way to make a more usable setup and set an account only free if there are no sessions open?

Best would be, if CPM takes action only if the account is still locked, although since 60 mins there were no Retrieve or PSM Session Closed events.

19 REPLIES 19

L5 Sessionator

Have you created PSM API Key and pointed to vault.ini file inside the PSM? If not, then you should focus on that too which helps to unlock the user accounts from PVWA once session is not in progress

Hi, this is not about PSM not releasing the account, but about achieving a setup, where CPM MinValidity does not ignore the fact, that there is still an ongoing session, so do not disturb the user during work.

It means I am quite perplexed. Could you please elaborate little more so that I can understand better and other also can jump in to put some ideas together?

Now:

  • Click on Connect = Account is locked
  • After 60 mins: Session gets disconnected automatically, CPM rotates password, Accounts gets released
    • User is unhappy as he was still working

Target:

  • Click on Connect = Account is locked
  • User is working... after 110 mins closes the session
  • User forgets to release account
  • CPM waits 60 mins after PSM Disconnect and rotates/releases the account
    • Alternative: CPM checks after 60 mins if account is still used, if not anymore, release/rotate account

L4 Transporter

Hi @Balazs Racz​ 

 

Have you received an answer to your question yet?

 

In the meantime, I have forwarded your inquiry to our PAM Self-Hosted Resource Center to gather input from our PAM Self-Hosted Experts.

You can track the progress here: 

https://community.cyberark.com/s/feed/0D5Ht0000ATyC1wKQF

 

Thank you,Liad

L4 Transporter

@Balazs Racz​ - It seems like this is a known issue. Smart customers and partners seem to bring this up every year, but honestly I'm not sure if there's a specific ER that addresses this and is seriously being considered by PM.

 

As you know, enforcing Exclusive Access and OneTimePassword on Platforms is highly recommended to ensure that only one person can use an account object at a specific time. Things like MinValidityPeriod, in theory, help automatically release/change the password and unlock that account for someone else to use. But as you point out, because any PSM sessions can remain active even after that CPM Release & Change actions occur, that leaves the chance that multiple users have access to the account (through PSM!) concurrently.

 

I would love to see PM address this and ensure that PSM sessions are terminated when a CPM Release/Change occurs. Perhaps they could get a warning button in advance of that happening, and optionally click a button to extend the MinValidityPeriod and keep their session active. @Gilad Artzi​ perhaps you could share if this has been discussed/if you're aware of a related ER we could upvote?

L4 Transporter

@Balazs Racz​ - It seems like this is a known issue. Smart customers and partners seem to bring this up every year, but honestly I'm not sure if there's a specific ER that addresses this and is seriously being considered by PM.

 

As you know, enforcing Exclusive Access and OneTimePassword on Platforms is highly recommended to ensure that only one person can use an account object at a specific time. Things like MinValidityPeriod, in theory, help automatically release/change the password and unlock that account for someone else to use. But as you point out, because any PSM sessions can remain active even after that CPM Release & Change actions occur, that leaves the chance that multiple users have access to the account (through PSM!) concurrently.

 

I would love to see PM address this and ensure that PSM sessions are terminated when a CPM Release/Change occurs. Perhaps they could get a warning button in advance of that happening, and optionally click a button to extend the MinValidityPeriod and keep their session active. @Gilad Artzi​ perhaps you could share if this has been discussed/if you're aware of a related ER we could upvote?

Hi LiadD,

Thank you, no usable response received.

Hi Nathaniel,

I also brought this up years ago already directly to our CyberArk contacts, though PM seems not to be interested.

I've found several other features with (from my PoV) design bugs, but it was told, that they are "working as designed", so no issue there 😅 😑

L4 Transporter

I believe 'ExclusiveUnlockAfterPSMSession' was created to help resolve this issue although as it is an API it does not blend well with accounts that are set with OT and EXCL. The other limitation is that if a user has more than one session up with the same account, when the first session is closed it will initiate a password change even though the additional sessions are still active

Similar experiences here... I'd keep raising those concerns/calling them out as bugs as much as you can. If you firmly believe they are bugs/things that are not working correctly, keep calling it that and pushing CyberArk to fix them. Coordinate/request regular meetings with PM to share those concerns. I'm not saying these things have worked for me entirely, but I do have generally positive interactions with PM and other leaders across CyberArk - communication is the first step. 🙂

Similar experiences here... I'd keep raising those concerns/calling them out as bugs as much as you can. If you firmly believe they are bugs/things that are not working correctly, keep calling it that and pushing CyberArk to fix them. Coordinate/request regular meetings with PM to share those concerns. I'm not saying these things have worked for me entirely, but I do have generally positive interactions with PM and other leaders across CyberArk - communication is the first step. 🙂

As you found, ExclusiveUnlockAfterPSMSession is "buggy" at best and actually causes the opposite effect you have OneTimePassword & Exclusive Access enabled -- it can preemptively unlock an account to allow other users to retrieve/use the EXACT SAME password as the first user had. For example:

 

  1. User 1 retrieves (show/copy) password for account A [locking account A to user 1]
  2. User 1 starts PSM session 1 for account A
  3. User 1 starts PSM session 2 for account A
  4. User 1 disconnects PSM session 1 for account A
  5. PSM unlocks account A
  6. User 2 retrieves (show/copy) password for account A [locking account A to user 2]

 

User 1 & 2 now both have the exact same password for account A, and both have active PSM sessions to it.

 

I can't imagine ever enabling this ExclusiveUnlockAfterPSMSession for anything and would never recommend any other customers do that either.

 

Really, really dangerous design implications.

As you found, ExclusiveUnlockAfterPSMSession is "buggy" at best and actually causes the opposite effect you have OneTimePassword & Exclusive Access enabled -- it can preemptively unlock an account to allow other users to retrieve/use the EXACT SAME password as the first user had. For example:

 

  1. User 1 retrieves (show/copy) password for account A [locking account A to user 1]
  2. User 1 starts PSM session 1 for account A
  3. User 1 starts PSM session 2 for account A
  4. User 1 disconnects PSM session 1 for account A
  5. PSM unlocks account A
  6. User 2 retrieves (show/copy) password for account A [locking account A to user 2]

 

User 1 & 2 now both have the exact same password for account A, and both have active PSM sessions to it.

 

I can't imagine ever enabling this ExclusiveUnlockAfterPSMSession for anything and would never recommend any other customers do that either.

 

Really, really dangerous design implications.

  • 558 Views
  • 19 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!