Tchater maintenant avec le support
Tchattez avec un ingénieur du support

One Identity Safeguard for Privileged Passwords 7.0.x LTS - Administration Guide

Introduction System requirements and versions Using API and PowerShell tools Using the virtual appliance and web management console Cloud deployment considerations Setting up Safeguard for Privileged Passwords for the first time Using the web client Home Privileged access requests Appliance Management
Appliance Backup and Retention Certificates Cluster Enable or Disable Services External Integration Real-Time Reports Safeguard Access
Asset Management
Account Automation Accounts Assets Partitions Discovery Profiles Tags Registered Connectors Custom platforms
Security Policy Management
Access Request Activity Account Groups Application to Application Cloud Assistant Asset Groups Entitlements Linked Accounts User Groups Security Policy Settings Reasons
User Management Reports Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions Appendix A: Safeguard ports Appendix B: SPP and SPS join guidance Appendix C: Regular Expressions About us

Discovered Services

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 128: Discovery: Discovered Services toolbar
Option Description

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 129: Discovery: Discovered Services properties
Property Description
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.

SSH Key Discovery

You can schedule one or more SSH Key Discovery jobs to run automatically against the accounts you have added to Safeguard for Privileged Passwords (SPP). The SSH keys in the scope of the discovery job may include SSH keys that were previously added (manually) to the SPP partition.

For more information, see Discover SSH Key settings.

When an SSH Key Discovery job runs, the found SSH keys are listed in the Discovered SSH Keys tile in the selected partition. They are also shown in Assets (under the Discovered SSH Keys tab) and in Accounts (under the Discovered SSH Keys tab).

Supported platforms

SSH Key Discovery is supported on the following platforms:

  • Hardware/Custom (A custom script is required to accommodate how keys are handled.)
  • Drac
  • Fortinet
  • Junos
  • PanOs
  • Window OS
  • General Unix style platforms
    • Linux
    • Aix
    • Hpux
    • Solaris
    • F5BigIP
    • FreeBSD
    • MacOS
Properties and toolbar

Go to SSH Key Discovery:

  • web client: Navigate to Asset Management | Discovery | SSH Keys.

Use these toolbar buttons to manage the SSH Key Discovery jobs.

Table 130: SSH Key Discovery: Toolbar
Option Description
New SSH Key Discovery Job

Add an SSH Key Discovery job. For more information, see Adding an SSH Key Discovery job.

Delete

Delete the selected SSH Key Discovery job.

View Details

Modify the selected SSH Key Discovery job. You can also double-click a row to open the edit dialog.

Discover SSH Keys

Click this button to open a new window where you can select a single account to run the selected SSH Key Discovery job on.

Occurrences

View the accounts associated with the selected discover SSH key settings by account Name and Asset Name. The Inherited column has a check mark if the assignment is an inherited association via the asset. If not inherited, the accounts have an explicit assignment to a Profile/SSH Key Discovery job. For more information, see About profiles.

Export

Use this button to export the listed data as either a JSON or CSV file. For more information, see Exporting data.

Refresh

Update the list of SSH Key Discovery jobs.

Search

Enter the character string to be used to search for a match. For more information, see Search box.

SSH Key Discovery jobs display in the grid.

Table 131: SSH Key Discovery: SSH Key Discovery job grid
Name Name of the SSH Key Discovery job.
Created By Indicates the creator of the SSH Key Discovery job.
Partition

The partition in which to manage the discovered SSH keys.

Schedule

Designates when the SSH Key Discovery job runs.

Profiles

Lists the number of profiles that are configured with this job. Click the link to go to the SSH Key Profiles dialog that lists the Name and Description of the SSH key profiles that are associated with this SSH key discovery job.

Accounts

Lists the number of accounts that are associated with this SSH key discovery job via profile association. Click the link to view the account Name and parent System Name of this SSH key discovery job.

Description

The description of the SSH Key Discovery job.

SSH Key Discovery job workflow

The SSH Key Discovery jobs discover SSH keys of the accounts that are in the scope of the profile. You can configure, schedule, and run SSH Key Discovery jobs. After a job has run, you can view the Discovered SSH Keys under the tab of that name. You will see the following: Key Fingerprint, Comment (that is in the key), Key Type, Key Length, Asset Name, Account Name, and Account Status ("managed" means Safeguard for Privileged Passwords manages the account, and "disabled" means Safeguard for Privileged Passwords does not manage the account).

  1. Set up the partition with the SSH key profile. For more information, see SSH Key Profiles tab (partitions).
  2. Create an SSH Key Discovery job. For more information, see Adding an SSH Key Discovery job.
  3. SSH Key Discovery jobs can be scheduled to run automatically. In addition you can manually launch a job on a single account: 

    • From Asset Management | Discovery | SSH Keys select the SSH Key Discovery job to run, then click Discover SSH Keys.
  4. After the SSH Key Discovery job runs, click SSH Key Discovery Results tile to view the SSH Keys found. For more information, see SSH Key Discovery Results.

    NOTE: The discovery job finds all current SSH keys that match the discovery rule's criteria. SSH Key Discovery does not update existing accounts.

Search the Activity Center for information about discovery jobs that have run. Safeguard for Privileged Passwords lists the SSH Key Discovery events in the SSH Key Discovery Activity category. For more information, see Activity Center.

Adding an SSH Key Discovery job

It is the responsibility of the Asset Administrator or the partition's delegated administrator to configure the rules that govern how Safeguard for Privileged Passwords performs SSH key discovery. For more information, see SSH Key Discovery job workflow.

To add an SSH Key Discovery job

  1. Navigate to Asset Management | Discovery | SSH Keys.
  2. Click  New SSH Key Discovery Job to open the New SSH Key Discovery Job dialog.
  3. Provide the following:
    1. Name: Enter a name for the account discovery job. Limit: 50 characters.

    2. Description: Enter descriptive text about the SSH Key Discovery job. Limit: 255 characters

    3. Partition: Browse to select a partition.

    4. To identify when to Discover SSH Key, on the Schedule tab:

      • Select a time frame:

        • Never: The job will not run according to a set schedule. You can still manually run the job.
        • Minutes: The job runs per the frequency of minutes you specify. For example, Run Every 30/Minutes runs the job every half hour over a 24-hour period. It is recommended you do not use the frequency of minutes except in unusual situations, such as testing.
        • Hours: The job runs per the minute setting you specify. For example, if it is 9 a.m. and you want to run the job every two hours at 15 minutes past the hour starting at 9:15 a.m., select Run Every 2/Hours/@ minutes after the hour 15.

        • Days: The job runs on the frequency of days and the time you enter.

          For example, Run Every 2/Days/Starting @ 11:59:00 PM runs the job every other evening just before midnight.

        • Weeks The job runs per the frequency of weeks at the time and on the days you specify.

          For example, Run Every 2/Weeks/Starting @ 5:00:00 AM and Repeat on these days with MON, WED, FRI selected runs the job every other week at 5 a.m. on Monday, Wednesday, and Friday.

        • Months: The job runs on the frequency of months at the time and on the day you specify.

          For example, If you select Run Every 2/Months/Starting @ 1:00:00 AM along with Day of Week of Month/First/Saturday, the job will run at 1 a.m. on the first Saturday of every other month.

      • Select Use Time Windows if you want to enter the Start and End time. You can click Add or Remove to control multiple time restrictions. Each time window must be at least one minute apart and not overlap.

        For example, for a job to run every ten minutes every day from 10 p.m. to 2 a.m., enter these values:

        Enter Run Every 10/Minutes and set Use Time Windows:

        • Start 10:00:00 PM and End 11:59:00 PM
        • Start 12:00:00 AM and End 2:00:00 AM

          An entry of Start 10:00:00 PM and End 2:00:00 AM will result in an error as the end time must be after the start time.

        If you have selected Days, Weeks, or Months, you will be able to select the number of times for the job to Repeat in the time window you enter.

        For a job to run two times every other day at 10:30 am between the hours of 4 a.m. and 8 p.m., enter these values:

        For days, enter Run Every 2/Days and set Use Time Windows as Start 4:00:00 AM and End 8:00:00 PM and Repeat 2.

      If the scheduler is unable to complete a task within the scheduled interval, when it finishes execution of the task, it is rescheduled for the next immediate interval.

  4. To save and close , click OK.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation