This document provides guidelines for the recommended minimum hardware and software requirements to run PAM360 in your environment. You can use these baselines for your on-premises PAM360 installation. We have categorized the requirements based on the size of the organization where PAM360 is installed: Small, Medium, and Large.
Besides the standard system requirements (both hardware and software) listed in the upcoming sections, the following elements are essential for the proper functioning of the PAM360 server if you are planning to utilize PAM360’s account discovery and password reset provisions:
| Environment Size | Criteria | Processor | RAM | Hard Disk |
|---|---|---|---|---|
Small | Fewer than 1000 servers, 500 keys, and 500 users | Dual Core or above | 8GB |
|
Medium | Fewer than 5000 servers, 1000 keys, and 1000 users | Quad Core or above | 16GB |
|
Large | Larger than 5000 servers, 1000 keys, and 1000 users | Octa Core or above | 32GB |
|
Additional Details
For session recordings, the disk space requirement may vary based on usage levels. PAM360’s session recording files occupy a disc space of 1 MB/minute that excludes idle times. This way, administrators can calculate the space as per their usage.
Caution
If you have configured any High Availability model with an external database, the processor, RAM, and hard disk requirements for database remain the same as listed above for each environment size. However, for Application Scaling setups:
| Operating Systems | Web Interface and Database |
|---|---|
Windows
Linux
Note: In general, PAM360 goes well with any flavor of Linux and can also be run on VMs of the above operating systems. | Web InterfaceHTML client requires one of the following browsers** to be installed in the system:
** PAM360 is optimized for 1280 x 800 resolution and above. Database Requirement
|
The below table lists the set of all ports used by PAM360 for various functions.
| Port Name | Port Number | Purpose | Direction |
|---|---|---|---|
Web Client | 8282 | For PAM360 web application | Inbound |
SMTP | 25 | For sending emails between mail servers | Outbound |
SSH | Telnet | 22 | 23 | For Unix and network device management | Outbound |
RDP | 3389 | For remote desktop connections to Windows devices | Outbound |
WMI | 135, 139, 445 | For managing Windows services and devices | Outbound |
LDAP, LDAPS | 389, 636 | For standard and secure directory communication | Outbound |
REST API | 8282 | For application interactions through RESTful services | Inbound |
SSH API | 6622 | For secure shell API interactions | Inbound |
Session Gateway | 8283 | For remote desktop and SSH sessions through the web client or mobile application | Inbound |
PostgreSQL | MS SQL | 3456 | 1433 | For database operations between servers | Outbound |
Application Gateway | 8288, 8289 | For communication between the PAM360 Application Gateway and PAM360 | Outbound |
Private CA-OCSP Responder Server port | 8080 | OCSP responder endpoint for certificate status checking | Inbound |
Oracle | 1521 | For Oracle Database Servers communication | Outbound |
Sybase ASE | 5000 | For Sybase listener communication | Outbound |
PAM360 supports seven distinct user roles:
The term administrator in the registered version encompasses Privileged Administrators, Administrators, Cloud Administrator, and Password Administrators. Licensing restricts the total number of these administrators. However, there is no limitation on the number of Password Users and Password Auditors. For more details on PAM360 user roles, click here.