Centrify Privilege Service Deploys Everywhere: On-premises, Private Cloud or PIM-as-a-Service

I’m very pleased to announce that we’ve added a brand-new deployment option to Centrify Privilege Service, our enterprise-grade privileged identity management (PIM) solution for remote access, shared account password management, multi-factor authentication (MFA) and privileged session monitoring. Privilege Service is now the only product of its type available today that natively supports all three deployment models that enterprise customers need: on-premises, private cloud and public cloud.

Privilege Service has been available as PIM-as-a-Service from day one, i.e. the public cloud deployment option. And now, you have the option to install, deploy and manage Privilege Service within your own IT environment. You can deploy it in a traditional on-premises model, in your data center and behind your firewall. You can deploy it in a virtual private cloud (VPC) as an extension to your data center that either you manage or a vendor manages for you. Or, you can deploy it entirely in your own private cloud that’s independent of your data center. Traditional or hybrid, on-premises or in the cloud. It’s your choice.

CPS

Regardless of how you decide to deploy it, Privilege Service is the same product with the same great feature sets (adjusting for a few things that do not make sense in an on-premises or private cloud installation): all the features for securely accessing servers and network devices with password checkouts and support for SSH and RDP; all the features for shared account password management (SAPM) and application-to-application password management (AAPM); all the MFA features, including support for server MFA with Centrify Server Suite; and all the session monitoring features, including tight integration with Server Suite Enterprise Edition. In fact, it’s the same code base that runs your Centrify Cloud tenant or your on-premises/private cloud Privilege Service installation.

We know that one size does not fit everyone, and one deployment model does not, either. We did this to give you a choice so that you can decide how you want to deploy Privilege Service. Regardless of how you deploy it — as a Centrify cloud service or installed and managed by you in your own environment — it’s the same product, with the same great features.

How do you decide which deployment model is right for you? Here are some thoughts from some folks at Centrify who are very close to our customers and their deployment concerns — our sales engineering and technical marketing teams.

First, here are some reasons why you might deploy PIM-as-a-Service:

  • Low implementation cost
  • Low operational overhead
  • Low infrastructure overhead
  • Don’t want to manage manual product updates
  • Want fast time to value and rapid upgrade cadence
  • Don’t want to integrate optional services manually (e.g. SMTP, SMS, Google maps)

And, here are some reasons why you might deploy on-premises or in a private cloud:

  • Concerned about public cloud
  • Need total control over the app & stack
  • Policy and/or compliance says “no public cloud”

Should you decide on an on-premises/private cloud deployment, don’t worry, you’ll get new feature updates at the same cadence that we update the cloud service. We’ll post updates in the form of installer packages every four weeks (more or less). And, long term support (LTS) releases will come out every six months if you want to stay at a fixed version level for a period of time.

In addition to the new deployment options, we’re rapidly adding new features and functionality to Privilege Service, and we’ll have a lot to talk about between now and the end of the year!

If you’re interested in evaluating Centrify Privilege Service for yourself — on-premises, private cloud or PIM-as-a-Service, please contact your Centrify sales representative or visit us here.