Skip to main content

Hitachi ID certification

Product Sites

Service Account Password Management

Service account password management refers to a process for orchestrating changes to service account passwords in a security database or directory with matching notification to subscribers (i.e., those OS components which start unattended processes such as services and scheduled jobs) of new password values.

Any password which persists for a long period of time may be compromised by an attacker. Attack methods may include:

  • Repeated attempts to authenticate to the primary security database (on the network) as the account in question.
  • Extracting a copy of the primary security database's database of password hashes and attacking that local copy.
  • Extracting a copy of the persistent storage used by a subscriber to hold service account passwords and using passwords from that data to connect to the primary security database.
  • Human beings who set a service account password in both the primary security database and any subscribers misusing, sharing or otherwise compromising those passwords. This is especially problematic if the network perimeter has been breached and malicious parties have access to sensitive subscribers and/or primary security databases.
  • Inability to monitor or control use of service accounts by people who do have a legitimate need to know their passwords.

The solution to all of these security concerns is the same: periodically change service account passwords to new and random values, which are not known to humans and which limit the time available to an attacker to compromise a password. When humans require manual access to these accounts (for example, to schedule a new job or install a new service), control access to these accounts and promptly change the password to a value not known to any humans.

Hitachi ID Privileged Access Manager can be configured to secure service account passwords. This means two things, depending on the mode of operation:

  1. In push mode (i.e., no local agent on the Windows server), Privileged Access Manager servers periodically connect to Windows servers or Active Directory in order to change the passwords of service accounts.
  2. If the local workstation service is installed on a Windows system (i.e., the "pull mode" agent), the Privileged Access Manager service periodically changes service account passwords locally, in coordination with the central Privileged Access Manager server cluster.

In both cases, Privileged Access Manager must notify the program that launches services -- the subscriber -- of the new password value, so that it can successfully launch the service at the time of the next system restart or when an administrator manually stops and restarts the service in question. In some cases, for example when domain accounts are used to run services, an immediate restart may be required or advisable, due to Kerberos token expiry. Privileged Access Manager can be configured to restart services after each automated password change.

Privileged Access Manager includes extensive automation to discover subscribers and subscriber-to-service-account dependency. This allows Hitachi ID Systems customers to review what services are run in the security context of what named users, on what systems. This is particularly helpful where services run in the security context of domain accounts, since multiple services on multiple servers may run as the same service account and may therefore require notification after each password change.

Privileged Access Manager includes several mechanisms to accomplish safe and secure changes to service account passwords:

  1. Auto-discovery of subscriber/account dependencies for a variety of subscriber types: IIS (multiple sub-components may have service accounts/passwords), Scheduler, SCM, DCOM, at various OS and subscriber versions.
  2. White-list policy tables:
    1. Initialized with discovered data about service accounts and services.
    2. Allow organizations to specify a password randomization schedule.
    3. Allow organizations to name application owners, who will be notified of password changes and any issues.
    4. Allow organizations to specify a style of notification. For example, notify the subscriber of new password values before a password change, after or both? Restart the subscriber or not?
  3. A mechanism that tests for the availability of all subscribers before each password change. In particular, if some systems where services run in the security context of a domain service account are unreachable, then changes to that account's password will be deferred.
  4. Built-in tools to notify subscribers of new password values and restart services if this was specified in the policy.
  5. A transaction manager that will retry notifications to subscribers that went off-line after a password was changed and before they could be notified of the new password value.

The above are primarily used when managed systems are integrated with Privileged Access Manager in "push mode" -- i.e., there is no locally installed agent on the target system and Privileged Access Manager initiates all connections remotely, over the network, directly or via a Privileged Access Manager proxy server deployed near the target system.

Where push mode is inappropriate -- for example because the relevant services (remote registry, WMI, etc.) are disabled or firewalled or because the end system is offline or inaccessible due to name resolution or IP routing issues (NAT, etc.), a local workstation service can be installed on the managed system, which performs essentially the same functions but with much simpler connectivity (call home over HTTPS) and no need for network accessible services on the local system.

The local workstation service is most often used on laptops and in firewalled network segments (DMZs).

Privileged Access Manager is normally configured to contact application owners after each password change and in the event of a problem. This makes troubleshooting easier in the event that notification failed and a service subsequently could not be started.

The entire infrastructure mentioned here is extensible. Customers can expand it to support other process-launching systems, such as third job party schedulers for example.

Return to Identity Management Concepts

page top page top