Best Practice for Linux Reconcile Account

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

Best Practice for Linux Reconcile Account

L3 Networker

We used Account Discovery to discover a thousand Linux Local Accounts in our environment. Each server has 3 accounts root, admin, and reconcile account. We can onboard it automatically, but we having an issue with associating the Reconcile Account with each admin account. If we do associate on the platform level it can associate only 1 account. I'm seeking your recommendation and experience on this matter. Highly appreciate your answers.

1 accepted solution

Accepted Solutions

L0 Member

In the platform you can use dynamic references for the reconcile account properties instead of explicitly naming the reconcile account.

To use a Dynamic Reference, use the name pattern: %Device Type%-%PlatformIO%-%Address%-%username%-<EditReconcileUserNameHere>

This means the CPM will look for the reconcile account with the same name pattern as the account that needs to be reconciled. You may need to replace PlatformID with the actual PlatformID for the Reconcile Account if it isn't the same. Here is another answer that explains it with a screenshot. https://community.cyberark.com/s/question/0D52J00009Y5pSkSAJ/how-to-create-a-dynamic-rule-for-a-reconcile-account

View solution in original post

11 REPLIES 11

L4 Transporter

Hi @Putmano Keo​ ,

​

​

Firstly, just want to know what's the challenge.

​

Do you want to link the reconcile account automatically to other accounts automatically?

 

Until the account is some sort of domain account you can't do anything more with onboarding rule for the pending accounts discovered.

 

What's my suggestion is to discovery data and onboard it via rest api script with linking the recon account capability.

 

Thank you

L4 Transporter

Hi @Putmano Keo​ ,

​

​

Firstly, just want to know what's the challenge.

​

Do you want to link the reconcile account automatically to other accounts automatically?

 

Until the account is some sort of domain account you can't do anything more with onboarding rule for the pending accounts discovered.

 

What's my suggestion is to discovery data and onboard it via rest api script with linking the recon account capability.

 

Thank you

L7 Applicator

Hi @Putmano Keo​ 

 

Ideally you should have two separate reconcile accounts created one for root and another for admin account with appropriate sudo entitlements for each. You can then associate two reconcile account for its respective platform policy.

 

This is to segregate the sudo entitlements for two reconcile accounts.

 

Hope it helps !

Hi Malhar,

 

You meant we should create another two accounts separately on all the servers and then associate the platform level. So, these accounts need to disable the Automatic Password Management. This is what I understand.

 

Hi Vamshi,

 

We have thousands of Linux local accounts. They were onboard via account discovery. The challenge is, that we need to associate the account with the Reconcile Account (also a Linux local account). I need to access each Linux local account to associate the reconciled account. I'm seeking any method that can do things faster.

L0 Member

In the platform you can use dynamic references for the reconcile account properties instead of explicitly naming the reconcile account.

To use a Dynamic Reference, use the name pattern: %Device Type%-%PlatformIO%-%Address%-%username%-<EditReconcileUserNameHere>

This means the CPM will look for the reconcile account with the same name pattern as the account that needs to be reconciled. You may need to replace PlatformID with the actual PlatformID for the Reconcile Account if it isn't the same. Here is another answer that explains it with a screenshot. https://community.cyberark.com/s/question/0D52J00009Y5pSkSAJ/how-to-create-a-dynamic-rule-for-a-reconcile-account

Hi @Putmano Keo​ 

 

The point I was referring is to segregate password management of root and admin accounts by two reconcile accounts, let's say reconcile account 1 and reconcile account 2.

 

In my view the benefits you will get will be,

 

  1. Segregation of password reset privileges / entitlements for both root and admin accounts
  2. Reconcile account 1 and reconcile account 2 can also be configured as backup of each other in terms of password reset if one of the account goes out of sync

 

Hope this helps !

 

Thank you for your suggestion, Malhar.

This is what I'm looking for, Ipapp.

 

@Lorie Papple​ - I have added below parameters at platform level. Still I get the same error. Is something need to be modified?

 

Reconcile Account Safe: RECON_Safe

Operating System-<platform id>%address%-%username%-<recon_account>

 

CACPM178E Error while creating extra passwords section - password object not found.

The CPM is trying to reconcile this password because its status matches the following search criteria: ResetImmediately,Failure

Safe: RECON_Safe

Folder: Root

Hey @Himanshu Prahari​ , I suggest you create a new post as this is an old one. I can reply in that one

  • 1 accepted solution
  • 55 Views
  • 11 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!