Study guide
3.1 PVWA Web Portal Architecture & Interface Configuration
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
3.1 PVWA Web Portal Architecture & Interface Configuration
Key Takeaways Explain This Topic AI
The Password Vault Web Access (PVWA) operates as a multi-tier presentation layer hosted on Microsoft IIS, communicating with the Digital Vault exclusively over TCP port 1858 via the encrypted CyberArk Vault protocol.
Global web portal settings, search indexing rules, and platform configurations reside centrally in the PVWAConfig Safe (primarily inside PVConfiguration.xml and Policies.xml), while individual user UI customizations are isolated in PVWAPrivateUserPrefs.
PVWA utilizes two built-in service accounts: PVWAUser (for interacting with Vault data on behalf of authenticated sessions) and PVWAGWUser (the Gateway user establishing the initial authenticated channel to the Vault).
Configuration changes made to PVConfiguration.xml are cached in IIS worker process memory and automatically refreshed every 20 minutes by default (ConfigurationRefreshInterval), or instantaneously upon an IIS reset.
Last updated: September 2026
3.1 PVWA Web Portal Architecture & Interface Configuration
Password Vault Web Access (PVWA) is the primary presentation tier and operational interface for CyberArk Privileged Access Manager (PAM). Through this centralized portal, users check out privileged credentials, initiate isolated administrative sessions via Privileged Session Manager (PSM), and submit approval workflows. Simultaneously, administrators configure platforms, onboard accounts, govern Safe permissions, and monitor active session telemetry. For the CyberArk Defender (PAM-DEF) exam, candidates must master the underlying Microsoft Internet Information Services (IIS) infrastructure, Vault-resident configuration architecture, and interface customization techniques.
The Multi-Tier Architecture of PVWA
PVWA operates as a multi-tier web application built on Microsoft Windows Server. Rather than storing application logic, session state, or credentials locally on the web server's filesystem, PVWA acts as an intelligent proxy between web clients and the CyberArk Digital Vault.
Network Communication & Protocol Flows
PVWA bridges two distinct network boundaries:
Client-to-PVWA (Ingress) : End users and administrators connect to PVWA over standard HTTPS (TCP port 443) using modern web browsers. All communication is encrypted via Transport Layer Security (TLS).
PVWA-to-Vault (Egress) : PVWA communicates directly with the primary Digital Vault engine using the proprietary CyberArk Vault protocol over TCP port 1858 . All queries for account metadata, authorization checks, and configuration files flow across this single port.
PVWA-to-Session Components : When launching privileged sessions, PVWA either generates an encrypted .rdp bootstrap file for desktop PSM connections or proxies the session via the clientless HTML5 Gateway over HTTPS (TCP port 443).
High Availability & Load Balancing Topologies
In enterprise environments, high availability is achieved by deploying multiple PVWA web servers behind a Network Load Balancer (such as F5 BIG-IP or AWS Application Load Balancer). Because PVWA stores minimal persistent state locally, any node can process incoming requests if session persistence (cookie-based sticky sessions) is enabled. Session affinity prevents user sessions from bouncing between differing IIS worker processes, avoiding ASP.NET session state invalidation.
Microsoft IIS & Application Pool Architecture
PVWA is deployed inside Microsoft IIS (typically IIS 10 on Windows Server 2019/2022). Understanding its virtual directory layout and application pool behavior is essential for deployment and maintenance.
Virtual Directories and Applications
The PVWA installation registers a web application under the IIS Default Web Site, structured around specific URIs:
/PasswordVault : The root application directory hosting the web application framework, static assets, and client resources.
/PasswordVault/v10 : The modern Angular-based single-page application interface, providing optimized account views and streamlined navigation.
/PasswordVault/API : The REST API endpoint framework, enabling programmatic administrative operations and third-party integrations.
Application Pool Configuration
PVWA runs inside a dedicated IIS application pool named PasswordVaultWebAccessPool :
.NET CLR Version : Runs in .NET CLR Version v4.0 with Integrated Managed Pipeline Mode.
Architecture : Configured as a 64-bit process ( Enable 32-Bit Applications = False ).
Application Pool Identity : Defaults to ApplicationPoolIdentity , running under the least-privileged virtual service account context created by IIS.
Worker Process Management : Hosted by w3wp.exe . System administrators must coordinate worker process recycling during maintenance windows to avoid dropping active administrative workflows.
Configuration Storage: PVWAConfig and PVWAPrivateUserPrefs Safes
A core design principle of CyberArk PAS is that no enterprise configuration is stored locally on the PVWA web server . If a PVWA server fails, an administrator can deploy a replacement server, run the PVWA installer, and instantly rejoin the cluster without manual reconfiguration because configurations reside centrally inside Vault Safes.
The PVWAConfig Safe
The PVWAConfig Safe is the central configuration repository for all PVWA servers in the environment. It contains core XML configuration objects that govern the visual interface, policy behaviors, and system options:
PVConfiguration.xml : Governs global UI parameters, system-wide options, search property configurations, authentication method displays, platform view assignments, and branding elements.
Policies.xml : Houses definitions of all active and inactive platforms, specifying credential management parameters, account properties, and CPM operational rules.
Configuration Caching & ConfigurationRefreshInterval
To eliminate database overhead on the Digital Vault, PVWA caches PVConfiguration.xml and associated parameters in the local memory of the IIS worker process ( w3wp.exe ).
The synchronization of this cache is controlled by the ConfigurationRefreshInterval parameter defined inside PVConfiguration.xml (under Administration -> Configuration Options -> Options -> General ). By default, this value is set to 20 minutes (1,200 seconds). When an administrator updates UI settings in PVWA, other cluster nodes may not reflect updates until their interval expires. To force an immediate refresh, administrators can run iisreset or recycle PasswordVaultWebAccessPool in IIS.
The PVWAPrivateUserPrefs Safe & Service Accounts
While PVWAConfig contains global parameters, the PVWAPrivateUserPrefs Safe stores individualized user preferences—including customized grid column ordering, favorite Safes, default search filters, and dashboard widget layouts. Each user's settings are stored in unique objects indexed by user ID.
During installation, the installer provisions two specialized Vault service accounts:
PVWAUser : Used by the web application to query and write data to the Vault on behalf of authenticated human sessions.
PVWAGWUser (Gateway User): Used to establish the initial anonymous connection between IIS and the Vault before user authentication takes place. It verifies system availability and retrieves login screen parameters.
Both accounts authenticate using credential files ( pvwauser.ini and pvwagwuser.ini ) stored securely on the PVWA host and protected by the machine's local encryption keys.
Web Interface Customization & UI Navigation
Administrators can customize the PVWA interface for branding and compliance:
Corporate Branding : Logos and banners can be uploaded via Administration -> Configuration Options to replace default emblems.
Security Disclaimers : Organizations frequently mandate legal disclaimers. Setting DisplayDisclaimer=Yes and populating DisclaimerText in PVConfiguration.xml forces users to acknowledge terms before logging in.
Search Property Indexing : The Accounts search engine allows users to locate credentials by username, address, or custom file categories. Adding custom account properties to the indexed search properties list in PVConfiguration.xml accelerates queries across large vaults.
The modern PVWA v10 interface organizes operations into four core workspaces:
Accounts : Inventory view for credential check-outs, rotations, and PSM connections.
Safes : Administrative console for Safe permissions, CPM assignments, and retention rules.
Administration : Governance hub for Platform Management, User Management, and System Options.
Monitoring : Live auditing workspace for session shadowing, keystroke monitoring, and termination.
PVWA Architectural Artifacts Comparison
Component / Artifact Storage Location Managing Identity Operational Function
PVConfiguration.xml PVWAConfig Safe (Vault) PVWAUser / Admins Global portal options, UI branding, search properties, and system parameters
Policies.xml PVWAConfig Safe (Vault) PVWAUser / Admins Master repository of target platform definitions and policy parameters
User Preferences PVWAPrivateUserPrefs Safe (Vault) End Users (via PVWAUser ) Per-user grid layouts, customized filters, recent searches, and UI favorites
pvwauser.ini Local PVWA filesystem ( conf ) Local Machine Key Encrypted credential file used by PVWAUser for Vault authentication
pvwagwuser.ini Local PVWA filesystem ( conf ) Local Machine Key Encrypted credential file used by PVWAGWUser for anonymous pre-auth queries
Local Cache IIS Worker Memory ( w3wp.exe ) Application Pool Identity RAM cache of XML configurations; auto-refreshes every 20 minutes