Study guide

2.2 Vault Administrative Utilities & PARClient Commands

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

2.2 Vault Administrative Utilities & PARClient Commands

Key Takeaways Explain This Topic AI

The PrivateArk Client GUI provides low-level Safe, user, licensing, and audit management directly at the storage and database layer, bypassing PVWA Master Policy enforcement.

PACLI (PrivateArk Command Line Interface / PARClient) provides headless, scriptable automation governed by a strict lifecycle: INIT, DEFAULT, LOGON, command execution, LOGOFF, and TERM.

Critical PACLI commands include CREATESAFE and UPDATESAFE for Safe lifecycle management, as well as FINDFILES, GETFILE, and ADDFILE for programmatic object manipulation.

Enterprise automation scripts must never store plaintext credentials; administrators must use CreateCredFile.exe to generate secure credential files bound to OS user, host, and binary paths.

Last updated: September 2026

2.2 Vault Administrative Utilities & PARClient Commands

Quick Answer: CyberArk provides two primary low-level administrative utilities: the graphical PrivateArk Client (used for direct database, Safe, licensing, and raw log administration) and the command-line utility PACLI ( pacli.exe / PARClient, used for headless scripting and automation). Both tools operate over TCP port 1858 directly against the PrivateArk Server engine, bypassing PVWA Master Policy constraints and dual-control approval workflows.

PrivateArk Client GUI Architecture & Operations

The PrivateArk Client is a 32-bit thick-client administrative console installed on designated management jump hosts or on the Vault server during staging. It establishes direct encrypted sessions over TCP port 1858 using the proprietary PrivateArk RPC protocol. While daily credential access and password rotations occur via the Password Vault Web Access (PVWA) web portal, the PrivateArk Client remains essential for low-level system operations, recovery procedures, and emergency maintenance.

Key Administrative Functions in PrivateArk Client

Safe & Container Management : Administrators can create, configure, and delete Safes, inspect file structures, and view raw folder hierarchies. Unlike PVWA, PrivateArk Client displays raw file objects, version histories, and low-level metadata.

Granular Safe Authorizations (ACLs) : Key Safe-level permissions configured in PrivateArk Client include:

Manage Safe : Modifies Safe properties, retention settings, and user access.

Backup Safe : Authorizes backup utilities and replication agents against the Safe.

View Audit : Permits reviewing historical access logs for objects in the Safe.

Access Safe without Confirmation : Bypasses dual-control approval requirements when retrieving credentials.

Retrieve, Store, and Delete Files : Grants specific object manipulation rights.

License File Administration : Inspecting active license parameters ( license.xml ), reviewing allocated user licenses against quotas (e.g., EPVUser, CPM, PSM, AppProvider), and uploading updated license files.

Audit Log Inspection : Directly opening and reviewing italog.log and Safe activity logs without relying on web services or SIEM forwarding.

Directory Mapping & User Administration : Creating internal Vault users, defining administrative groups, configuring LDAP directory mappings, and managing administrative credentials.

PrivateArk Client vs. PVWA: The Exam Distinction

  • Capability PrivateArk Client GUI Password Vault Web Access (PVWA)
  • Primary Layer Direct Vault Database & Storage Application / Web Presentation Layer
  • Master Policy Enforcement No — Bypasses Master Policy rules Yes — Enforces Master Policy & Platform settings

Dual Control Workflows Bypassed if user has 'Access without Confirmation' Strictly enforced by web workflow engine

  • Credential Rotation Cannot trigger CPM rotation directly Initiates Verify, Change, and Reconcile tasks
  • Session Isolation (PSM) Cannot launch PSM proxy sessions Launches isolated RDP, SSH, and Web sessions
  • Disaster Recovery Access Operates even if PVWA / IIS is offline Inaccessible if web tier or IIS fails
  • PARClient / PACLI Command-Line Architecture

The Privileged Access Command Line Interface (PACLI), also known as the PARClient CLI utility, is an administrative executable ( pacli.exe ) providing scriptable command-line access to the PrivateArk Server over TCP port 1858.

The Mandatory PACLI Session Lifecycle

PACLI is a stateful command engine. Automation scripts must strictly execute its six-stage lifecycle:

INIT : Allocates internal memory buffers, socket handlers, and API libraries.

DEFAULT : Defines session constants, including default Vault name, user identity, and timeout thresholds.

LOGON : Establishes an authenticated session against the Vault database, receiving a session authorization token.

Command Execution : Dispatches administrative commands ( CREATESAFE , ADDFILE , FINDFILES , etc.).

LOGOFF : Invalidates the session token, releases database locks, and records an audit logoff event.

  • TERM : Releases memory allocations and cleanly closes network sockets. # Standard PACLI Execution Pattern
  • pacli INIT
  • pacli DEFAULT VAULT="ProductionVault" USER="PACLIAdmin"
  • pacli LOGON VAULT="ProductionVault" USER="PACLIAdmin" CRED="C:\Keys\admin.cred"
  • # [Administrative operations executed here]
  • pacli LOGOFF VAULT="ProductionVault" USER="PACLIAdmin"
  • pacli TERM
  • Credential Security: CreateCredFile.exe Integration

Hardcoding plaintext administrative passwords inside batch, shell, or PowerShell scripts creates a critical security risk. CyberArk requires administrators to generate encrypted credential files using CreateCredFile.exe : CreateCredFile.exe C:\Keys\admin.cred Password /Username PACLIAdmin /Password SuperSecret123! /Hostname ADMIN-MGMT-01 /AppType PACLI /Exe C:\CyberArk\PACLI\pacli.exe

This utility binds the resulting .cred file to:

The specific machine hostname ( ADMIN-MGMT-01 ).

The designated executable binary hash ( pacli.exe ).

The local operating system user running the process.

If an attacker copies the .cred file to an unauthorized machine, the Vault rejects the authentication token.

  • Syntax and Usage of Core PACLI Commands
  • 1. CREATESAFE

Provisions a new Safe container, assigning its managing CPM and description: pacli CREATESAFE VAULT="ProductionVault" USER="PACLIAdmin" SAFE="Linux_Prod_Keys" DESCRIPTION="Production Unix SSH Keys" MANAGINGCPM="PasswordManager"

SAFE : Unique Safe container name.

MANAGINGCPM : Specifies the CPM user account assigned to manage accounts in this Safe.

2. UPDATESAFE

Modifies Safe properties, description, or version retention settings: pacli UPDATESAFE VAULT="ProductionVault" USER="PACLIAdmin" SAFE="Linux_Prod_Keys" DESCRIPTION="Updated Production Keys" NUMOFVERSIONSRETENTION="10" NUMOFDAYSRETENTION="30"

NUMOFVERSIONSRETENTION : Maximum historical versions retained per object.

NUMOFDAYSRETENTION : Days deleted objects are preserved before purging.

3. ADDFILE

Encrypts and uploads a local file into a specific folder inside a target Safe: pacli ADDFILE VAULT="ProductionVault" USER="PACLIAdmin" SAFE="Linux_Prod_Keys" FOLDER="Root" FILE="id_rsa" LOCALFILE="D:\Staging\id_rsa"

FOLDER : Target folder within the Safe (root level is "Root" ).

LOCALFILE : Path to the local file to encrypt and store.

4. GETFILE

Extracts and decrypts an object from a Safe, saving it locally: pacli GETFILE VAULT="ProductionVault" USER="PACLIAdmin" SAFE="Linux_Prod_Keys" FOLDER="Root" FILE="id_rsa" LOCALFILE="D:\Restored\id_rsa"

Essential for emergency offline secret extraction when web portals are unreachable.

5. FINDFILES

Queries the Vault database to locate objects matching specific patterns within a Safe: pacli FINDFILES VAULT="ProductionVault" USER="PACLIAdmin" SAFE="Linux_Prod_Keys" FOLDER="Root" PATTERN="*.rsa" OUTPUT(NAME,SIZE,CREATIONDATE)

PATTERN : Wildcard search expression.

OUTPUT : Selects returned metadata fields (e.g., name, size, creation date).

Administrative Use Cases & Tool Selection Matrix

While modern deployments favor the PVWA REST API for routine automation, PACLI and PrivateArk Client are preferred in specific operational scenarios:

Air-Gapped & Offline Maintenance : When web components are unavailable, PACLI executes directly on the Vault or from administrative jump hosts.

Disaster Recovery Validation : Automated scripts query replicated DR Vaults to verify data integrity without disturbing PVWA production services.

Bulk Safe Provisioning : Rapidly creating hundreds of departmental Safes and assigning CPM ownership prior to account onboarding.

  • Requirement PrivateArk Client GUI PACLI CLI PVWA REST API
  • License Inspection Optimal Unsupported Partial
  • Emergency File Decryption Optimal Scriptable ( GETFILE ) Complex
  • Batch Safe Provisioning Manual / Slow Highly Scriptable Industry Standard
  • Policy Enforcement Bypassed Bypassed Enforced
  • Authentication Mode Interactive Login Encrypted .cred File REST Bearer Token

Loading diagram... PACLI Stateful Execution Lifecycle & Administrative Operation Sequence