Hitachi ID Privileged Access Manager & Password Manager

Discussion created by NathanF on Nov 18, 2011
Latest reply on May 16, 2012 by NathanF

Hitachi ID Privileged Access Manager and Hitachi ID Password Manager leverage RSA enVision to provide centralized reporting of audit logs as well as system errors, warnings & usage. Examples of events reported to RSA enVision include:


  • Who signed into a privileged account, when and from where.
  • Database replication errors and warnings, such as failure of one Hitachi ID Privileged Access Manager node to replicate new passwords to another, often in another data center.
  • The number of users who reset their password using self-service password reset and/or enrolled security question/answer data into their profile.


This integration is achieved by configuring RSA enVision to monitor Hitachi ID Privileged Access Manager's or Hitachi ID Password Manager's internal audit database tables.


Release Date

What’s New In This Release


Initial support for Hitachi ID Privileged Access Manager and Password Manager


Converted XML to Content 2.0


Note: Content 2.0 features substantial improvements to the parsing of event data into the various tables that are used for queries and reports. Content 2.0 is the future direction for all event sources within the supported library. For rules and reports, note the following:

-For factory reports, as existing event sources are converted to Content 2.0, their device-specific reports are updated to work with the new content. In some cases, class-specific reports have replaced device-specific reports.

-Factory correlated rules have been modified to take advantage of the improved tables, variables and parsing.

-Custom rules, that involve event sources updated to work with Content 2.0, need to be rewritten.

-Custom reports may not produce the same results as previously. For guidance on updating custom reports, see the RSA enVision Content Inspection Tool document and the online Help topics that describe the Content 2.0 tables