Import Passwords from Lieberman

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

Import Passwords from Lieberman

L3 Networker

Client has about 2500 Windows domain service/application accounts vaulted and not managed in Lieberman. Migrating to PAS as unmanaged. Need a secure way to move existing passwords with the account .

8 REPLIES 8

L4 Transporter

If liberman has an export feature, you export the accounts, move them to a password upload utility template and then upload them to PAS.

L3 Networker

Thanks Kostya:

 

The client is concerned about the security of the passwords during the export, data prep and import process.

 

I am looking for technical and non-technical solutions or processes to maintain the security and confidentiality of the current passwords.

L4 Transporter

Well if Lieberman have an API, you could always script the whole process. Go through all the accounts one by one, then use CyberArk's REST API to import them in the Vault in the desired format. I took a quick look at the Marketplace, and a search for "Lieberman" didn't return anything, so I doubt that there's an official migration tool for it. You'll have to use the Password Upload Utility, PACLI or the REST API of CyberArk. However, the PUU is the one that leaves the passwords the most at risk since it takes time to format the .csv file you'll pass the PUU. Plus depending on the account properties, the PUU might not be able to import everything properly. From my understanding, the PACLI is being replaced by the REST API, so I would go with that.

L4 Transporter

I agree with @Yoan Schinck​ . The risk is high exporting it into a csv. Also, since we are about reducing risk, you can let your client know as part of the process, a password verification process via CPM followed by an immediate password change can be done to minimise exposure.

L4 Transporter

Alternatively, you can start by creating reconciliation accounts in CyberArk as a first step and then create dummy passwords for accounts in CyberArk that represent those accounts in Liberman. As part of the account migration process, you can then use reconciliation to set new passwords for accounts you are moving over. This way, you can plan the process to migrate accounts over systematically and reduce exposure of these passwords in the clear.

L4 Transporter

Sorry, just saw it has to moved as unmanaged..my suggestions are not really relevant in this case..

L4 Transporter

The risk for a CSV is high only if left unattended. If this is done by him and removed later, then the risk minimal at best.

 

REST is an excellent option, as the password will only be exposed in memory while running, but that also requires coding skills and knowledge in both APIs, which might be an issue here 🙂

Hi,

 

I've a quick question. How did you design the safes in CyberArk for respective accounts that you migrated from Lieberman ERPM?

 

In ERPM we have a concept of Management Sets and also account level permissions? Just want to understand what was your strategy while migrating the accounts from ERPM to CyberArk considering we want to give the right permission to the users (not more not less)?

  • 607 Views
  • 8 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!