New Discovery UI - Discovered Accounts unusable

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 UI - Discovered Accounts unusable

L3 Networker

Dear All,

On a new tenant, we only have the new UI for discovered accounts which is highly problematic.

 

  1. Neither the domain, password age, dependencies are visible on the list
    1. Especially the dependencies are one of the most critical info on the discovery we need to see with “one look” and not open each account and search in the info if there is and dependancy.
  2. There is no way to sort the results by username, address, platform, etc
  3. On the list, it shows accounts that already onboarded without any flag or something. This is critical since if someone onboard an already existing account this can cause major issues on the client side. (duplicate cyberark accounts managing the same account). On the old scanning if the account was onboarded there was an error on the scan but the account was not visible to be onboarded.

 

Missing all the above (and still missing the option to export the results) it will take a huge amount of time to review them.

Even with RestAPI export (which ofcourse is not practial) there is a limit to the accounts that will be fetched (1000 if i remember correctly).

below examples of new vs old UI

I strongly believe that either the old UI must return as soon as possilbe, or to add an option to export the results (showing the dependacies on each account)

Field_Content_versions_oct20__068Vy00000KZiDxIAL.pngField_Content_versions_oct20__068Vy00000KZjUzIAL.png

1 REPLY 1

L3 Networker

On point 3 - do the account details match EXACTLY? If the Name & Address don't match exactly, it won't be seen as the same account by Discovery.

For example, if Discovery finds "[email protected]" on "Domain.com", but you've onboarded it as "Username" on "Domain.com" that's not a match.

 

When I was testing Discovery for our organization I made a point of checking for this issue and was unable to produce the problem you've reported.

 

I agree completely on your other points. The interface is completely impractical for anything larger than a private lab.

  • 176 Views
  • 1 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!