<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Differences in solution approaches between PAM Self-Hosted and PAM SaaS in PAM SaaS Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-saas-articles/differences-in-solution-approaches-between-pam-self-hosted-and/ta-p/1427196</link>
    <description>&lt;H2&gt;Benefits of PAM SaaS&lt;/H2&gt;
&lt;P&gt;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&amp;nbsp;University:&amp;nbsp;&lt;A href="https://training.cyberark.com/learn/courses/1291/the-benefits-of-migrating-to-pam-saas" rel="noopener noreferrer" target="_blank"&gt;The Benefits of Migrating to PAM SaaS&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;Platform Navigation&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted&lt;/H3&gt;
&lt;P&gt;PAM Self-Hosted is a self-contained application, so end users, auditors and administrators all work within the same area.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;For more information on the end user experience changes, see &lt;A href="https://community.cyberark.com/s/article/Navigating-the-Unified-Idira-Platform-Post-Migration-to-PAM-SaaS" rel="noopener noreferrer" target="_blank"&gt;Navigating the Unified Idira Platform Post Migration to PAM SaaS&lt;/A&gt;.&lt;/P&gt;
&lt;H2&gt;User Management and Access Control&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;In PAM Self-Hosted, user management is typically performed through a combination of:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Use of the PrivateArk Client, for internal Vault users, and&lt;/LI&gt;&lt;LI&gt;Managing users and groups in an integrated directory, e.g. Active Directory&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;PVWA and the Vault together handle Authentication (details vary depending on the authentication method), while Authorization is mostly handled by the Vault.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;In PAM SaaS, users, groups, authentication and directory integrations are instead managed via Idira&amp;nbsp;Identity. Identity handles authentication and authorization, and access to the Vault and associated services.&lt;/P&gt;
&lt;P&gt;Idira&amp;nbsp;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.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H2&gt;Safe Recovery via Master Access&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;In PAM Self-Hosted, administrators may be using PrivateArk for recovering access to orphaned safes through the use of the Master key and password.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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&amp;nbsp;&lt;A href="https://community.cyberark.com/" target="_self"&gt;Idira Community Portal&lt;/A&gt; to request a safe recovery from Palo Alto Networks Support.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;For more information about Palo Alto Networks SaaS Security, see the following pages:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;&lt;A href="https://trust.cyberark.com/" target="_self"&gt;Idira Trust Center&lt;/A&gt; - Idira security and compliance reports and certifications&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://www.paloaltonetworks.com/legal/idira/privacy-and-data-protection-faqs" rel="noopener noreferrer" target="_blank"&gt;Privacy and Data Protection FAQs&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;File Storage&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;PAM SaaS supports the storage of files, but the method varies based on the type of file:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;SSH Keys and Certificates can be stored in Safes within the Vault
&lt;UL&gt;&lt;LI&gt;SSH Keys: &lt;A href="https://docs.cyberark.com/manage/latest/en/content/privilege-cloud/pasimp/plugin-ssh.htm" target="_self"&gt;SSH Keys | Idira Docs&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;The Certificates platform can be found on the Idira Marketplace&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;Other types of secret files can be attached to secrets within the Workforce Password Management solution
&lt;UL&gt;&lt;LI&gt;See: &lt;A href="https://docs.cyberark.com/wpm/latest/en/content/securestorage/manage-secured-items.htm#Attachafiletoasecureditem" target="_self"&gt;Manage secured items&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H2&gt;Account Discovery&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;In PAM Self-Hosted, discovery is a function of the Central Policy Manager (CPM) component. Two account discovery and automatic onboarding mechanisms exist:&lt;/P&gt;
&lt;OL&gt;&lt;LI&gt;The CPM Auto-Detection function in Self-Hosted provides the ability to scan systems, and onboard accounts using a specified template, on the assumption that user will exist on the identified system.&lt;/LI&gt;&lt;LI&gt;The Discovery function actively scans discovered systems for accounts, and separates the process into two stages: Discovery, which adds accounts to a queue for review, and onboarding, which may be manual or automatic.&lt;/LI&gt;&lt;/OL&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;The modern service has these additional capabilities:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Support for additional platforms&lt;/LI&gt;&lt;LI&gt;Automatic or supervised Offboarding of deleted accounts&lt;/LI&gt;&lt;LI&gt;Integration with Cora AI for on/off-boarding guidance&lt;/LI&gt;&lt;LI&gt;Integration with Risk Management to help with prioritization&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;The "Auto-Detection" capability to automatically onboard accounts based on a template is not available in PAM SaaS. Idira-recommended alternative approaches include:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Integrate PAM with system provisioning and deprovisioning flows to onboard accounts at creation/deletion,&lt;/LI&gt;&lt;LI&gt;Use discovery to find and onboard only accounts which are actually confirmed to exist,&lt;/LI&gt;&lt;LI&gt;Create an external discovery function which uses the REST API to insert discovered systems and accounts into Idira, and/or&lt;/LI&gt;&lt;LI&gt;Implement a Vulnerability Scanning system which discovers systems and accounts and integrates with Idira ISP.&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;For more information on securing privileged identities at inception, see:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;&lt;A href="https://community.cyberark.com/s/article/Securing-Privileged-Accounts-at-Inception-with-Automation-and-REST-APIs" rel="noopener noreferrer" target="_blank"&gt;Securing Privileged Accounts at Inception with Automation and REST APIs&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.cyberark.com/cyberark-blueprint/latest/en/content/operationalize-identity-security.htm" rel="noopener noreferrer" target="_blank"&gt;Operationalize identity security | Idira Docs&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Bulk Actions and Automation&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;PAM Self-Hosted provides a variety of mechanisms for bulk actions and automation. This includes:&lt;/P&gt;
&lt;TABLE border="1" style="width: 100%;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1" style="width: 33.3745%;" valign="top"&gt;Mechanism&lt;/TD&gt;&lt;TD colspan="1" rowspan="1" style="width: 66.6255%;" valign="top"&gt;Details&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1" style="width: 33.3745%;" valign="top"&gt;PACLI&lt;/TD&gt;&lt;TD colspan="1" rowspan="1" style="width: 66.6255%;" valign="top"&gt;Command-line interface for the Vault&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1" style="width: 33.3745%;" valign="top"&gt;Export Vault Data (EVD)&lt;/TD&gt;&lt;TD colspan="1" rowspan="1" style="width: 66.6255%;" valign="top"&gt;Bulk export tool for vault data&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1" style="width: 33.3745%;" valign="top"&gt;RESTful API (via PVWA)&lt;/TD&gt;&lt;TD colspan="1" rowspan="1" style="width: 66.6255%;" valign="top"&gt;RESTful API access to the PAM SH environment&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;The RESTful API in PAM SaaS functions almost exactly the same as in PAM Self-Hosted. The primary differences are:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Authentication, and the nature of the resulting authentication token, are different
&lt;UL&gt;&lt;LI&gt;Documentation: &lt;A href="https://api-docs.cyberark.com/create-api-token/docs/create-api-token" target="_self"&gt;API Authentication for Idira Identity Security Platform Shared Services&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;When assigning safe memberships, the “memberType” parameter was optional in PAM Self-Hosted, but is mandatory in PAM SaaS
&lt;UL&gt;&lt;LI&gt;Documentation: &lt;A href="https://docs.cyberark.com/manage/latest/en/content/privilege-cloud/webservices/add%20safe%20member.htm" target="_self"&gt;Add Safe member&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;As the Discovery function in PAM SaaS has been moved to a modern SaaS service, the associated APIs are different:
&lt;UL&gt;&lt;LI&gt;Documentation: &lt;A href="https://docs.cyberark.com/manage/latest/en/content/discovery/discovery-apis/discovery-account-discovery.htm" target="_self"&gt;Account discovery APIs&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;User management is done through Identity
&lt;UL&gt;&lt;LI&gt;Documentation: &lt;A href="https://api-docs.cyberark.com/identity-docs-api/docs/identity-apis" rel="noopener noreferrer" target="_blank"&gt;Idira Identity API Documentation&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;There are many additional services available on the platform which can be managed via APIs&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Reporting&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;PAM Self-Hosted reports may be created in several ways:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;The Activity Log, Compliance, Inventory and Entitlement reports built into PasswordVault Web Access (PVWA)&lt;/LI&gt;&lt;LI&gt;PAS Reporter – a legacy tool which generates summary reports&lt;/LI&gt;&lt;LI&gt;Export Vault Data (EVD) – a legacy tool which exports a variety of vault data for reporting or other purposes&lt;/LI&gt;&lt;/UL&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;In PAM SaaS, reports are consolidated in the "Audit and Reports" space. This includes:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Users and roles&lt;/LI&gt;&lt;LI&gt;Privileged account inventories and compliance&lt;/LI&gt;&lt;LI&gt;Entitlements&lt;/LI&gt;&lt;LI&gt;Activities&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;For more information, see:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.cyberark.com/privilege-cloud-secrets-rotation/latest/en/content/privilege%20cloud/privcloud-reports-lp.htm" rel="noopener noreferrer" target="_blank"&gt;&lt;/A&gt;&lt;A href="https://docs.cyberark.com/audit-and-reports/latest/en/content/audit/audit-reports-main.htm" rel="noopener noreferrer" target="_blank"&gt;Workforce reports and activity logs&lt;/A&gt;&lt;A href="https://docs.cyberark.com/privilege-cloud-secrets-rotation/latest/en/content/privilege%20cloud/privcloud-reports-lp.htm" rel="noopener noreferrer" target="_blank"&gt;&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.cyberark.com/privilege-cloud-secrets-rotation/latest/en/content/privilege%20cloud/privcloud-reports-lp.htm" rel="noopener noreferrer" target="_blank"&gt;Privilege reports&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Object-Level Access Control (OLAC)&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H2&gt;On-Demand Privilege Manager&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;On-Demand Privilege Manager (OPM) in PAM Self-Hosted could be used to grant users temporary, just-in-time elevated access to systems.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;OPM is not available in the SaaS platform. Depending on the required capabilities, one or more of the following components may be used:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Endpoint Privilege Manager
&lt;UL&gt;&lt;LI&gt;Provides centralised, granular, per-command privileged access control&lt;/LI&gt;&lt;LI&gt;May be used in combination with Secure Infrastructure Access (below) to combine privileged command security with JIT access flows&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;Secure Infrastructure Access (SIA)
&lt;UL&gt;&lt;LI&gt;With Zero Standing Privileges (ZSP), privileged access can be granted to users on-demand and only for as long as they need it, removing all standing access.&lt;/LI&gt;&lt;LI&gt;With Just-in-Time (JIT) Elevation, users have limited standing access to systems. Permissions are elevated on-demand for the completion of specific tasks, and removed afterwards.&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Business Users&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;The Business Users function was added in PAM Self-Hosted to provide a method for access to Business Applications for non-IT users.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;For details, see&amp;nbsp;&lt;A href="https://docs.cyberark.com/wpm/latest/en/content/getstarted/welcome-to-wpm.htm" target="_self"&gt;What is Workforce Password Management?&lt;/A&gt;&lt;/P&gt;
&lt;H3&gt;Additional Note&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;For more details, see&amp;nbsp;&lt;A href="https://docs.cyberark.com/manage/latest/en/content/identity/applications/wpm/pas-passwords.htm" target="_self"&gt;Integrate Workforce Password Management with Privileged Access Manager - Self-Hosted&lt;/A&gt;&lt;/P&gt;
&lt;H2&gt;Component Management&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted&lt;/H3&gt;
&lt;P&gt;Components in PAM Self-Hosted include:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;PrivateArk Server (Vault for secure storage)&lt;/LI&gt;&lt;LI&gt;PasswordVault Web Access (PVWA for web access)&lt;/LI&gt;&lt;LI&gt;Central Policy Manager / Password Manager (CPM for password management)&lt;/LI&gt;&lt;LI&gt;Privileged Session Manager (PSM for privileged session isolation and management)&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Upgrades of the Vault and PVWA components are manual actions, done by downloading software, and following documented upgrade steps with each new release.&lt;/P&gt;
&lt;P&gt;For PSM and CPM, there are two methods available:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;As with the previously mentioned components, software can be downloaded and installed manually directly on the server, or&lt;/LI&gt;&lt;LI&gt;The Connector Management SaaS service can be used to automate most of the upgrade process.&lt;/LI&gt;&lt;/UL&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;Idira manage upgrades and maintenance of the secure storage and web access components of the Identity Security Platform.&lt;/P&gt;
&lt;P&gt;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:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Connector Management Agent, which provides
&lt;UL&gt;&lt;LI&gt;Upgrades of PSM and CPM (as relevant)&lt;/LI&gt;&lt;LI&gt;Discovery scanning&lt;/LI&gt;&lt;LI&gt;Secrets Rotation Service (if tenant uses SRS for password management instead of CPM)&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;Secure Infrastructure Access (SIA) for privileged session isolation and monitoring&lt;/LI&gt;&lt;LI&gt;PSM (Optional, if required to deliver use cases not covered by SIA)&lt;/LI&gt;&lt;LI&gt;CPM (if the tenant uses CPM for password management, and not SRS)&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H2&gt;Identity Threat Detection and Response&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H3&gt;PAM SaaS&amp;nbsp;Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Thu, 05 Nov 2026 19:42:38 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-11-05T19:42:38Z</dc:date>
    <item>
      <title>Differences in solution approaches between PAM Self-Hosted and PAM SaaS</title>
      <link>https://live.paloaltonetworks.com/t5/pam-saas-articles/differences-in-solution-approaches-between-pam-self-hosted-and/ta-p/1427196</link>
      <description>&lt;H2&gt;Benefits of PAM SaaS&lt;/H2&gt;
&lt;P&gt;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&amp;nbsp;University:&amp;nbsp;&lt;A href="https://training.cyberark.com/learn/courses/1291/the-benefits-of-migrating-to-pam-saas" rel="noopener noreferrer" target="_blank"&gt;The Benefits of Migrating to PAM SaaS&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;Platform Navigation&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted&lt;/H3&gt;
&lt;P&gt;PAM Self-Hosted is a self-contained application, so end users, auditors and administrators all work within the same area.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;For more information on the end user experience changes, see &lt;A href="https://community.cyberark.com/s/article/Navigating-the-Unified-Idira-Platform-Post-Migration-to-PAM-SaaS" rel="noopener noreferrer" target="_blank"&gt;Navigating the Unified Idira Platform Post Migration to PAM SaaS&lt;/A&gt;.&lt;/P&gt;
&lt;H2&gt;User Management and Access Control&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;In PAM Self-Hosted, user management is typically performed through a combination of:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Use of the PrivateArk Client, for internal Vault users, and&lt;/LI&gt;&lt;LI&gt;Managing users and groups in an integrated directory, e.g. Active Directory&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;PVWA and the Vault together handle Authentication (details vary depending on the authentication method), while Authorization is mostly handled by the Vault.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;In PAM SaaS, users, groups, authentication and directory integrations are instead managed via Idira&amp;nbsp;Identity. Identity handles authentication and authorization, and access to the Vault and associated services.&lt;/P&gt;
&lt;P&gt;Idira&amp;nbsp;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.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H2&gt;Safe Recovery via Master Access&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;In PAM Self-Hosted, administrators may be using PrivateArk for recovering access to orphaned safes through the use of the Master key and password.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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&amp;nbsp;&lt;A href="https://community.cyberark.com/" target="_self"&gt;Idira Community Portal&lt;/A&gt; to request a safe recovery from Palo Alto Networks Support.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;For more information about Palo Alto Networks SaaS Security, see the following pages:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;&lt;A href="https://trust.cyberark.com/" target="_self"&gt;Idira Trust Center&lt;/A&gt; - Idira security and compliance reports and certifications&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://www.paloaltonetworks.com/legal/idira/privacy-and-data-protection-faqs" rel="noopener noreferrer" target="_blank"&gt;Privacy and Data Protection FAQs&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;File Storage&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;PAM SaaS supports the storage of files, but the method varies based on the type of file:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;SSH Keys and Certificates can be stored in Safes within the Vault
&lt;UL&gt;&lt;LI&gt;SSH Keys: &lt;A href="https://docs.cyberark.com/manage/latest/en/content/privilege-cloud/pasimp/plugin-ssh.htm" target="_self"&gt;SSH Keys | Idira Docs&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;The Certificates platform can be found on the Idira Marketplace&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;Other types of secret files can be attached to secrets within the Workforce Password Management solution
&lt;UL&gt;&lt;LI&gt;See: &lt;A href="https://docs.cyberark.com/wpm/latest/en/content/securestorage/manage-secured-items.htm#Attachafiletoasecureditem" target="_self"&gt;Manage secured items&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H2&gt;Account Discovery&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;In PAM Self-Hosted, discovery is a function of the Central Policy Manager (CPM) component. Two account discovery and automatic onboarding mechanisms exist:&lt;/P&gt;
&lt;OL&gt;&lt;LI&gt;The CPM Auto-Detection function in Self-Hosted provides the ability to scan systems, and onboard accounts using a specified template, on the assumption that user will exist on the identified system.&lt;/LI&gt;&lt;LI&gt;The Discovery function actively scans discovered systems for accounts, and separates the process into two stages: Discovery, which adds accounts to a queue for review, and onboarding, which may be manual or automatic.&lt;/LI&gt;&lt;/OL&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;The modern service has these additional capabilities:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Support for additional platforms&lt;/LI&gt;&lt;LI&gt;Automatic or supervised Offboarding of deleted accounts&lt;/LI&gt;&lt;LI&gt;Integration with Cora AI for on/off-boarding guidance&lt;/LI&gt;&lt;LI&gt;Integration with Risk Management to help with prioritization&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;The "Auto-Detection" capability to automatically onboard accounts based on a template is not available in PAM SaaS. Idira-recommended alternative approaches include:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Integrate PAM with system provisioning and deprovisioning flows to onboard accounts at creation/deletion,&lt;/LI&gt;&lt;LI&gt;Use discovery to find and onboard only accounts which are actually confirmed to exist,&lt;/LI&gt;&lt;LI&gt;Create an external discovery function which uses the REST API to insert discovered systems and accounts into Idira, and/or&lt;/LI&gt;&lt;LI&gt;Implement a Vulnerability Scanning system which discovers systems and accounts and integrates with Idira ISP.&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;For more information on securing privileged identities at inception, see:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;&lt;A href="https://community.cyberark.com/s/article/Securing-Privileged-Accounts-at-Inception-with-Automation-and-REST-APIs" rel="noopener noreferrer" target="_blank"&gt;Securing Privileged Accounts at Inception with Automation and REST APIs&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.cyberark.com/cyberark-blueprint/latest/en/content/operationalize-identity-security.htm" rel="noopener noreferrer" target="_blank"&gt;Operationalize identity security | Idira Docs&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Bulk Actions and Automation&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;PAM Self-Hosted provides a variety of mechanisms for bulk actions and automation. This includes:&lt;/P&gt;
&lt;TABLE border="1" style="width: 100%;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1" style="width: 33.3745%;" valign="top"&gt;Mechanism&lt;/TD&gt;&lt;TD colspan="1" rowspan="1" style="width: 66.6255%;" valign="top"&gt;Details&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1" style="width: 33.3745%;" valign="top"&gt;PACLI&lt;/TD&gt;&lt;TD colspan="1" rowspan="1" style="width: 66.6255%;" valign="top"&gt;Command-line interface for the Vault&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1" style="width: 33.3745%;" valign="top"&gt;Export Vault Data (EVD)&lt;/TD&gt;&lt;TD colspan="1" rowspan="1" style="width: 66.6255%;" valign="top"&gt;Bulk export tool for vault data&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1" style="width: 33.3745%;" valign="top"&gt;RESTful API (via PVWA)&lt;/TD&gt;&lt;TD colspan="1" rowspan="1" style="width: 66.6255%;" valign="top"&gt;RESTful API access to the PAM SH environment&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;The RESTful API in PAM SaaS functions almost exactly the same as in PAM Self-Hosted. The primary differences are:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Authentication, and the nature of the resulting authentication token, are different
&lt;UL&gt;&lt;LI&gt;Documentation: &lt;A href="https://api-docs.cyberark.com/create-api-token/docs/create-api-token" target="_self"&gt;API Authentication for Idira Identity Security Platform Shared Services&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;When assigning safe memberships, the “memberType” parameter was optional in PAM Self-Hosted, but is mandatory in PAM SaaS
&lt;UL&gt;&lt;LI&gt;Documentation: &lt;A href="https://docs.cyberark.com/manage/latest/en/content/privilege-cloud/webservices/add%20safe%20member.htm" target="_self"&gt;Add Safe member&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;As the Discovery function in PAM SaaS has been moved to a modern SaaS service, the associated APIs are different:
&lt;UL&gt;&lt;LI&gt;Documentation: &lt;A href="https://docs.cyberark.com/manage/latest/en/content/discovery/discovery-apis/discovery-account-discovery.htm" target="_self"&gt;Account discovery APIs&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;User management is done through Identity
&lt;UL&gt;&lt;LI&gt;Documentation: &lt;A href="https://api-docs.cyberark.com/identity-docs-api/docs/identity-apis" rel="noopener noreferrer" target="_blank"&gt;Idira Identity API Documentation&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;There are many additional services available on the platform which can be managed via APIs&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Reporting&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;PAM Self-Hosted reports may be created in several ways:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;The Activity Log, Compliance, Inventory and Entitlement reports built into PasswordVault Web Access (PVWA)&lt;/LI&gt;&lt;LI&gt;PAS Reporter – a legacy tool which generates summary reports&lt;/LI&gt;&lt;LI&gt;Export Vault Data (EVD) – a legacy tool which exports a variety of vault data for reporting or other purposes&lt;/LI&gt;&lt;/UL&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;In PAM SaaS, reports are consolidated in the "Audit and Reports" space. This includes:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Users and roles&lt;/LI&gt;&lt;LI&gt;Privileged account inventories and compliance&lt;/LI&gt;&lt;LI&gt;Entitlements&lt;/LI&gt;&lt;LI&gt;Activities&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;For more information, see:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.cyberark.com/privilege-cloud-secrets-rotation/latest/en/content/privilege%20cloud/privcloud-reports-lp.htm" rel="noopener noreferrer" target="_blank"&gt;&lt;/A&gt;&lt;A href="https://docs.cyberark.com/audit-and-reports/latest/en/content/audit/audit-reports-main.htm" rel="noopener noreferrer" target="_blank"&gt;Workforce reports and activity logs&lt;/A&gt;&lt;A href="https://docs.cyberark.com/privilege-cloud-secrets-rotation/latest/en/content/privilege%20cloud/privcloud-reports-lp.htm" rel="noopener noreferrer" target="_blank"&gt;&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.cyberark.com/privilege-cloud-secrets-rotation/latest/en/content/privilege%20cloud/privcloud-reports-lp.htm" rel="noopener noreferrer" target="_blank"&gt;Privilege reports&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Object-Level Access Control (OLAC)&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H2&gt;On-Demand Privilege Manager&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;On-Demand Privilege Manager (OPM) in PAM Self-Hosted could be used to grant users temporary, just-in-time elevated access to systems.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;OPM is not available in the SaaS platform. Depending on the required capabilities, one or more of the following components may be used:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Endpoint Privilege Manager
&lt;UL&gt;&lt;LI&gt;Provides centralised, granular, per-command privileged access control&lt;/LI&gt;&lt;LI&gt;May be used in combination with Secure Infrastructure Access (below) to combine privileged command security with JIT access flows&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;Secure Infrastructure Access (SIA)
&lt;UL&gt;&lt;LI&gt;With Zero Standing Privileges (ZSP), privileged access can be granted to users on-demand and only for as long as they need it, removing all standing access.&lt;/LI&gt;&lt;LI&gt;With Just-in-Time (JIT) Elevation, users have limited standing access to systems. Permissions are elevated on-demand for the completion of specific tasks, and removed afterwards.&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Business Users&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted Function&lt;/H3&gt;
&lt;P&gt;The Business Users function was added in PAM Self-Hosted to provide a method for access to Business Applications for non-IT users.&lt;/P&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;For details, see&amp;nbsp;&lt;A href="https://docs.cyberark.com/wpm/latest/en/content/getstarted/welcome-to-wpm.htm" target="_self"&gt;What is Workforce Password Management?&lt;/A&gt;&lt;/P&gt;
&lt;H3&gt;Additional Note&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;For more details, see&amp;nbsp;&lt;A href="https://docs.cyberark.com/manage/latest/en/content/identity/applications/wpm/pas-passwords.htm" target="_self"&gt;Integrate Workforce Password Management with Privileged Access Manager - Self-Hosted&lt;/A&gt;&lt;/P&gt;
&lt;H2&gt;Component Management&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted&lt;/H3&gt;
&lt;P&gt;Components in PAM Self-Hosted include:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;PrivateArk Server (Vault for secure storage)&lt;/LI&gt;&lt;LI&gt;PasswordVault Web Access (PVWA for web access)&lt;/LI&gt;&lt;LI&gt;Central Policy Manager / Password Manager (CPM for password management)&lt;/LI&gt;&lt;LI&gt;Privileged Session Manager (PSM for privileged session isolation and management)&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Upgrades of the Vault and PVWA components are manual actions, done by downloading software, and following documented upgrade steps with each new release.&lt;/P&gt;
&lt;P&gt;For PSM and CPM, there are two methods available:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;As with the previously mentioned components, software can be downloaded and installed manually directly on the server, or&lt;/LI&gt;&lt;LI&gt;The Connector Management SaaS service can be used to automate most of the upgrade process.&lt;/LI&gt;&lt;/UL&gt;
&lt;H3&gt;PAM SaaS Approach&lt;/H3&gt;
&lt;P&gt;Idira manage upgrades and maintenance of the secure storage and web access components of the Identity Security Platform.&lt;/P&gt;
&lt;P&gt;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:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Connector Management Agent, which provides
&lt;UL&gt;&lt;LI&gt;Upgrades of PSM and CPM (as relevant)&lt;/LI&gt;&lt;LI&gt;Discovery scanning&lt;/LI&gt;&lt;LI&gt;Secrets Rotation Service (if tenant uses SRS for password management instead of CPM)&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI&gt;Secure Infrastructure Access (SIA) for privileged session isolation and monitoring&lt;/LI&gt;&lt;LI&gt;PSM (Optional, if required to deliver use cases not covered by SIA)&lt;/LI&gt;&lt;LI&gt;CPM (if the tenant uses CPM for password management, and not SRS)&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H2&gt;Identity Threat Detection and Response&lt;/H2&gt;
&lt;H3&gt;PAM Self-Hosted&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H3&gt;PAM SaaS&amp;nbsp;Approach&lt;/H3&gt;
&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2026 19:42:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-saas-articles/differences-in-solution-approaches-between-pam-self-hosted-and/ta-p/1427196</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-11-05T19:42:38Z</dc:date>
    </item>
  </channel>
</rss>

