Study guide

8.3 PSM Universal Connector Framework & Custom Integrations

CyberArk Defender - PAM PAM-DEF

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Vault Architecture, Network & Security

1.1 CyberArk PAS Core Architecture & Component Topology 1.2 Vault OS Hardening, Network Isolation & Port Requirements 1.3 Vault Cryptography, Encryption Keys & Master User Recovery

2 Chapter 2: Vault Configuration, Administration & CLI Utilities

2.1 Vault Server Configuration Files & DBParm.ini Tuning 2.2 Vault Administrative Utilities & PARClient Commands 2.3 Event Notification Engine (ENE) & Notification Administration

3 Chapter 3: Password Vault Web Access (PVWA) Administration

3.1 PVWA Web Portal Architecture & Interface Configuration 3.2 PVWA REST API Administration & Lifecycle Automation 3.3 PVWA Security Settings, User Access & Session Timeouts

4 Chapter 4: Central Policy Manager (CPM) Architecture & Operations

4.1 CPM Service Architecture, Logs & Multi-CPM Load Distribution 4.2 The Credential Management State Machine: Change, Verify & Reconcile 4.3 CPM Plug-in Architecture, Process/Prompts Files & Custom Plug-in Troubleshooting 4.4 Loosely Connected Devices: Rotating Laptop & Workstation Credentials

5 Chapter 5: Safe Design, RBAC & Account Governance

5.1 Enterprise Safe Architecture & Naming Conventions 5.2 Safe Permissions, Authorizations & Safe Handler Delegation 5.3 Object Versioning, Retention Policies & Storage Quotas 5.4 Mandatory Account Properties, Account Types & Linked Accounts 5.5 Vault Users, Predefined Groups & Vault-Level Authorizations

6 Chapter 6: Account Discovery & Lifecycle Workflows

6.1 Automated Account Discovery, Detection Rules & Pending Accounts 6.2 Dual Control Workflows, Multi-Level Approvals & Master Approver 6.3 Exclusive Access, One-Time Passwords (OTP) & Check-out Automation 6.4 Bulk Onboarding: Password Upload Utility, Bulk Upload REST API & AccountUploader

7 Chapter 7: Master Policy & Platform Management

7.1 Master Policy Framework & Enterprise Compliance Rules 7.2 Platform Architecture, Settings Tree & Platform Duplication 7.3 Platform Policy Overrides, Advanced Settings & Target Tuning

8 Chapter 8: Privileged Session Manager (PSM) Core Architecture

8.1 PSM Architecture, Jump Host Isolation & Service Accounts 8.2 PSM Connection Components (PSM-RDP, PSM-SSH, PSM-Web) 8.3 PSM Universal Connector Framework & Custom Integrations 8.4 Split Workflow: Separating Session Use from Credential Retrieval

9 Chapter 9: PSMP, HTML5 Gateway & Session Security

9.1 PSM for SSH (PSMP) Architecture & Unix Proxy Brokering 9.2 PSM HTML5 Gateway Architecture & Clientless Web Access 9.3 Session Recording, Storage in Recordings Safes & Vault Retention 9.4 CyberArk Remote Access (Vendor PAM): Administering Third-Party Privileged Access

10 Chapter 10: Live Session Auditing, Reporting & Privileged Threat Analytics

10.1 Live Session Monitoring, Shadowing & Active Termination 10.2 Privileged Threat Analytics (PTA) Behavioral Anomaly Detection 10.3 PTA Automated Incident Response & SIEM Integration (CEF/Syslog) 10.4 Vault Reports, Report Authorizations & the Export Vault Data (EVD) Utility

11 Chapter 11: Application Access Manager (AAM) & Secrets Management

11.1 AAM Credential Provider (CP) Architecture & Local Memory Cache 11.2 Central Credential Provider (CCP) & Web Service Integration 11.3 Application Server Credential Provider (ASCP) & Application Authentication (AppID) 11.4 Conjur Secrets Manager & Cloud-Native DevOps Workflows

12 Chapter 12: Directory Integration, Disaster Recovery & Troubleshooting

12.1 Directory Integration: LDAP Mapping, RADIUS MFA & SAML 2.0 SSO 12.2 Disaster Recovery (DR) Vault & PADR Replication Architecture 12.3 Vault Backup Operations with PAReplicate & Safe Recovery 12.4 Diagnostic Procedures, Vault/CPM/PSM Error Codes & System Recovery

8.3 PSM Universal Connector Framework & Custom Integrations

Key Takeaways Explain This Topic AI

The PSM Universal Connector framework (formerly PSM Custom Dispatcher) allows organizations to integrate arbitrary thick-client, client/server, and legacy enterprise software into CyberArk PSM session isolation and auditing workflows.

Custom Universal Connectors are built on the AutoIt scripting engine using the CyberArk AutoIt wrapper library (PSMGenericClientDriver.au3), which standardizes credential fetching, error handling, process execution, and session logging.

Secure automation requires accurate detection of target client GUI elements, leveraging the AutoIt Window Info tool (Au3Info.exe) to capture window titles, class names, control IDs, and focus states for reliable credential injection.

The CyberArk Marketplace provides hundreds of certified, community-tested connection components that can be downloaded as ZIP packages and imported directly into PVWA to accelerate deployment.

Deployment and validation of custom connectors require deploying the compiled dispatcher executable (.exe) to the PSM Components folder, updating AppLocker rules to whitelist the binary, and testing through interactive PSM test runs with debug logging enabled.

Last updated: September 2026

8.3 PSM Universal Connector Framework & Custom Integrations

Quick Answer: The PSM Universal Connector framework (formerly PSM Custom Dispatcher ) enables organizations to extend jump-host isolation, transparent credential injection, and session recording to proprietary, legacy, or third-party thick-client applications. Built on the lightweight AutoIt scripting engine and CyberArk's PSMGenericClientDriver.au3 wrapper, custom dispatchers automate window detection and credential entry using GUI tools like Au3Info.exe . Compiled dispatchers are placed in the PSM Components folder, whitelisted in Windows AppLocker via PSMConfigureAppLocker.xml , and registered in PVWA. Pre-built connectors can also be imported directly from the CyberArk Marketplace .

The Universal Connector Framework Architecture

Enterprise IT environments rely heavily on specialized administrative thick clients that lack native PAM integrations:

Industrial SCADA and building automation software.

Proprietary banking, financial, and healthcare client/server applications.

Enterprise Resource Planning (ERP) fat clients (such as SAP GUI).

Specialized firewall and network management consoles (such as Cisco ASDM).

Mainframe terminal emulators (TN3270 / TN5250 clients).

Without a custom integration mechanism, administrators would access these systems directly from unmanaged endpoints with static, visible passwords.

The Universal Connector framework addresses this challenge by encapsulating arbitrary Win32 and x64 executables into CyberArk's secure session architecture. When a session initiates, PSM executes a compiled custom dispatcher that queries session parameters from the Vault, launches the client application, detects the authentication dialog, injects credentials directly into UI controls, and registers the application process ID (PID) with PSM for active surveillance and video recording.

The AutoIt Scripting Engine and PSMGenericClientDriver Wrapper

CyberArk selected AutoIt as the scripting engine for Universal Connectors. AutoIt interacts natively with the Windows Messaging API, manipulates window controls with minimal overhead, and compiles into standalone binaries without requiring external runtimes on the hardened PSM host.

Core Wrapper Functions ( PSMGenericClientDriver.au3 )

CyberArk provides the PSMGenericClientDriver.au3 library to standardize communication between the dispatcher script and the PSM service:

PSMGenericClient_Init() : Establishes communication with the PSM service, parses command-line parameters, and prepares shared memory.

PSMGenericClient_GetSessionProperty($propName) : Securely retrieves account properties from the Vault, such as "Address" , "UserName" , "Password" , and custom platform file attributes.

Target Execution ( Run ): Launches the target client executable and captures its process identifier.

PSMGenericClient_SendPID($PID) : Essential exam concept. Passes the target application's Process ID back to the PSM service. This registration enables PSM to bind session recording (video and keystroke capture) and enforce LockApplicationWindow . If omitted, PSM cannot track the session and closes prematurely.

PSMGenericClient_Term() : Notifies PSM of successful injection and terminates the dispatcher process, leaving the target application under PSM monitoring.

PSMGenericClient_LogMessage($msg, $level) : Emits structured diagnostic messages to PSM log files ( $LOG_LEVEL_INFO , $LOG_LEVEL_ERROR ).

Secure Scripting Standards

Never Log Secrets: Plaintext passwords and private keys must never be passed to PSMGenericClient_LogMessage() or written to temporary files.

Variable Cleansing: Plaintext variables must be wiped from memory immediately after injection (e.g., $Password = "" ).

Fail-Safe Timeouts: All window wait operations must include explicit timeouts to prevent hung dispatcher processes on the PSM host.

Window Identification, Control Automation, and UI State Management

Accurate GUI element detection is critical for reliable credential injection into non-standard dialogs:

Element Discovery with Au3Info.exe

Developers use the AutoIt Window Info Tool ( Au3Info.exe ) to inspect target login dialogs:

Window Matching: Captures window title and class (e.g., [CLASS:#32770] ). Setting AutoItSetOption("WinTitleMatchMode", 2) allows partial substring matching.

Control Identifiers: Captures control properties, such as Control ID ( [ID:1001] ), ClassNameNN ( Edit1 , Button2 ), or window handle ( HWND ).

Control Injection: ControlSetText vs. Send

Risks of Send() : Simulates raw keystrokes to whichever control holds active focus. If a background window or notification steals focus, keystrokes are lost or typed into the wrong window.

Advantages of ControlSetText() : Targets specific UI controls directly using control identifiers. It writes text near-instantaneously without requiring active focus, eliminating race conditions. ; Example AutoIt injection workflow

  • AutoItSetOption("WinTitleMatchMode", 2)
  • $hWnd = WinWaitActive("Console Login", "", 15)
  • If $hWnd = 0 Then
  • PSMGenericClient_LogMessage("Login window not found", $LOG_LEVEL_ERROR)
  • PSMGenericClient_Term()
  • Exit
  • EndIf
  • ControlSetText($hWnd, "", "Edit1", $Username)
  • ControlSetText($hWnd, "", "Edit2", $Password)
  • ControlClick($hWnd, "", "Button1")
  • CyberArk Marketplace Integration and Community Connectors

Before developing a custom connector from scratch, administrators should search the CyberArk Marketplace . The Marketplace hosts hundreds of pre-built, community-tested, and CyberArk-certified connection components.

Marketplace packages are distributed as .zip archives containing:

Connection Component XML: Contains component parameters, Target Settings, and client arguments.

Compiled Dispatcher / Source Code: The compiled .exe or .au3 script ready for deployment.

AppLocker Configuration Snippet: XML rules for whitelisting the connector.

Implementation Guide: Prerequisites, client installation instructions, and configuration parameters.

Packages can be imported directly into PVWA via Administration > Options > Import Connection Component , significantly reducing development effort.

Deployment Pipeline, AppLocker Lockdown, and Troubleshooting

Deploying a custom connector requires following a strict implementation workflow:

Compile Binary: Compile the .au3 script to an executable using Aut2Exe.exe , ensuring the architecture (x86 vs x64) matches the target client.

Deploy Files: Copy the compiled dispatcher executable and client dependencies to C:\Program Files (x86)\CyberArk\PSM\Components\ .

Update AppLocker: Add path or hash rules to PSMConfigureAppLocker.xml for both the dispatcher and target client binaries: <Application Name="CustomDispatcher" Type="Exe" Path="C:\Program Files (x86)\CyberArk\PSM\Components\CustomDispatcher.exe" Method="Path" />

<Application Name="TargetApp" Type="Exe" Path="C:\Program Files\Vendor\App\client.exe" Method="Path" />

Apply AppLocker Policy: Execute .\PSMConfigureAppLocker.ps1 in an elevated PowerShell session to update Windows Local Security Policy.

Configure PVWA: Register the Connection Component in PVWA, set LockApplicationWindow = Yes , and link the component to the appropriate Platform.

Validate & Test: Perform end-user test connections and verify session recordings in PVWA.

Diagnostic Troubleshooting Matrix

Symptom Root Cause Resolution

Session fails immediately with Access Denied AppLocker policy blocks dispatcher or client binary Check Event Viewer (Event ID 8004); add path/hash rules to PSMConfigureAppLocker.xml and rerun script

Dispatcher times out waiting for login dialog Window title mismatch or slow client launch Verify window title with Au3Info.exe , adjust WinTitleMatchMode , or increase WinWaitActive timeout

Credentials entered into wrong fields UI controls dynamically reordered or focus lost using Send() Replace Send() with ControlSetText() using specific Control IDs

Session terminates immediately after login PSMGenericClient_SendPID called with launcher PID instead of target process Capture child application PID and pass to PSMGenericClient_SendPID()

Loading diagram... CyberArk PSM Universal Connector Execution & Process Tracking Flow