Personally Identifying Information (PII for short) is data that describes a person which is considered to be sensitive in a legal jurisdiction. PII may include a person's name, social security or social insurance number, mailing address, personal e-mail address, credit card numbers, driver's license number, telephone number, etc.

Many jurisdictions (e.g., USA, European Union, etc.) and some organizations (e.g., Payment Card Industry) have laws, rules and regulations that require organizations to take special care when handling PII, to not share it, to protect it against accidental disclosure or malicious compromise, to notify users of such compromise. Different rules may pertain to different types of organizations or data. For example, PCI-DSS pertains to protection of credit card data, HIPAA pertains to protection of health insurance data, GLB refers to investor data, etc.

Hitachi ID Identity Manager attaches access rights not to sets of users but to types of relationships, using user classes. This is essential to privacy protection, as illustrated by the following example:

  • Consider a very sensitive profile attribute -- scheduled termination date. This may be mundane as it applies to contractors, representing the end of an engagement. It may also be very sensitive, indicating when an employee is due to be terminated.
  • Who can access this data depends on relationships. For example, HR users should be able to access this data for all users -- except themselves. Managers should be able to access this data for their direct and indirect subordinates, but not themselves or other people who do not report to them.
  • The Hitachi ID Identity Manager access control model allows organizations to define types of relationships, such as "recipient in HR, recipient and requester are not the same person." or "recipient reports to requester."
  • Access rights are linked to types of relationships, as above.
  • The search engine provided through Hitachi ID Identity Manager respects these access rights, to protect against data leakage. For example, a manager might search for all users who are scheduled for near-term termination and will only see those who report to him -- but not himself or others.

Using relationships makes it easy to define various user support models. For example, users in a country-specific help desk can reset passwords for other users in the same country, or managers in some regions may be allowed to reset passwords for their direct (or indirect) reports.

Using this access control model makes it practical to manage highly sensitive or privacy-related data using the Hitachi ID Identity Manager request portal and approvals workflow. Personal data such as date of birth, social security number, student or employee number, enrollment and deactivation dates, healthcare classification and more are all safe to manage using Hitachi ID Identity Manager.

Hitachi ID Password Manager is a solution that helps users to more effectively manage their already-existing credentials and resolve problems such as forgotten passwords or PINs in a self-service fashion.

Return to Identity Management Concepts