PAM360 Application Gateway

Organizations often operate in complex IT infrastructures spanning multiple locations, secure subnets, diverse platforms, and isolated networks. Managing privileged resources across these varied environments can be challenging when those resources are not directly connected to the network where the PAM360 server is hosted. The PAM360 Application Gateway addresses this challenge, serving as a secure intermediary between the PAM360 server and remote resources, enabling seamless privileged resource management across environments. Whether the resources are deployed in diverse geographical locations, within secure subnets and DMZs, or in isolated networks managed by a service gateway, the Application Gateway ensures that privileged access management remains efficient and secure. It also facilitates cross-platform management by bridging Linux-hosted PAM360 servers with Windows-based resources.

This document explains how the PAM360 Application Gateway enables secure and efficient privileged resource management across distributed IT environments. It covers the gateway's setup, communication workflow with the PAM360 server, supported operations, and how tasks are securely handled, helping administrators manage resources effectively in segmented networks.

1. Overview
2. Supported Operations via Application Gateway
3. Communication Between Application Gateway and PAM360
4. Limitations

1. Overview

The PAM360 Application Gateway is a service designed to run on either Windows or Linux machines. It is specifically designed to execute key resource and password management operations, such as resource discovery, account discovery, password verification, and password reset for privileged resources not directly connected to the network where the PAM360 server is hosted, and facilitate privileged remote connections to remote resources managed via Application Gateways. Currently, RDP, SSH, and VNC sessions are supported. The Application Gateway allows organizations to manage and secure resources across various isolated or segmented networks, ensuring seamless administration despite network constraints.

After deploying an Application Gateway within a secure, isolated, or private network, you can discover the privileged resources and associated accounts that are otherwise inaccessible from the PAM360 server. Post discovery, these privileged resources are added to the PAM360 inventory, where administrators can associate them with the desired Application Gateway in bulk from the PAM360 Application Gateway window for streamlined resource management.

Once the resources are associated with an Application Gateway, any password management operations, such as password verification or reset triggered from the PAM360 interface, are executed by the corresponding Application Gateway to which the selected resources are associated. This comprehensive approach allows for secure and efficient management of privileged resources and accounts across isolated or segmented networks.

2. Supported Operations via Application Gateway

This section covers the list of operations supported by PAM360 via the Application Gateways.

2.1 Resource Discovery

PAM360 supports privileged resource discovery via the Application Gateway, enabling the discovery of privileged resources within networks not directly connected to the PAM360 server. With this capability, PAM360 can seamlessly identify Linux endpoints, VMware instances, and network devices in the environment that are part of isolated or secure subnets and discover the associated privileged accounts. Explore the relevant help documents for more details about discovering privileged resources and the associated accounts via the PAM360 Application Gateway.

2.2 Account Discovery

Once the privileged resources within your environment are successfully onboarded into the PAM360 inventory, you can proceed with the discovery of the privileged accounts associated with those IT assets. PAM360 supports privileged account discovery via the Application Gateway for Windows, Linux, macOS, VMware devices, database servers, network devices, and privileged accounts associated with any SSH-based devices. Additionally, PAM360 supports the discovery of Service Accounts, Scheduled Tasks, IIS AppPools, and IIS Web.config Credentials via the Application Gateway.

Similarly, PAM360 supports periodic discovery of privileged accounts through schedules via the Application Gateways to discover and add the newly added privileged accounts to the privileged resources in your environment into the PAM360 repository. Explore the provided links for more details about the privileged accounts discovery and periodic discovery of privileged accounts in PAM360.

2.3 Password Management Operations

PAM360 supports various password management operations via the Application Gateway for Windows, Linux, macOS, VMware devices, database servers, network devices, and privileged accounts associated with any SSH-based devices, as well as Service Accounts, Scheduled Tasks, IIS AppPools, and IIS Web.config credentials. The supported password management operations are as listed below:

1. Password Verification - PAM360 supports password verification through the Application Gateway to verify the integrity of passwords for resources configured with remote password reset settings. This process ensures that the stored password in PAM360 matches the actual password on the target resource, maintaining data consistency and preventing access issues.
2. Password Reset - PAM360 provides the option to remotely change the passwords via the Application Gateway for the devices accessible via the command-line interface (CLI) and support remote password reset operations. Administrators can view the task status on the Application Gateway Task Monitor window and the Resource Audits page. Explore this link for more details about the remote password reset functionality in PAM360.
3. Periodic Password Integrity Check - To ensure that the stored passwords in PAM360 remain consistent with the actual passwords on target devices, PAM360 supports periodic integrity checks through schedules via the Application Gateway.
4. Periodic Password Reset Schedule - PAM360 allows the administrators to schedule password reset operations for the privileged resources in their environment via the Application Gateway. The Application Gateway executes the scheduled password reset operation and updates the status on the Application Gateway Task Monitor window. You can also track the changes on the Resource Audits page. Explore this link for more details about periodic password reset in PAM360.

2.4 Remote Connections

PAM360 provides comprehensive support for establishing remote sessions to privileged resources in your environment that are managed through Application Gateways. Currently, only RDP, SSH, and VNC connections are supported. Additionally, PAM360 offers the flexibility to configure a landing server to tunnel the remote session launched to privileged resources managed by the Application Gateway servers.

3. Communication Between Application Gateway and PAM360

The Application Gateway communicates with the PAM360 server over port 8288, sending a ping every 5 seconds to maintain a continuous connection. This periodic communication enables PAM360 to monitor the status of the Application Gateway in real-time. On the PAM360 Application Gateway page, the status is shown as either Active or Inactive, allowing administrators to verify its availability and operational state.

When a user initiates an operation, such as password verification or reset, for a resource associated with an Application Gateway, PAM360 notifies the Application Gateway about the task through a secure encrypted channel. The Application Gateway executes the task and notifies the PAM360 server about the status, thereby facilitating seamless task handling and accurate tracking within the environment. All the communication between the PAM360 server and the Application Gateways occurs through a secure encrypted channel.

If the Application Gateway is down or there is a connectivity issue between PAM360 and the Application Gateway at the time of task execution, the task is placed in a queue for up to 3 minutes on the PAM360 server. If the Application Gateway remains unreachable beyond the 3-minute window, the task is marked as failed, and its status is updated on the Application Gateway Task Monitor window and the Resource Audits page.

4. Limitations

• Resources managed via agents or landing servers cannot be associated with an Application Gateway.
• Application Gateway mapping will not be retained when a resource is duplicated.
• IPv6 addresses are not supported during Application Gateway configurations.
• Adding or editing Application Gateways is restricted on secondary servers, read-only servers, and sub-nodes. However, resources can still be mapped to available Application Gateways from these servers.
• In environments configured with the Application Scaling setup, PAM360 does not support privileged remote sessions to devices managed through the Application Gateway when the session is initiated from a subnode, regardless of whether the main node is active or inactive.