Server requirements - Hitachi ID Privileged Access Manager
Multiple, Load-Balanced Servers
Hitachi ID Privileged Access Manager supports multiple, load-balanced servers.
Each server can host multiple Privileged Access Manager instances, each with its own
users, managed systems, features and policies.
Privileged Access Manager must be installed on a Windows 2012 or Windows 2012/R2 server.
Installing on a Windows server allows Privileged Access Manager to leverage
client software for most types of target systems, which is available
only on the "Wintel" platform. In turn, this makes it possible for
Privileged Access Manager to manage passwords and accounts on target systems without
installing a server-side agent.
The Privileged Access Manager server must also be configured with a web server.
Since the Privileged Access Manager application is implemented as CGI executables,
any web server will work. The Privileged Access Manager installation program
can detect and automatically configure IIS but Apache can be
manually configured instead if required.
Privileged Access Manager is a security application and should be locked down accordingly.
Please refer to the Hitachi ID Systems document about hardening Privileged Access Manager
servers to learn how to do this. In short, most of the native
Windows services can and should be removed, leaving a very small
attack surface, with exactly one inbound TCP/IP port (443):
- No ASP, JSP or PHP are used, so such engines should be disabled.
- .NET is not required on the web portal and in most cases can be
disabled on IIS.
- No ODBC or DCOM are required inbound, so these services should
be filtered or disabled.
- File sharing (inbound, outbound) should be disabled.
- Remote registry services should be disabled.
- Inbound TCP/IP connections should be firewalled, allowing only port
443 and possibly remote desktop services (often required for some
configuration tasks), plus a handful of port numbers between Privileged Access Manager
servers, for replication.
Each Privileged Access Manager server requires a database instance. Microsoft SQL 2012 is the
most common option, Microsoft SQL 2014 will be officially supported in Q1,
2016. Oracle database is also supported in the current release.
** Please note that support for using an Oracle database is being discontinued
as of version 10.0 which is scheduled for release in Q1, 2016.
Production Privileged Access Manager application servers are normally configured
- Hardware requirements or equivalent VM capacity:
- An Intel Xeon or similar CPU.
Multi-core CPUs are supported and leveraged.
- At least 8GB RAM -- 16GB or more is typical for a server.
- At least 500GB disk, preferably configured as RAID for reliability and
preferably larger for retention of more historical and log data.
More disk is always better, to increase log retention.
- At least one Gigabit Ethernet NIC.
- Operating system:
- Windows 2012R2 Server, with current service packs.
- The server should not normally be a domain controller and in
most deployments is not a domain member.
- Installed and tested software on the server:
- TCP/IP networking, with a static IP address and DNS name.
- Web server (usually IIS).
- Client software: web browser, Acrobat or other PDF reader,
native clients for the systems that Privileged Access Manager needs to interface
- SQL Server client or Oracle client to connect to the Privileged Access Manager
- SSL server certificate, for HTTPS connections to the web
portal and SOAP API.
- A database instance is required to host the Privileged Access Manager schema. Most
customers use Microsoft SQL Server 2012, but Oracle 11gR2 is also supported up
to version 9.0. (support for using Oracle database is being discontinued as of
release 10.0 (Q1, 2016)). The SQL Server database software can be deployed on
the same server as the Privileged Access Manager application, as this reduces hardware cost
and allows application administrators full DBA access for troubleshooting and
performance tuning purposes.
In addition to a web/application server, Privileged Access Manager requires a database
server. In most environments, the database server software (Microsoft
SQL Server or Oracle Database Server) is installed on the same
hardware or VM as the Privileged Access Manager software, on each Privileged Access Manager server node.
This reduces hardware cost, eliminates network latency and reduces
the security surface of the combined solution.
Database I/O performance on a virtualized filesystem (e.g., VMDK or
equivalent) may not be ideal. If a VM is used to host the database
server software, please consider a NAS or SAN solution for disk I/O.
Privileged Access Manager can leverage an existing database server cluster. Hitachi ID Systems
recommends a dedicated database server instance, however, for a number
- The data managed by Privileged Access Manager is extremely sensitive, so it is
desirable to minimize the number of DBAs who can access it (despite
use of encryption).
- MSSQL and Oracle have limited ability to isolate workloads between
database instances on the same server. This means that a burst of
activity from Privileged Access Manager (as happens during nightly auto-discovery)
would cause slow responses in other applications. Conversely, other
applications experiencing high DB load would slow down Privileged Access Manager.
- Privileged Access Manager already includes real-time, fault-tolerant, WAN-friendly,
encrypted database replication between application nodes, each with
its own back-end database. Use of an expensive DB server cluster
is neither required nor beneficial.
- Network Architecture:
How user PCs, servers, network devices, multiple, replicated Privileged Access Manager nodes and other elements interact on the network.
- Replicated Credential Vault:
Replicated storage of passwords to privileged accounts in multiple, physically distant, encrypted vaults.
- Included Connectors:
Systems on which Privileged Access Manager can discover accounts, randomize passwords and launch login sessions.
- Infrastructure Auto-discovery:
Automatically finding and classifying workstations, servers, applications and network devices as well as privileged accounts and services on each one.
- Non-target integrations:
Integrations between Privileged Access Manager and IT infrastructure where it may not be managing passwords or privileged access -- such as e-mail systems, incident management applications and more.
- Workflow Requests and Approvals:
Enabling users to request and approve one-off access to sensitive accounts.
- Concurrent Access to Accounts:
Limiting how many administrators can simultaneously manage a system and keeping administrators informed of one-anothers activity.
- Single Sign-on Mechanisms:
Options for connecting users to privileged accounts, through credential injection, trust manipulation and temporary group membership, all without displaying passwords from the vault.
- Server requirements:
Sizing, configuration and number of servers on which to deploy Privileged Access Manager.
Scaling to manage passwords across millions of devices.
- Emergency access:
Access to Privileged Accounts During Emergencies.
- Language Support:
A list of languages supported in the web portal.