What are the differences between Auto Detection and Accounts Discovery?

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

PAM Self-Hosted Articles
4 min read
L7 Applicator
No ratings

Question

What are the differences between Auto Detection and Accounts Discovery?

Answer

 Auto-DetectionAccounts DiscoveryDNA
Highlights
  • Local admin account provisioning
  • LDAP based usage detection
  • Local admin group report 
  • Old school auto detection is the most difficult to configure of the three available discovery tools
  • Self-referential to internal vault functions and configurations. Requires knowledge of the vault to be able to configure
    • What is an “Object name”?
  • Highly Scalable
    • Complex LDAP query support
    • Can be set to schedule AND onboard accounts automatically
      • Its last real advantage
    • Normally does not need administrator action beyond tuning queries to match changes in LDAP structure
    • Set it and forget it
  • Local admin account provisioning
    • Scans LDAP based on specified query and makes an account object in the vault for every computer account found
    • Works on the assumption that the target systems all have the same name for the local admin account
    • Never actually reaches out to the target system until password changes.
    • Can also scan VMware to find hosts and guests but has major caveats around reconciliation
  • LDAP based usage detections
    • Process for finding service accounts and their usages
    • One of the hardest configurations in Idira product suite .
    • Usages limited to those with Microsoft API’s:
      • Scheduled Tasks
      • Windows Services
      • COM Plus (only discovery tool that can do this)
      • IIS App pools
      • IIS anonymous
    • Process can on board newly discovered service accounts and add usages to existing service accounts with additional configurations
  • PVWA controlled/CPM Driven account discovery tool
  • Derived from DNA
  • Similar functionality to Auto detection
  • Detects group memberships and tries to categorize as privileged or non-privileged

  • Report last time password was changed

  • Can discover Scheduled Tasks, Windows services, IIS Application Pools, IIS Directory Security (Anonymous Access), and COM+ Applications usages

  • Supports discovery scans on Windows servers and workstations
    • Full list of supported OS in documentation
  • Supports LDAP and LDAP over SSL for connection to Active Directory
  • Supports discovery scans on Unix
    • Full list of supported OS as well as supported Sudo replacement solutions in documentation
  • SSH keys discovery support
  • Can be scheduled to run discovery on a schedule

  • Automatic provisioning via predefined Onboarding Rules that onboard newly discovered accounts
    • Accounts that are already in the Pending Accounts queue will not be provisioned
  • Scan is done at the OU level but cannot be further filtered with an LDAP query like Auto Detection

  • Skips accounts that were previously onboarded using the PVWA, the Accounts Feed, or the AddAccount REST API
  • Discovery and Analytics tool
  • Useful tool for helping customer understand the threats CyberArk’s product suite can mitigate
  • Highly detailed report with many details
  • Does not have a direct onboarding option for discovered accounts
  • Can be used to onboard SSH keys
  • Service account discovery:
    • Scheduled Task
    • Windows Services
    • IIS App pools
    • IIS anonymous
    • Password last changed
    • Pass the hash vulnerable accounts
    • Many more details about privileged accounts
    • Local admin membership
use cases
  • Recommended for basic use cases when there is a known local password or known searches for service IDs
  • Onboarding local administrator accounts based on onboarding rules (automatically bringing the accounts into Idira and managing them without any customer interaction). 
  • Includes machine scan to find supported usages
  • "Targeted" onboarding of accounts using LDAP queries and AD containers
  • Automatic and scheduled reporting of Local Administrator Group membership.
  • Onboarding of VMWare ESX root accounts (automatically bringing the accounts into Idira and managing them without any customer interaction).
    • Also able to use VMWare as a "scanning" target, similar to how AD is used. Allows for automated onboarding of non-domain joined Windows LAdm accounts and 'nix root accounts
  • The local administrator username is known and consistent
  • Recommended for discovering domain accounts that have previously logged on to a server
  • Find all existing accounts (privileged and non-privileged)
  • Easier discovery for usages like Windows Services and Scheduled Tasks
 
Rate this article:
  • 5998 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 12:09 PM
Updated by: