PSM connectors & CPM plugins

Every estate has the application that won't play along: the vendor console with its own login page, the switch that wants a menu-driven password change. That is where we come in.

PSM connection components

A privileged session is only isolated and recorded if PSM knows how to open it. When the Marketplace has nothing for your target, we build the connector.

  • Web applications: connectors for vendor consoles and admin portals, using the web application framework (WebDriver), including login flows with MFA or TOTP injection where your version supports it.
  • Thick clients: Universal Connector components (AutoIt or the PSM SDK) for Windows administration tools that need credentials typed or injected.
  • SSH and proxies: PSMP configuration and connection components for Unix, network devices and jump servers.
  • Hardening: AppLocker rules, dispatcher configuration and session restrictions, so that a connector never becomes a way out of PSM.

To see how a web connector is put together, read our step-by-step guide to PSM web application connectors.

CPM plugins

Rotation only covers what CPM can talk to. We write plugins for the targets that standard platforms don't handle:

  • Terminal plugins (TPC11The Terminal Plugin Controller drives a CPM plugin from a process file (the steps) and a prompts file (what the target is expected to answer).) for network and security appliances with interactive, menu-driven or vendor-specific prompts;
  • Web application plugins for consoles that only change passwords through a browser;
  • REST API plugins for SaaS consoles and modern appliances;
  • PowerShell plugins for Windows and Microsoft workloads.

Each plugin covers verify, change and reconcile, with error handling that tells your operators what went wrong in plain words rather than a generic failure code.

How we build them

  1. Check what existsWe look at the Marketplace and existing platforms first. Building a connector that already exists is money badly spent.
  2. Lab buildDeveloped and tested in a lab that mirrors your target and your CyberArk version, never first in production.
  3. Test matrixVerify, change, reconcile and logon flows, error cases, session recording and restrictions, all documented.
  4. Packaging and handoverA platform package, installation notes and the source. You own the code and can maintain it without us.

Field notes

Nordic bank

Review of applications and of their privileged access protection, including the development of CPM plugins and PSM connectors for targets not covered by standard platforms.

Telecom group

CyberArk integrations for a wide range of projects, with drivers for Fortinet, Gigamon, Juniper and Oracle targets, maintained across upgrades.

Describe your target

Questions

Before you ask

Do you check the Marketplace before building?

Always. If a supported connector or plugin exists, we will tell you and help you deploy it instead.

Who owns the connector code?

You do. We deliver the source, the platform package and the documentation.

Will the connector survive CyberArk upgrades?

We build on the supported frameworks and test against your target version. An upgrade can still change behaviour, so we document what to re-test after each one.

Does it work with Privilege Cloud?

Yes. With Privilege Cloud, CPM and PSM run on connector servers in your network, and custom plugins and connectors are deployed there.

● Next step

Tell us about your vault

Version, size, deadline. We will tell you straight away whether we are the right people for it.