PAM on-premises or cloud: deciding where privileged access belongs

All Posts

Remote Access

9 min

 read

PAM on-premises or cloud: where privileged access belongs

Cloud PAM is quick to set up; on-premises PAM keeps session data and control in-house. Five criteria to decide where your privileged access belongs.

Jan Zeppernick - Amitego CEO

Jan Zeppernick

Management

Published

14 Aug 2025

Aktualisiert

17 Nov 2026

Introduction

Almost all software is moving to the cloud. For privileged access management (PAM) it is worth taking a second look. A PAM system manages access to your most critical systems, stores administrator passwords and records every privileged session. Buying it as SaaS puts exactly this data, and the availability of that access, in a vendor's hands.

This article compares cloud PAM and on-premises PAM against five criteria, shows which model suits whom, and explains what to look for when running PAM on-premises.

Key Takeaways

  • A PAM system stores admin credentials, approval rules and session recordings, which makes it critical infrastructure itself.
  • With cloud PAM this data sits with the vendor and is also subject to its jurisdiction, for US vendors the CLOUD Act.
  • If the internet or the vendor fails, cloud PAM blocks privileged access to your own systems.
  • For critical infrastructure, OT, finance and public sector, on-premises PAM is usually the better fit.
  • Agentless solutions such as VISULOX keep the operating effort of on-premises low.

What a PAM system actually stores

To answer cloud or on-premises, start with the data. A PAM system holds three highly sensitive sets: the credentials of privileged accounts, meaning administrator and service passwords; the approval rules for who may access what and when; and the session recordings that show what was done on servers, databases and controllers. These recordings are the most sensitive metadata an organisation produces. They reveal network layout, system names, configurations and often content.

Availability matters too: if the PAM system is unreachable, administrators and service providers cannot reach the systems either. A PAM system is therefore critical infrastructure in its own right. Our article What is privileged access management? covers the basics.

Cloud PAM compared with on-premises PAM across five criteria

Cloud PAM and on-premises PAM compared

1. Where session data is stored

With cloud PAM, recordings and logs live in the vendor's infrastructure. With on-premises PAM they stay in your own data centre or private cloud. For organisations whose regulator or customers dictate where access evidence is kept, that often settles the question.

2. The vendor's jurisdiction

If the vendor or its parent company sits in a third country, that country's law applies as well. US vendors, for example, are subject to the CLOUD Act, which can oblige them to hand data to US authorities regardless of whether the servers are in Frankfurt or Virginia. On-premises, data and keys stay within your own control. Our article IT security independent of the US shows how this factors into vendor selection.

3. Dependency and availability

Cloud PAM requires a working internet connection and an available vendor. If either fails, privileged access to your own systems is blocked, often exactly when administrators need it most during an incident. An on-premises system keeps running regardless.

4. Updates and changes

A SaaS vendor rolls out updates on its own schedule. That is convenient, but it can change workflows without you choosing the timing or testing first. On-premises, you plan updates in your maintenance windows and test them beforehand. In regulated environments with change management this is often mandatory.

5. Attack surface

A central SaaS platform through which many customers run their privileged access is an attractive target. A well-known example is the attack on the US Treasury in late 2024, where attackers got in through a stolen API key for BeyondTrust's cloud remote support service. An on-premises instance serves only your organisation and can be isolated deliberately.

When cloud PAM makes sense

Cloud PAM has real advantages: it is quick to deploy, needs no in-house operation and scales with little effort. For small teams without their own data centre, with mostly cloud-based target systems and no special data residency requirements, it can be the right choice. In that case, check the vendor's jurisdiction, exit terms and availability commitments carefully.

When on-premises PAM is the better choice

The more critical the target systems, the stronger the case for on-premises. That typically applies to:

  • Critical infrastructure operators and organisations under NIS2 that must control access to control systems demonstrably. See our article on IT security for energy suppliers.
  • OT environments deliberately separated from the internet, where no cloud service should reach in.
  • Banks, insurers and public authorities with rules on data residency and outsourcing.
  • Organisations focused on digital sovereignty that want to reduce dependency on third countries.

Our article Sovereign PAM solution: 7 selection criteria lists further criteria, and 6 PAM licensing criteria helps with licensing models.

The objection: on-premises is a lot of work

The most common objection to on-premises is operating effort, and it depends heavily on architecture. Classic PAM suites need agents on every target system, several servers and long rollout projects. An agentless solution that sits as an access gateway in front of the target systems changes that: nothing is installed on target systems, users connect through the browser, and existing directories are connected via standards such as LDAP or SAML.

VISULOX is built for exactly this: on-premises, agentless and usually ready in under two days. It has been developed in Stuttgart for over 20 years, with sales and service for Europe in Zurich. See the VISULOX product overview and Enterprise ready for large environments.

Decision checklist

  1. Where should session recordings and credentials be stored, and who may access them?
  2. Which jurisdiction is the vendor subject to, and is there a parent company outside the EU?
  3. What happens to privileged access if the internet or the vendor goes down?
  4. Who decides when updates are applied and tested?
  5. How much operating effort does the chosen architecture really need, with or without agents?

Contact

Your Direct Path to Secure Remote Access

Speak directly with a cybersecurity expert.

Personal Meeting
Personal Meeting
Personal Meeting

Conclusion

Cloud or on-premises is not a matter of taste for PAM. A PAM system holds the keys to an organisation's most critical systems and its most sensitive evidence. Cloud PAM can suit small, cloud-heavy teams. The more critical the target systems and the stricter the requirements, the more data residency, jurisdiction, availability and control over updates point to on-premises PAM. With an agentless architecture, the operating effort stays manageable. (This article does not constitute legal advice.)

Frequently Asked Questions

What is the difference between cloud PAM and on-premises PAM?

With cloud PAM the vendor runs the system as SaaS, and credentials and session recordings sit in its infrastructure. With on-premises PAM the system runs in your own data centre or private cloud, and you keep control of data, updates and availability.

Is cloud PAM insecure?

Not in principle. Reputable vendors secure their platforms carefully. The questions are different ones: where is the data, which law applies to the vendor, and what happens if the vendor goes down? For critical environments these points often favour on-premises.

Is on-premises PAM hard to operate?

That depends on the architecture. Solutions with agents on every target system are demanding. Agentless solutions such as VISULOX sit as a gateway in front of the systems, need no installation on target systems and are usually ready in under two days.

Does NIS2 require an on-premises solution?

No. NIS2 does not prescribe an operating model, but it does require effective access control, multi-factor authentication, supply chain security and evidence. A cloud vendor is itself part of your supply chain and must be assessed accordingly.

Jan Zeppernick - Amitego CEO

Jan Zeppernick

Management

Jan has over 12 years of consulting experience at PwC and Ernst & Young, focusing on information security and compliance for critical infrastructure and the automotive industry. As a certified ISO 27001 Lead Auditor and strategy expert, he advises organizations on establishing and auditing security management systems in accordance with ISO 27001 and TISAX.