White Papers Frequently Asked Questions FAQ for Security Officers
Hitachi ID Facebook Page Hitachi ID Twitter Page Find us on Google+ Hitachi ID YouTube Page

Frequently Asked Questions for Security Officers


How does Hitachi ID Password Manager improve security?

Password Manager improves the security of authentication processes:


How does Password Manager authenticate users?

(1)Users may authenticate into Password Manager as follows:


How does Password Manager get challenge/response data for non-password authentication?

Users can authenticate to Password Manager by answering security questions, where the data is stored in the Password Manager identity cache or on an existing system (e.g., database, directory, etc.).

If the data is stored in Password Manager, then it is normally encrypted using 128-bit AES and a private key.

If the data is stored on an existing system, then Password Manager will call a plug-in program to retrieve questions and validate answers, as required. Standard plug-in programs for LDAP and SQL are provided.


Can one user "claim" another user's login ID?

To attach an existing login account, with a non-standard ID, to their user profile, a user can enroll. This is done by entering an ID and password combination for that account into an enrollment page in the Password Manager portal.

The process to register or "claim" user IDs in Password Manager is as follows:

  1. Password Manager portal: asks user to authenticate using a primary credential
  2. User: signs in, for example with AD credentials.
  3. Password Manager portal: validates the password against the indicated system.
  4. Password Manager portal: display a list of already-attached IDs. Ask for an additional IDs.

  5. User: enters his login ID and current password for a system that does not yet appear on the list.

    Note: the user does not specify which system the ID is for.

  6. Password Manager portal: finds instances of this ID in its database. Eliminates already-assigned IDs. Tries to connect to each remaining system with the credentials entered by the user. For systems where the login was successful, adds the system ID / login ID to the user's profile.

    repeat as necessary.


Does Password Manager transmit all sensitive data encrypted?

(2)Data transmitted to and from Password Manager on the network is cryptographically protected, as illustrated by the following examples:

Data transmitted to/from the Password Manager server
To/From Algorithm Key length
Interactive sessions    
User browser SSL (varies) 128 bits.
Trigger password synchronization    
From Win2K/2K3 AD DC 128-bit AES 128-bit shared secret.
From z/OS    
From Unix    
From LDAP server    
Set passwords, Create/update users    
To SSH scripted target SSH Varies by SSH configuration
To Unix agent 128-bit AES 128-bit shared secret.
To z/OS task    
To RSA Authentication Manager    
To proxy server    
API Session - socket    
From calling system / IVR 128-bit AES 128-bit shared secret.
API Session - web services    
From calling system / IVR HTTPS 128 bits.
Set passwords, Create/update users    
To target system native Varies. Use proxy server when native protocol is inadequate.

 


Does Password Manager store all sensitive data encrypted?

Encryption is used to protect stored Password Manager data as follows:

Data stored on the Password Manager server
Data Algorithm Key
Privileged passwords, used to log into target systems 128-bit AES 128-bit random
Answers to security questions 128-bit AES 128-bit random
User old password history SHA-1 64-bit random salt