Study guide
9.3 Session Recording, Storage in Recordings Safes & Vault Retention
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
9.3 Session Recording, Storage in Recordings Safes & Vault Retention
Key Takeaways Explain This Topic AI
CyberArk PSM separates session recording into searchable text metadata (keystrokes, window titles, SQL commands) and differential vector/frame graphical video.
Active recordings are temporarily buffered on the PSM server at C:\Program Files (x86)\CyberArk\PSM\Recordings to prevent network interruptions from dropping audit data.
Upon session termination, recordings are asynchronously uploaded over TCP port 1858 to dedicated PSMRecordings or host-specific PSMRecordingsSafe_<hostname> Safes in the Vault.
Vault recording Safes enforce WORM-like immutability with AES-256 object encryption, requiring structured retention rules and PAReplicate archiving to prevent storage exhaustion.
Last updated: September 2026
9.3 Session Recording, Storage in Recordings Safes & Vault Retention
Quick Answer: Privileged Session Manager (PSM) records all proxied administrative activities using a dual-stream architecture: searchable text metadata (keystrokes, window titles, executed commands, SQL statements) and compressed graphical video (differential screen frames and vector graphics). During an active session, recordings are buffered locally on the PSM host in C:\Program Files (x86)\CyberArk\PSM\Recordings . Once the session ends, the recording is finalized and uploaded asynchronously over TCP port 1858 into dedicated Vault Safes (such as PSMRecordings or PSMRecordingsSafe_<PSMServerName> ). In the Vault, recordings are protected by AES-256 object-level encryption , tamper-resistant immutability, and configurable Safe retention policies, with long-term compliance archiving supported via PAReplicate .
The Dual Architecture: Metadata Indexing vs. Visual Capture
A critical design achievement of CyberArk PSM is the separation of session recording into two distinct, synchronized streams:
1. Searchable Text & Keystroke Metadata
What is Captured: Keystrokes typed by the user, active window titles, process launches, SQL queries (in database connection components), clipboard copy/paste events, and shell commands.
Storage Mechanism: Stored as searchable text metadata and audit events in the Vault database and recordings Safes.
Operational Purpose: Allows security officers to search PVWA for specific activity (e.g., searching for DROP TABLE , net user /add , or regedit ) and immediately jump to the exact second in the video recording where that action occurred. It also provides telemetry streamed to Privileged Threat Analytics (PTA) for real-time anomaly detection.
2. Differential Vector & Frame Screen Capture
What is Captured: Full visual capture of the remote desktop or terminal interface.
Proprietary Compression Engine: PSM does not record continuous high-framerate raster video (such as a 30 FPS MP4 stream), which would generate hundreds of megabytes per session. Instead, PSM captures screen differentials, graphical update bounding boxes, and vector drawing commands compressed using CyberArk's recording codecs.
Storage Efficiency: When an administrator leaves their session idle, PSM records zero frames. Under normal administrative workloads, graphical recording consumes only 1 to 5 MB per hour of active session , achieving extreme storage efficiency without degrading playback fidelity.
The Session Recording Lifecycle: Endpoint to Vault
The recording workflow is engineered to guarantee audit trail integrity even during network degradation between the PSM server and the Digital Vault:
Real-Time Capture & In-Flight Buffering: When an administrator launches a session, the PSM core service spawns the connection component along with the recording monitor process ( CAPSMRcp.exe or equivalent recorder). The recorder captures user interface events, window focus changes, and keystroke buffers directly from the isolated session.
Local Disk Spooling on PSM: Recording chunks are spooled locally on the PSM host's NTFS filesystem at C:\Program Files (x86)\CyberArk\PSM\Recordings . Active subfolders contain .rec (video/vector data), .log (audit text events), and .idx (timeline synchronization) files. Local buffering ensures that transient network interruptions between PSM and the Vault never cause dropped frames or dropped sessions.
Session Finalization & Checksumming: When the user disconnects, logs off, or is terminated, the recording service closes file handles, generates a cryptographic hash/checksum of the recording bundle to ensure tamper-evidence, and marks files for upload.
Asynchronous Upload to Vault (TCP 1858): The PSM Uploader service initiates an authenticated session to the Digital Vault over TCP port 1858 using PSMAppUser . The finalized recording files are uploaded into the target recordings Safe. Once the Vault confirms that the object is committed to disk, the upload transaction completes.
Local Cache Pruning ( RecordingCleanDays ): To prevent the PSM local disk from filling up, the PSM maintenance engine evaluates the local Recordings directory. The parameter RecordingCleanDays (configured in basic_psminf.ini or platform settings, defaulting to 2–7 days) determines how long uploaded recording files are retained locally before deletion.
Vault Recordings Safes Architecture & Cryptographic Protection
Recordings stored in the Digital Vault are managed within specialized Vault Safes designed for high-capacity binary storage and strict regulatory governance:
Consolidated Safe ( PSMRecordings ): In smaller environments, all PSM servers upload session recordings into a single default Safe named PSMRecordings .
Per-Server Safes ( PSMRecordingsSafe_<PSMServerName> ): In enterprise environments with multiple PSM servers, recordings are segregated into dedicated Safes named after each PSM host (e.g., PSMRecordingsSafe_PSM01 ). This avoids Safe-level file count bottlenecks, isolates Safe locks, and optimizes database performance.
Envelope Encryption: Every recording uploaded to the Vault is encrypted with a unique symmetric AES-256 object key . The object key is encrypted with the Safe Key, which is encrypted by the Vault's Server Key. Individual recordings cannot be decrypted or inspected without authenticated Vault engine arbitration.
WORM Immutability: Recordings Safes enforce Write Once, Read Many (WORM) compliance. Vault administrators and PSM service accounts do not possess permission to edit or truncate recording objects. The Vault database rejects any API request attempting to modify an archived recording.
Separation of Duties: PSMAppUser holds Add file/object , List files , and Write file/object permissions, but never Delete or Modify. Members of the Auditors group hold Retrieve file/object and List files to view recordings in PVWA.
Retention Policies, Compliance & Storage Management
Session recordings represent the fastest-growing consumer of storage capacity within the Digital Vault:
Compliance Mandates: PCI-DSS Requirement 10.7 mandates retaining audit logs for at least 1 year , with 90 days immediately available online. Sarbanes-Oxley (SOX) Section 404 often requires retaining records for 5 to 7 years .
Vault Safe Retention vs. Object Versioning: For recordings Safes, object versioning is set to 0 because recordings are static, immutable single-instance files. Retention is governed by the Safe property Retention (days) (e.g., 180 days). The Vault's internal purge process automatically deletes recording objects exceeding this retention window.
Preventing Storage Exhaustion: If the Vault NTFS storage volume drops below emergency thresholds (e.g., less than 1–2 GB free), the PrivateArk Server engine will automatically halt the Vault service to prevent database corruption.
Long-Term Cold Archiving with PAReplicate : Organizations deploy the CyberArk PAReplicate utility on an external backup server to copy recording Safes to cold enterprise storage tiers (SAN, NAS, AWS S3 Glacier, Azure Archive). Once replicated externally, the online Vault retention window can be safely set to 90 or 180 days.
Session Recording Profiles & Storage Impact
Recording Stream Type Data Captured Average Storage Consumption Searchable in PVWA?
Standard GUI Video (RDP) Screen differentials, window movements, vector graphics 1 to 5 MB per active hour (0 MB when idle) No (visual playback only)
Keystrokes & Text Metadata User-entered keystrokes, clipboard paste, window titles 10 to 50 KB per active hour Yes (Instant text search & jump-to-time)
SSH Terminal Recording (PSMP) Full terminal stream, commands, outputs, ANSI codes 50 to 200 KB per active hour Yes (Full command transcript search)
Database SQL Activity Executed SQL queries, affected rows, stored proc calls 20 to 100 KB per active hour Yes (Searchable SQL command audit)
Web Application Session Browser window rendering, field inputs, form submissions 2 to 6 MB per active hour Yes (Keystrokes & URLs searchable)