With OTP function, is it possible to rotate password on viewing or copying the password only but not after a regular 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

With OTP function, is it possible to rotate password on viewing or copying the password only but not after a regular PSM session?

I have OTP enabled for one of the onboarded account along with days defined in platform policy when password rotation should take place.

I have observed that CPM has now started to rotate password even when there is a regular PSM session from user. I assume OTP is unbale to identify when password is being retrieved by user via SHOW COPY and when the password is being retrieved by CyberArk solution itself for launching a regular PSM initiated session.

Is that regular by design behavior?

If so, is it possible to rotate password on viewing or copying the password only but not on regular PSM usage?

3 REPLIES 3

L7 Applicator

Hi @Himanshu Prahari​ 

 

Its by design to increase security by ensuring that a credential is automatically changed after it has been exposed for any purpose including by PSM session.

 

Here, an idea is that a credential once exposed 'show/copy' or via 'PSM session' should ideally be changed to prevent further, potentially from unauthorized use of that session / password. This protects against credential theft during a session or a user leaving a password visible.

 

Possible Workarounds:

 

Workaround 1:

 

  • You can disable OTP on the platform policy.
  • Configure auditing to specifically capture "Show Password" and "Copy Password" events.
  • Integrate with a SIEM to capture Syslogs.
  • When the SIEM detects a "Show/Copy" event for a specific account, it would then trigger a CPM "Change Now" action for that account via Rest API.

 

Please note, its a complex solution, requires custom development and it will introduces latency in the rotation dependsing on the reliability of the external system. It also means PSM sessions won't trigger immediate rotation unless you build separate API script.

 

Workaround 2:

 

  • You can increase the MinValidityPeriod and keep OTP enabled.
  • It means that passwords will rotate after that minimum period and the account is released, regardless of how it was used.

 

Hope it helps !

L4 Transporter

You can achive this without any issue by adding dual control.

Enable the one time password with Dual control in master policy for that platform

and set the parameter to No at platform level

DisableDualControlforPSMSession

L4 Transporter

You can achive this without any issue by adding dual control.

Enable the one time password with Dual control in master policy for that platform

and set the parameter to No at platform level

DisableDualControlforPSMSession

  • 157 Views
  • 3 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!