New discovery creates duplicate dependencies (Windows Services, Scheduled Tasks) which require manual deletion within the classic interface.

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

New discovery creates duplicate dependencies (Windows Services, Scheduled Tasks) which require manual deletion within the classic interface.

L2 Linker

I asked if this was expected behavior in the roadmap call and was told it wasn't and we should open a support case, but looking back at my closed cases (03905301) they said this is just an unfortunate issue when the CyberArk back end database loses sync and there's nothing we can do to prevent it. This makes automating discovery scans to identify new dependencies impossible to scale to an enterprise wide process.

 

Please tell me someone else has found a fix for this - currently we can't run new discovery scans without creating a giant annoying mess to go manually re-delete all the dependencies one at a time.

9 REPLIES 9

L2 Linker

We are currently stalled at proceeding with service account onboarding. I can't picture manually deleting duplicative dependencies from hundreds of service accounts when they randomly stop being managed by cyberark represents the product operating as intended but support keeps refusing to acknowledge this is an issue.

L7 Applicator

hey @Mike Mason​ 

I'm checking internally to see if I can find a good resolution for this, but maybe you can make a script via RESTApi to do this? I'm honestly not sure.

 

Perhaps maybe @Malhar Vora​ might have a suggestion here? No pressure, though.

 

-Matt

L7 Applicator

Hi @Mike Mason​  and @Matt Jennison​ 

 

The REST API script would be a great solution to identify and delete duplicate dependencies.

 

Another option I’m thinking is to limit the scan scope. Instead of broad enterprise-wide scans, consider running targeted scans on specific OUs or IPs where you know new accounts or dependencies might exist. This will reduce volume of data and the potential for duplicate creation.

 

Also instead of full automation of onboarding after discovery, use the discovery reports to identify potential new dependencies and then manually verify if they are truly new or duplicates before onboarding them.

 

Has there been an ER raised for the database sync issue ?

 

What discovery reports are available and how do we get to them?

Do they show newly discovered dependencies?

 

I went through the new discovery saas course in the CyberArk University but it never referenced how to view dependencies or any reporting available.

 

The videos did show how to view newly discovered accounts in the new accounts list, but I believe part of our challenge is we've already onboarded these accounts so they don't show up there. When the scan decides these already onboarded accounts have new dependencies (even though they are already existing dependencies in CyberArk and nothing has changed with the scheduled task or service) the account goes into an unmanaged state no longer rotating credentials. We then have to go manually delete the dependencies in the classic interface and re-enable the account so it will resume automated password rotation.

 

My impression was an ER was not created for the sync issue, we were basically left with no resolution.

@Malhar Vora​ we ran a new discovery scan and re-created the duplicate dependency detection which disables management of the account, but we cannot find any reports like you mentioned. Is there any sort of discovery reporting that shows newly discovered dependencies for existing accounts?

 

We will also follow up on the existing support case, but support seems to not know about any reporting that would show this either.

L4 Transporter

Hi @Mike Mason​ 

 

Since several community members answered your question, please let us know if these solutions addressed your query.

If so, it would be great if you could mark the most helpful response as 'Select as Best' to assist other community members with similar questions.

 

Thank you, Liad.

I still don't know what reports @Malhar Vora​  was referencing otherwise I would select the answer as best, but I and support were unable to identify any reporting that showed us which dependencies were "discovered" even though they already existed. We did eventually get support to acknowledge the bug though I haven't seen it show up in Known Issues yet.

L7 Applicator

Hi @Mike Mason​ 

 

Apologies for the delay in responding to this message.

 

Please manually verify if they are new or if they are duplicates of existing dependencies before onboarding them.

 

I can see a feature introduced to manage dependencies in the recent release notes for self-hosted but I haven’t been able to check for Priv cloud.

 

https://docs.cyberark.com/pam-self-hosted/latest/en/content/release%20notes/rn-whatsnew.htm

 

 

 

Thanks, unfortunately the dependencies don't go through an onboarding process. The issue is that an existing account has already been discovery scanned and onboarded. When the discovery scan runs again, the same account and same dependencies exist, but suddenly the account stops being managed and duplicate versions of the already existing dependencies automatically appear - we don't have an option not to onboard the dependencies to an already-onboarded account.

  • 292 Views
  • 9 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!