You can view the results of running one or more Account Discovery jobs. To see the results of discoveries, see Discovered Accounts
To view Account Discovery results
- Navigate to Asset Management > Discovery > Accounts (add or edit a Account Discovery job).
- On the Account Discovery Results tab:
- Select the time frame of the completed jobs you want to display which ranges from the last 24 hours to the last 7, 30, 60, or 90 days. Or, click Custom to create a custom time frame.
- Click
Refresh to refresh the results.
- View the following information displays for each job:
- Date/Time: The most recent date the Account Discovery job successfully ran.
- User: The user who ran the job or Automated System, if the job is run on an automated schedule.
- Event: The outcome of running the Account Discovery job event, which may be Account Discovery Succeeded, Account Discovery Failed, or Account Discovery Started.
- Asset: The asset which is associated with the Account Discovery job.
- Partition: The partition in which the discovered accounts will be managed.
- Profile: The profile which will govern the discovered accounts.
- Appliance: The name of the Safeguard for Privileged Passwords Appliance.
- # Accounts: The number of accounts found during the discovery job; click to view details.
You can view the results of all Account Discovery jobs that have ever run in a partition (in other words, all accounts ever discovered) and choose to enable or disable the accounts.
Accounts created display as managed accounts in the Discovered Accounts properties grid (see below). For more information, see .
Go to Discovered Accounts:
web client: Navigate to Asset Management > Discovery > Discovered Items > Accounts tile.
Use these toolbar buttons to manage the discovered accounts.
Table 132: Discovery: Discovered Accounts toolbar
|
 Manage
|
Click Manage to change the status to managed for one or more selected accounts. Accounts that are managed by Safeguard for Privileged Passwords will be added to the asset's list of accounts and access request policies. The Discovery job may mark the accounts managed, or they can be selected and marked managed using this button. |
|
 Ignore
|
Click  Ignore to set the Status to Ignore to prevent Safeguard for Privileged Passwords from managing the selected account. If the status of the account is None then the resulting status will be Ignored.
If the status of the account is Managed then you will need to use the Accounts page to change the status. |
|
 Show Ignored
|
Display the accounts with a Status of Ignored. |
|
 Hide Ignored
|
Hide the accounts with a Status of Ignored. |
|
 Export
|
Use this button to export the listed data as either a JSON or CSV file. For more information, see Exporting data. |
|
Refresh |
Retrieve and display an updated list of discovered accounts. Ignored accounts are not displayed if Hide Ignored is selected. |
|
 Search
|
Enter the character string to be used to search for a match. For more information, see Search box. |
The following information displays.
Table 133: Discovery: Discovered Accounts properties grid
|
Status |
The discovered account may be:
- Managed: A discovered account that is managed.
- None: A discovered account that was not auto managed when discovered.
- Ignored: A discovered account that was not auto managed and was ignored from discovery.
- Disabled: A discovered account that previously had the status of Managed and then was marked Ignored. A disabled account is not removed from the Asset account list nor unconfigured as a dependent account. It is marked disabled and cannot be used or acted upon.
|
|
Name |
The name of the account in Safeguard that maps to the discovered account associated with the asset. This can be a local account or an Active Directory account |
|
Domain Name |
The domain name of the account if the account is an Active Directory account. |
|
Asset Name |
The name of the asset the account was discovered on. |
|
Account Discovery Job |
Name of the discovery schedule. |
|
Asset Discovery Rule |
The name of the Asset Discovery rule applied that discovered the account. |
| Date/Time Discovered |
The date and time when the service or task was discovered. |
Setting up Service Discovery
To discover Windows services, you must first create an Account Discovery job, including an Account Discovery Rule, and select Discover Services. When the discovery job is run, services are discovered. The discovery of services is not dependent on the discovery rules. For more information, see Adding an Account Discovery job.
To view Service Discovery results
- Navigate to Asset Management > Discovery > Accounts > (add or edit a Account Discovery job).
- On the Service Discovery Results tab:
- Select the time frame of the completed jobs you want to display which ranges from the last 24 hours to the last 7, 30, 60, or 90 days. Or, click Custom to create a custom time frame.
- Click Refresh to refresh the results.
- Click Search and enter the character string to be used to search for a match. For more information, see Search box.
- View the following information displays for each job:
The Discovered Services tile displays information for the selected partition on which the services were discovered.
The Asset Administrator or delegated administrator can configure service discovery jobs to scan Windows assets and discover Windows services that may require authorization credentials.
The following types of services are discovered on managed Windows assets:
-
Windows services
-
Scheduled tasks
-
IIS Application Pools
-
Com+ applications
If the Windows asset is joined to a Windows domain, the authorization credentials can be local on the Windows asset or be Active Directory credentials.
IMPORTANT: For Windows SSH assets, a local account does not have the access necessary to discover services running as domain accounts. So if a local account is used as the service account for a Windows SSH asset, Safeguard for Privileged Passwords will only discover services running as local accounts on that asset and domain account dependencies will not be updated.
IMPORTANT: If your asset's management type is Windows or WinRM (either desktop or server) then in order to discover IIS App Pools using Service Discovery, you will need to install one of the following features under the Management Tools section of the Web Server role:
NOTE: Discovery is supported for each of these service types on both Windows Server and Windows SSH platforms, but only the Windows SSH platform supports updating account dependencies on IIS App pools and Com+ applications.
Running Service Discovery jobs automatically and manually
- Service discovery jobs run automatically in the background if Discover Services check box is selected. If the Automatically Configure Dependent Systems check box is selected, any directory accounts that are discovered in the Service Discovery job are automatically configured as dependent accounts on the asset where the service was discovered. For more information, see Adding an Account Discovery job.
- You can manually run a Service Discovery job from Asset Management > Assets > Discovered Services. For more information, see Discovered Services tab (asset).
Discovered services and tasks association to known Safeguard accounts
Service discovery jobs associate Windows services with accounts that are already managed by Safeguard for Privileged Passwords. The accounts put under management display with an Account Status of Managed.
Service Discovery with Active Directory
A discovered service configured to run as an Active Directory account can be automatically associated to the asset with the account managed by Safeguard. Effectively, the asset will have an account dependency on the account.
To automatically associate, the Account Discovery job (which runs when Safeguard synchronizes the directory) must have the Automatically Manage Found Accounts check box selected. For more information, see Adding an Account Discovery rule. Once configured as an account dependency, when the Active Directory account’s password is changed by Safeguard, Safeguard updates the password for the service on the asset, according to the asset’s profile change settings. For more information, see Adding change password settings.
View Service Discovery job status
From the Activity Center, you can select the Activity Category named Service Discovery Activity, which shows the Event outcomes: Service Discovery Succeeded, Service Discovery Failed, or Service Discovery Started.
Discovered Services toolbar and properties
Go to Discovered Services:
- web client: Navigate to Asset Management > Discovery > Discovered Items > Services tile.
Use these toolbar buttons to manage the discovered services.
Table 134: Discovery: Discovered Services toolbar
|
Show | Ignore |
The Show and Ignore buttons control the Service Ignored column on this window so the administrator can either display or ignore the rows.
The Account Status column is controlled by the Manage and Ignore buttons on the Discovered Accounts grid. For more information, see Discovered Accounts. |
|
Show Ignored |
Display the accounts with a Status of Ignored. |
|
Hide Ignored |
Hide the accounts with a Status of Ignored. |
|
Export |
Use this button to export the listed data as either a JSON or CSV file. For more information, see Exporting data. |
|
Refresh |
Retrieve and display an updated list of discovered accounts. Ignored accounts are not displayed if Hide Ignored is selected. |
|
Search |
Enter the character string to be used to search for a match. For more information, see Search box. |
The grid shows the Asset Name, Account, Domain Name, System Name, and Account Status for the Discovered Account that Safeguard found that is matched up with the service discovered. The service is identified by a Service Name (with a Service Type of Service, IIS App pool, Com+ service, or Task).
Table 135: Discovery: Discovered Services properties
| Asset Name |
The name of the asset where the service was discovered. |
|
Account |
The name of the account that maps to the Discovered Account column. |
|
Domain Name |
The domain name of the account if the account is an Active Directory account. Used to help determine uniqueness. Only Active Directory accounts can be configured as dependent accounts. |
|
System Name |
The system or asset that hosts the discovered mapped account. |
|
Account Status |
The Account Status column is controlled by the Manage and Ignore buttons on the Discovered Accounts grid. For more information, see Discovered Accounts.
The discovered account may be:
- Managed: A discovered account that is managed.
- None: A discovered account that was not auto managed when discovered.
- Ignored: A discovered account that was not auto managed and was ignored from discovery.
- Disabled: A discovered account that previously had the status of Managed and then was marked Ignored. A disabled account is not removed from the Asset account list nor unconfigured as a dependent account. It is marked disabled and cannot be used or acted upon.
|
| Dependent Account |
A  check displays if the account is associated as an account dependency on the asset. The value is blank if the account is not associated as an account dependency of the asset. This automatic dependency mapping only happens if the Automatically Manage Found Accounts option is selected on the Account Discovery job associated with the profile that is associated to the asset. For more information, see Adding an Account Discovery job. |
|
Service Type |
Type of service discovered. Values may be Service, IIS App pool, Com+ service, or Task. |
|
Service Name |
The name of the discovered service. |
|
Service Enabled |
A check displays if the service on the asset is enabled on the target machine. If there is no check mark, the service is disabled on the target machine. |
|
Service Ignored |
Ignored means the service will not show up in the grid. In other words, the service is hidden. This is controlled by the Show | Ignore actions on this grid. |
|
Discovered Account |
The discovered account name. If the account has an Account Status of Managed, then the Account, Domain Name, and System Name display. |
| Date/Time Discovered |
The date and time when the service was discovered. |
