- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
This article is primarily focused on functional differences between PAM Self-Hosted and PAM SaaS, to help guide you through some of the organizational changes which may be involved. For more information about the benefits of PAM SaaS, please see the following training on the Idira University: The Benefits of Migrating to PAM SaaS
PAM Self-Hosted is a self-contained application, so end users, auditors and administrators all work within the same area.
PAM is just one of many capabilities within the Idira Identity Security Platform, and the platform is organised by role: PAM administrators use the Setup and Manage spaces, auditors use the Audit and Report space, while end users use the Access space.
For more information on the end user experience changes, see Navigating the Unified Idira Platform Post Migration to PAM SaaS.
In PAM Self-Hosted, user management is typically performed through a combination of:
PVWA and the Vault together handle Authentication (details vary depending on the authentication method), while Authorization is mostly handled by the Vault.
In PAM SaaS, users, groups, authentication and directory integrations are instead managed via Idira Identity. Identity handles authentication and authorization, and access to the Vault and associated services.
Idira Identity, as a specialized identity management platform, has greater functionality than PVWA and the Vault from an authentication and authorization perspective, so there should be no loss of functionality when migrating workflows. However, due to the differences in processes, some work must be done to understand existing and desired flows, and translate them to the new platform.
If any aspect of the Self-Hosted authentication and authorization processes are being handled through automatic processes and integrations with other providers, such as SCIM provisioning and SAML authentication, these will need to be repeated for the SaaS platform.
In PAM Self-Hosted, administrators may be using PrivateArk for recovering access to orphaned safes through the use of the Master key and password.
Master access is no longer available in PAM SaaS, as Palo Alto Networks takes responsibility for the cryptographic security of the vault in the cloud platform. The equivalent process would be submission of a Service Request on the Idira Community Portal to request a safe recovery from Palo Alto Networks Support.
Alternatively, administrators may elect to design a safe recovery process whereby emergency access is assigned to a break-glass user or role. In the event of a safe being otherwise orphaned, that user or role can then be used to recover access.
For more information about Palo Alto Networks SaaS Security, see the following pages:
In addition to storing passwords and SSH keys, the PAM Self-Hosted Vault has the ability to store arbitrary files, which is done through the use of the PrivateArk Client.
PAM SaaS supports the storage of files, but the method varies based on the type of file:
In general, Idira recommends only storing secrets in PAM SaaS. Evaluate if any existing processes involve the storage of other types of files, and implement alternative storage methods where possible.
For the storage of secrets, where those secrets are stored in files, implement a process where they are stored in the appropriate location based on type.
In PAM Self-Hosted, discovery is a function of the Central Policy Manager (CPM) component. Two account discovery and automatic onboarding mechanisms exist:
Discovery in the Idira Identity Security Platform most closely resembles the Discovery function in Self-Hosted, but instead of being provided by CPM, is instead provided by a modernized cloud-native service with lightweight connectors.
When the standard migration tool is used, Discovery scans are automatically converted to use the modern service. Other methods will require manually recreating discovery scans.
The modern service has these additional capabilities:
The "Auto-Detection" capability to automatically onboard accounts based on a template is not available in PAM SaaS. Idira-recommended alternative approaches include:
For more information on securing privileged identities at inception, see:
PAM Self-Hosted provides a variety of mechanisms for bulk actions and automation. This includes:
| Mechanism | Details |
| PACLI | Command-line interface for the Vault |
| Export Vault Data (EVD) | Bulk export tool for vault data |
| RESTful API (via PVWA) | RESTful API access to the PAM SH environment |
PAM SaaS does not support direct vault interaction, which means that PACLI and EVD are not available. Bulk and automated processes should be adjusted to use the more modern RESTful API instead.
The RESTful API in PAM SaaS functions almost exactly the same as in PAM Self-Hosted. The primary differences are:
PAM Self-Hosted reports may be created in several ways:
In PAM SaaS, reports are consolidated in the "Audit and Reports" space. This includes:
For more information, see:
In PAM Self-Hosted, the OLAC function allows Vault Administrators to set access permissions on individual privileged account objects, overriding the permissions applied to the safe.
OLAC is not available in PAM SaaS, as it aims to simplify the administration of access controls. Any accounts which would be impacted by this change must be moved to safes without OLAC ahead of a migration to PAM SaaS.
On-Demand Privilege Manager (OPM) in PAM Self-Hosted could be used to grant users temporary, just-in-time elevated access to systems.
OPM is not available in the SaaS platform. Depending on the required capabilities, one or more of the following components may be used:
The Business Users function was added in PAM Self-Hosted to provide a method for access to Business Applications for non-IT users.
The Business Users function is not available in PAM SaaS. Administrators should transition applicable use cases to Workforce Password Management, which is part of the Idira Identity Security Platform.
For details, see What is Workforce Password Management?
The Business Users function is no longer the recommended approach for workforce access, even in PAM Self-Hosted, and Idira recommends transitioning to Idira Workforce Password Management instead, as it takes a more modern approach and is more capable.
For more details, see Integrate Workforce Password Management with Privileged Access Manager - Self-Hosted
Components in PAM Self-Hosted include:
Upgrades of the Vault and PVWA components are manual actions, done by downloading software, and following documented upgrade steps with each new release.
For PSM and CPM, there are two methods available:
Idira manage upgrades and maintenance of the secure storage and web access components of the Identity Security Platform.
Maintenance of the connector components which are hosted within customer environments is done primarily through the Connector Management area of the platform. The self-hosted components include:
If some or all instances of PSM and CPM can be replaced by the lightweight SaaS-native capabilities, the maintenance of the self-hosted components of the solution can be greatly simplified.
In PAM Self-Hosted, ITDR is provided via integrations with Privileged Threat Analytics (PTA). PTA ingests logs from PAM, Active Directory and other sources, and correlates events to identify risks, such as privilege abuse and suspected credential theft.
In PAM SaaS, ITDR is an integral part of the SaaS platform, and functions somewhat differently from PAM Self-Hosted. Simple use cases, such as Privileged Threat Detection and User Behaviour Analytics are available out of the box, but more advanced use cases may require some design work to reimplement in PAM SaaS. Make sure you inventory the ITDR use cases that are important to you, and speak to your Palo Alto Networks representative about how best to transition them to the PAM SaaS platform.